All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, oliver.sang@intel.com
Subject: Re: [riteshharjani:atomic-writes-v6.12-fs-v10-ext4-rfcv2-wip1] 2eda7299be: xfstests.generic.350.fail
Date: Mon, 28 Oct 2024 13:53:45 +0530	[thread overview]
Message-ID: <87frogmy9a.fsf@gmail.com> (raw)
In-Reply-To: <202410281346.cfd98861-oliver.sang@intel.com>

kernel test robot <oliver.sang@intel.com> writes:

> Hello,
>
>
> it seems a debug patch to us, below report just FYI what we observed in our
> tests.
>
>
> kernel test robot noticed "xfstests.generic.350.fail" on:
>
> commit: 2eda7299be1daa307b815b480cb9dd0b14ad062b ("scsi debug 350mb device and 2x shosts and DEF_PER_HOST_STORE=true")
> https://github.com/riteshharjani/linux atomic-writes-v6.12-fs-v10-ext4-rfcv2-wip1

yes. I thought *wip* does not gets tested by default?

I did submit a patch to only allow for certain branches -
https://github.com/intel/lkp-tests/commit/3a68b7ad329bea895c3d2c31a6b93a99d2eca536 

It has some "integration_testing_branches" and "branch_allowlist". But what
I was looking for was, is there any report for what all gets tested, what
tests passed, how does it decides what tests to run? 
(Note I am aware of build success test report which gets generated which
is quite useful too.)

-ritesh

>
> in testcase: xfstests
> version: xfstests-x86_64-f71228e3-1_20240930
> with following parameters:
>
> 	disk: 4HDD
> 	fs: ext4
> 	fs2: smbv3
> 	test: generic-350
>
>
>
> config: x86_64-rhel-8.3-func
> compiler: gcc-12
> test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202410281346.cfd98861-oliver.sang@intel.com
>
> 2024-10-24 11:26:11 mount /dev/sda1 /fs/sda1
> 2024-10-24 11:26:12 mkdir -p /smbv3//cifs/sda1
> 2024-10-24 11:26:12 export FSTYP=cifs
> 2024-10-24 11:26:12 export TEST_DEV=//localhost/fs/sda1
> 2024-10-24 11:26:12 export TEST_DIR=/smbv3//cifs/sda1
> 2024-10-24 11:26:12 export CIFS_MOUNT_OPTIONS=-ousername=root,password=pass,noperm,vers=3.0,mfsymlinks,actimeo=0
> 2024-10-24 11:26:12 echo generic/350
> 2024-10-24 11:26:12 ./check -E tests/cifs/exclude.incompatible-smb3.txt -E tests/cifs/exclude.very-slow.txt generic/350
> FSTYP         -- cifs
> PLATFORM      -- Linux/x86_64 lkp-skl-d05 6.12.0-rc2-00029-g2eda7299be1d #1 SMP PREEMPT_DYNAMIC Thu Oct 24 12:37:44 CST 2024
>
> generic/350       - output mismatch (see /lkp/benchmarks/xfstests/results//generic/350.out.bad)
>     --- tests/generic/350.out	2024-09-30 21:13:44.000000000 +0000
>     +++ /lkp/benchmarks/xfstests/results//generic/350.out.bad	2024-10-24 11:26:14.507852855 +0000
>     @@ -1,10 +1,13 @@
>      QA output created by 350
>      Create and format
>      Zero punch
>     +fallocate: Operation not supported
>      Punch range past EOD
>     +fallocate: Operation not supported
>      Check contents
>     ...
>     (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/350.out /lkp/benchmarks/xfstests/results//generic/350.out.bad'  to see the entire diff)
> Ran: generic/350
> Failures: generic/350
> Failed 1 of 1 tests
>
>
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20241028/202410281346.cfd98861-oliver.sang@intel.com
>
>
>
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-10-28  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28  5:23 [riteshharjani:atomic-writes-v6.12-fs-v10-ext4-rfcv2-wip1] 2eda7299be: xfstests.generic.350.fail kernel test robot
2024-10-28  8:23 ` Ritesh Harjani [this message]
2024-10-29  5:25   ` Oliver Sang

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=87frogmy9a.fsf@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.