Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp1251547pxy; Fri, 23 Apr 2021 04:03:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx7cjXxEXNIrs01AXXI6L1GxVSrwDZ+nUQiyvCJrMcNRXLsO9/hmcMnC1mGwGknncUmMO2B X-Received: by 2002:a17:906:98d6:: with SMTP id zd22mr3677600ejb.17.1619175806166; Fri, 23 Apr 2021 04:03:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619175806; cv=none; d=google.com; s=arc-20160816; b=KY6OL7sz3Ss/FyhYBq4eZUnvTk4v9DExSzY9NwEK2H5usBFT49H+hH1ZfaJOwYk6WX pX3Q0FTxYRShg6CA6V+naxTKFJ59bEX35bO9/8Aq9DHUW7sDQV59SNwC4V1nma3eBggd 56tzw73BTpZSCm0ReU0u2Dsi/g3LqfwhDTSAoKbMe/QmsSXPYDylfOR58ARWRw5oi2Ua uHGk+HAKPdFmMdsZGJdvTrXi/eVIW6/bbLFjO+OsrUUXAG1CTh3lcMIAq5IXi32RegB9 hennuzpdhkBjoMdIMtcnR4rhzePZAg1x40iHT5pXofGj1EkPmYqSu6aqZGjGo3xTbUkT gV1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=ZofJc5lceP5+xT9us3fsKsgBvIKA0hnkUg3NouSR2UM=; b=SZmwKHlPQiJOuBVn0M+jfUiy4CMss49/+NfQKjwPKzfzhnvCHzTgzD3Ul7LJxqW8k6 D+niOIv9SxP+jh0nDqAZpMemX0BVog7qT6x/adNuk5fJj5uPjmApWozo88W5PqIfPqfh g5LA1rtpNJNX9N6+d1cdT/C3TJkV7J2Zu6pYL3p0SofcCsm5YM8JBxejg3XF3nz5GXip sd+u4flyRr5RObe2umjaVrO297e82PnEEywdlaywqDW6HRT2C/cgn1PlWcHXZtfgLaek Z3AjYy5lM+omrMZo1AFU1Yq/B8eF4TsnH8eJaWNlc7tn3HARFGog4xsvHSW3dE3xue3b pgXw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t9si4977400ejs.621.2021.04.23.04.02.56; Fri, 23 Apr 2021 04:03:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229965AbhDWLCX (ORCPT + 99 others); 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