From: Thorsten Leemhuis <firstname.lastname@example.org> To: Linus Torvalds <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Date: Mon, 1 Nov 2021 05:49:40 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAHk-=wjfbfQobW2jygMvgfJXKmzZNB=UTzBrFs2vTEzVpBXA4Q@mail.gmail.com> On 31.10.21 22:09, Linus Torvalds wrote: > It's been calm, and I have no excuse to add an extra rc, so here we > are, with v5.15 pushed out, and the merge window starting tomorrow. TLDR: Please tell me directly (by CC or forward) or via regzbot (see below) about any regression reports you stumble upon, as I'm giving regression tracking another shot. This time I'm doing it with the help of a bot, which really could need a lot to chew on for a proper test-run. Hi everyone! Years ago I did regression tracking for the Linux kernel for a while. Back then tracking and writing weekly reports was a manual and quite exhausting effort. Nevertheless, I'm giving regression tracking another shot. But this time I'll leave the hard work to a bot I wrote just for this purpose, which is specifically tailored to the needs of Linux kernel development. I tested this 'regzbot' a little in the past few weeks, but I need more regression reports now to shake out bugs and see where things might need big adjustments or fine-tuning. Hence, if you see any regression reports, please tell be about them, for example by simply forwarding the mail to firstname.lastname@example.org or CCing that address on a reply. I'll handle everything else then and tell regzbot about it. But if you feel adventurous, you can also skip me as the man-in-the-middle and tell the bot directly. To do that, just send a reply to the report to the regressions mailing list (email@example.com) either directly or by CCing it on a reply you would have written anyway; when doing so, place something like '#regzbot ^introduced v5.15..' (separated by blank lines) somewhere in the text, as outlined in regzbot's 'getting started guide' or its reference documentation: https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md That's it, regzbot then on its next run will add the report to the list of tracked regression. I'll keep an eye on things and try to fix any problems I notice, as there likely will be a few. But then doesn't need to bother you. There is one thing that would really help: if one or two subsystem maintainers could give regzbot a shot for all the regression reports they get, even for easy fixes, as the bot really needs something to chew on. Any volunteers? As years ago I'll send weekly regression reports, but this time they will get generated directly from regzbot. But thx to the bot there is now also a web-view which provides an always up2date view into the data gathered by regzbot: https://linux-regtracking.leemhuis.info/regzbot/mainline/ Ciao, Thorsten
next prev parent reply other threads:[~2021-11-01 4:49 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-31 21:09 Linux 5.15 Linus Torvalds 2021-11-01 0:23 ` Guenter Roeck 2021-11-01 8:13 ` Geert Uytterhoeven 2021-11-02 1:17 ` Guenter Roeck 2021-11-02 1:44 ` Linus Torvalds 2021-11-02 3:19 ` Guenter Roeck 2021-11-01 4:49 ` Thorsten Leemhuis [this message] [not found] ` <firstname.lastname@example.org> 2021-11-01 11:56 ` Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Greg KH 2021-11-01 12:54 ` Thorsten Leemhuis 2021-11-01 12:33 ` Greg KH 2021-11-01 12:44 ` Thorsten Leemhuis 2021-11-01 13:03 ` Greg KH 2021-11-01 13:34 ` Thorsten Leemhuis 2021-11-01 15:27 ` Greg KH 2021-11-01 16:19 ` Thorsten Leemhuis 2021-11-01 15:07 ` Linux 5.15 Andy Shevchenko 2021-11-01 16:19 ` Lee Jones 2021-11-01 17:25 ` Sudip Mukherjee
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15)' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).