From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [mm/page_alloc] f26b3fa046: netperf.Throughput_Mbps -18.0% regression #forregzbot
Date: Thu, 8 Sep 2022 13:39:46 +0200 [thread overview]
Message-ID: <91889499-6b15-100d-157a-8d536ad8a18d@leemhuis.info> (raw)
In-Reply-To: <b7593c4a-b232-77d2-6c26-31aacdacbefe@leemhuis.info>
On 13.05.22 10:37, Thorsten Leemhuis wrote:
> On 11.05.22 14:13, Thorsten Leemhuis wrote:
>> TWIMC: this mail is primarily send for documentation purposes and for
>> regzbot, my Linux kernel regression tracking bot. These mails usually
>> contain '#forregzbot' in the subject, to make them easy to spot and filter.
>
> Picked the wrong commit-id, fixing:
>
> #regzbot introduced: f26b3fa046116a7
#regzbot invalid: removing: thread faded out, mixed two regressions, and
some tests showed it might be something that doesn't show up in
real-world tests
https://lore.kernel.org/lkml/20220614020930.GA31620@shbuild999.sh.intel.com/
Not totally sure from reading that last messages in the thread if it's
right thing to ignore this, but warming it up now is not worth it afaics.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
prev parent reply other threads:[~2022-09-08 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220420013526.GB14333@xsang-OptiPlex-9020>
2022-05-11 12:13 ` [mm/page_alloc] f26b3fa046: netperf.Throughput_Mbps -18.0% regression #forregzbot Thorsten Leemhuis
2022-05-13 8:37 ` Thorsten Leemhuis
2022-09-08 11:39 ` Thorsten Leemhuis [this message]
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 \
--in-reply-to=91889499-6b15-100d-157a-8d536ad8a18d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).