From: Oliver Sang <oliver.sang@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, lkp@lists.01.org, lkp@intel.com
Subject: Re: [xfs] 1eb70f54c4: xfstests.xfs.348.fail
Date: Fri, 10 Jun 2022 13:38:07 +0800 [thread overview]
Message-ID: <20220610053807.GA9136@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20220602214436.GF1098723@dread.disaster.area>
Hi Dave,
On Fri, Jun 03, 2022 at 07:44:36AM +1000, Dave Chinner wrote:
> > ...
> > (Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/348.out /lkp/benchmarks/xfstests/results//xfs/348.out.bad' to see the entire diff)
> > xfs/349 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//xfs/349.out.bad)
> > --- tests/xfs/349.out 2022-05-16 16:42:32.000000000 +0000
> > +++ /lkp/benchmarks/xfstests/results//xfs/349.out.bad 2022-05-18 11:53:51.101272360 +0000
> > @@ -1,3 +1,2 @@
> > QA output created by 349
> > Format and populate
> > -Scrub
> > ...
> > (Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/349.out /lkp/benchmarks/xfstests/results//xfs/349.out.bad' to see the entire diff)
>
> You are running a test in the "dangerous_fuzzers" group that isn't
> in the auto group. This is a test for developers to find error
> detection issues and, as such, failure is kinda expected. It is not
> regression test that can be used for pass/fail testing....
Thanks a lot for guidance! we will disable auto tests in "dangerous_fuzzers"
group.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2022-06-10 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:04 kernel test robot
2022-06-02 21:44 ` Dave Chinner
2022-06-10 5:38 ` Oliver Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-18 14:45 kernel test robot
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=20220610053807.GA9136@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
/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
all inboxes | Powered by JetHome®