linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [linus:master] [kbuild] 3bc753c06d: xfstests.generic.454.fail #forregzbot
Date: Fri, 30 Dec 2022 11:14:57 +0100	[thread overview]
Message-ID: <0cf0fddb-f2e7-80b8-1c08-cf9919a391bd@leemhuis.info> (raw)
In-Reply-To: <202212291509.704a11c9-oliver.sang@intel.com>

[Note: this mail contains only information for Linux kernel regression
tracking. Mails like these contain '#forregzbot' in the subject to make
then easy to spot and filter out. The author also tried to remove most
or all individuals from the list of recipients to spare them the hassle.]

On 29.12.22 09:49, kernel test robot wrote:
> 
> please be noted we felt quite strange why this change could cause
>   xfstests.generic.454.fail
> but even by rebuild and rerun, the issue seems persistent while keeping clean
> on parent
> 
> daf4218bf8dd9750 3bc753c06dd02a3517c9b498e38
> ---------------- ---------------------------
>        fail:runs  %reproduction    fail:runs
>            |             |             |
>            :10         100%          10:10    xfstests.generic.454.fail
> 
> so we just report out FYI to seek any insights about this.
> 
> 
> Greeting,
> 
> FYI, we noticed xfstests.generic.454.fail due to commit (built with gcc-11):
> 
> commit: 3bc753c06dd02a3517c9b498e3846ebfc94ac3ee ("kbuild: treat char as always unsigned")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> [test failed on linux-next/master c76083fac3bae1a87ae3d005b5cb1cbc761e31d5]
> 
> in testcase: xfstests
> version: xfstests-x86_64-fb6575e-1_20221226
> with following parameters:
> 
> 	disk: 4HDD
> 	fs: ext4
> 	test: generic-group-22
> 

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced 3bc753c06dd02a
#regzbot title ext4/acls: xfstests.generic.454 suddenly fails for the
kernel test robot
#regzbot ignore-activity

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.

      parent reply	other threads:[~2022-12-30 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29  8:49 [linus:master] [kbuild] 3bc753c06d: xfstests.generic.454.fail kernel test robot
2022-12-29 18:55 ` Linus Torvalds
2022-12-30  2:08   ` Jason A. Donenfeld
2022-12-30 15:36   ` Christian Brauner
2022-12-30 10:14 ` 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=0cf0fddb-f2e7-80b8-1c08-cf9919a391bd@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).