From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F4D8C433B4 for ; Fri, 23 Apr 2021 11:01:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CE16B61474 for ; Fri, 23 Apr 2021 11:01:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242062AbhDWLCX (ORCPT ); Fri, 23 Apr 2021 07:02:23 -0400 Received: from mx2.suse.de ([195.135.220.15]:49652 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229809AbhDWLCW (ORCPT ); Fri, 23 Apr 2021 07:02:22 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 8DCE8B114; Fri, 23 Apr 2021 11:01:45 +0000 (UTC) Date: Fri, 23 Apr 2021 13:01:45 +0200 Message-ID: From: Takashi Iwai To: Thorsten Leemhuis Cc: Greg KH , Linus Torvalds , "Rafael J. Wysocki" , regressions@lists.linux.dev, Linux Kernel Mailing List , Konstantin Ryabitsev , Pablo Neira Ayuso , ksummit@lists.linux.dev, workflows@vger.kernel.org Subject: Re: RFC: building a regression tracking bot for Linux kernel development In-Reply-To: <8a44e6b3-fff4-ea6f-2643-bb2a15ff990a@leemhuis.info> References: <268a3049-7c0b-8a33-1ff6-5a2d35fcba16@leemhuis.info> <8a44e6b3-fff4-ea6f-2643-bb2a15ff990a@leemhuis.info> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 23 Apr 2021 12:49:25 +0200, Thorsten Leemhuis wrote: > > On 23.04.21 12:11, Greg KH wrote: > > On Thu, Apr 22, 2021 at 09:16:40AM +0200, Thorsten Leemhuis wrote: > >> That can't be all > >> ----------------- > >> > >> Of course the world is more complicated than the simple example scenario > >> above, as the devil is always in the details. The three most obvious > >> problems the initial ideal scenario left aside: > >> > >> * The reporter doesn't specify the #regzb tag at all. Regzbot can't do > >> anything about it, it sadly won't have visionary power and a AI engine > >> any time soon. Some human (for a while that often will be me) thus needs > >> to reply with the tag with a proper reply-to to the report to make > >> regboz track it. > > > > Any specific format/tag we can use to help make this easier? Or is that > > just something that you are going to do "by hand" to start with? > > For now making sure regressions@lists.linux.dev is added to the CCed of > any replies to regression reports would be a really big help to already > establish it as central place where they are all visible. Then no human > or bot needs to monitor hundreds of mailing list to find them -- which > obviously is doomed to fail and was one of the pain points when I > tracked regressions manually years ago. That sounds great. One thing I still wonder is how to populate the report from distro bug trackers. AFAIK, many reports come from there directly or indirectly. Can regzbot can have a reference to bug trackers or such? thanks, Takashi