Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp981929pxb; Fri, 22 Apr 2022 15:54:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxZBo4Jd0p89Ib4Eu51IjtbKSR5HbdrIrMW+/FelDXR4bw/DuRyw/JRFcp/1XaAnONiqTvI X-Received: by 2002:a17:902:8608:b0:158:b827:7721 with SMTP id f8-20020a170902860800b00158b8277721mr6675531plo.149.1650668066258; Fri, 22 Apr 2022 15:54:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650668066; cv=none; d=google.com; s=arc-20160816; b=kAFjwbt6Xe+kvViQsyJKt0teYVJ8fadOMH44NEgKRIyUrbbcprnjGYkznhRXfW0ouR oeMGG98CcG2xZoGPFS3L22BGpJqNNO3F6s98cGe7vo0Fz9UOPLRp7vo4B8SNo4uImDzz hddqbL909piLH0qlCJbVMthT1QUZ12xJxe2sfLnbxifAumx5ZsMy0dpnZs7YaYFeGJIM u1L7PQkm08+VlZF7/jLw95uj2F1kt4KmvOSw7JkBYW2bLx/JU+m7zEFdApQxjZaRuAzm +Q5LzQMs7NN3Lr5JIAy9byiDrUnMmeeOfCjrzRCC5nYE5YEhi61EEeEb3YPZpy9OvHTG 15gw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=2Woz/+mZiE4zdgq9fXEdF9FTAhQ1L1IAY4mWe3aDu0c=; b=Y18JJAl3E9qNMkt0BrXtwsXA9Csgvu2+KzoC5f3k8V2bK1X9w9miTVshyNaA1uwlxI ixDxG3oE+kwsdfbjMZbE+FamiwJLyQuWFAllt3TRRzG2xharNesLRKTql6l5TtrQQUg0 bzlgt00XChNUlBRdg6czDMZMmUqgsV/qju8b4VT+fhh9DP4eOg/WG7yTorDRU4rANlME hSop2aZDOMVedJ5bS/2cv552u1zcgZaJgiqgAFdtJnqFxK//BFO2yIf5rzpPyDOppD7u PcWMItBAmrZHcD+r3nLCSBhVajYvK1c4wAimmhCzmfCiIkCDdS7S+T1Lvj0J9FS5z+6x ZVRQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=uh5gJB3a; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id q11-20020a65494b000000b003a6d2c0b6f3si9451323pgs.573.2022.04.22.15.54.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Apr 2022 15:54:26 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=uh5gJB3a; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 471A52CC6F9; Fri, 22 Apr 2022 13:45:01 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351929AbiDTKeK (ORCPT + 99 others); Wed, 20 Apr 2022 06:34:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60908 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350520AbiDTKeJ (ORCPT ); Wed, 20 Apr 2022 06:34:09 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5B3F13F8A9; Wed, 20 Apr 2022 03:31:23 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EAF3E617C5; Wed, 20 Apr 2022 10:31:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EAC5EC385A0; Wed, 20 Apr 2022 10:31:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650450682; bh=VATqHpxy4xhyHxhfLQ62wyl7CnEWwvltNAvm4ld1EQk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=uh5gJB3axqdKC5OsivTse8L4a7Jij90v2MJSBj/nQGBUO5CgTBhN4wsVNnFzlHy21 m/upJaNGtunQ9DdX4OQJ+5KpQ5sga4HsG2MzmadYls3bbCG3lIuV3lmPd4Al2nDxeE t6dz+E4Xh2JFatRiw7FH4e3o9nPSSHNNkBAhGSQH91h+EwyYYQ4hkaR/5a1L2/N3nu JjmZ1u3th3JBvHqG8F7OhYQRm/RtMOQsSO2G3LaxURuQTzw0/+5BQsXZnRdCVUJgLF 04qV6ao7eo3aobR8EWlrGPU1XVuWVVWONwT8GmqvwD3A4HO4wo5SNU7BQ4thrqkM/S zaAmJmg5i4PdQ== Message-ID: Date: Wed, 20 Apr 2022 12:31:16 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: A lot of regression reports submitted to bugzilla.kernel.org are apparently ignored, even bisected ones Content-Language: en-US To: Thorsten Leemhuis , Linus Torvalds , Greg KH , Konstantin Ryabitsev Cc: "regressions@lists.linux.dev" , Linux Kernel Mailing List , workflows@vger.kernel.org References: <6808cd17-b48c-657d-de60-ef9d8bfa151e@leemhuis.info> From: Krzysztof Kozlowski In-Reply-To: <6808cd17-b48c-657d-de60-ef9d8bfa151e@leemhuis.info> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/04/2022 14:35, Thorsten Leemhuis wrote: > Hi! TLDR: I looked closer at every ticket filed in bugzilla.kernel.org > over a time span of two weeks to see how well reports are handled, in > particular those for kernel regressions. The results of this rough > analysis are kinda devastating from my point of view. I for example > found 8 tickets describing a regression where the reporter had even > bisected the problem, but nevertheless the ticket afaics didn’t get a > single reply or any other reaction from a regular kernel developer > within about a week; in fact out of a total of 20 reports that looked > like regressions to me (17 if you exclude tickets where the reporter > used an afaics lightly patched distro kernel), only one got a helpful > reply from a developer within a week. To respond, developer would first had to be notified. Did it happen? Or just some default assignee got automated notification? > That makes us miss valuable > reports and puts our "no regressions" rule into a bad light. Hence, > something IMHO should be done here to improve the situation, but I'm not > sure myself what exactly -- that's why I'm writing this mail. A better > warning on bugzilla’s frontpage suggesting to report issues by mail > maybe? And/or disable all bugzilla products and components where it's > not clear that somebody will be looking at least once at submitted tickets? I find such Bugzilla useless - the Components are not matching reality, Products look ok except missing really a lot. Does it have proper assigners based on maintainers? Nope. At least not everywhere. All the bug or issue reports I get via email and I think I am not alone in this. All automated tools (kbuild, kernelCI) are using emails for bug reporting. Why having one more system which seems not up to date? The only reliable and up to date information we have in maintainers file: who is responsible and whom to CC (e.g. lists). I can give example from my domain: https://bugzilla.kernel.org/show_bug.cgi?id=210047 This is clearly issue for me but there is no way I was notified about this. I just found it by using the keyword from maintainers. Wrong mailing list as Assignee, no CC to me. Such bug reports will be missed because there is no way I can receive information about them. Why then providing interface for bug reports which by design will not reach the respective person? Best regards, Krzysztof