From: Thorsten Leemhuis <linux@leemhuis.info>
To: regressions@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, lkp@lists.01.org
Subject: Re: [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail #forregzbot
Date: Mon, 5 Sep 2022 12:47:23 +0200 [thread overview]
Message-ID: <7f2cf157-2d1e-8b19-57ef-adce50db047b@leemhuis.info> (raw)
In-Reply-To: <d8290cbe-5d87-137a-0633-0ff5c69d57b0@redhat.com>
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.
On 17.08.22 02:06, Gavin Shan wrote:
>
> Yeah, the system for the coverage was likely having high CPU loads,
> which is similar
> to my (simulated) environment. I usually have my system being idle when
> running the
> coverage test cases. I didn't hit this specific failure before.
>
> Lets leave it as of being. We can improve if needed in future :)
In that case:
#regzbot invalid: 0-day report that apparently can be ignoreD
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.
next prev parent reply other threads:[~2022-09-05 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 7:50 [KVM] e923b0537d: kernel-selftests.kvm.rseq_test.fail kernel test robot
2022-08-15 21:42 ` Sean Christopherson
2022-08-16 5:02 ` Gavin Shan
2022-08-16 10:02 ` Gavin Shan
2022-08-16 22:23 ` Sean Christopherson
2022-08-17 0:06 ` Gavin Shan
2022-09-05 10:47 ` Thorsten Leemhuis [this message]
2022-11-01 8:32 ` Robert Hoo
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=7f2cf157-2d1e-8b19-57ef-adce50db047b@leemhuis.info \
--to=linux@leemhuis.info \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--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).