linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
	Niklas Cassel <niklas.cassel@wdc.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	ltp@lists.linux.it
Subject: Re: [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail
Date: Tue, 20 Jun 2023 16:42:52 +0900	[thread overview]
Message-ID: <61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org> (raw)
In-Reply-To: <202306192248.1ece4c29-oliver.sang@intel.com>

On 6/20/23 14:58, kernel test robot wrote:
> 
> 
> Hello,
> 
> kernel test robot noticed "ltp.ioprio_set03.fail" on:

LTP maintainers,

Patches have been submitted to fix this issue. Were these patches applied ?

Kernel test robot maintainers,

Once the LTP patches are applied, you will need to update LTP.

> 
> commit: eca2040972b411ec27483bf75dc8b84e730e88ff ("scsi: block: ioprio: Clean up interface definition")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> 
> [test failed on linux-next/master f7efed9f38f886edb450041b82a6f15d663c98f8]
> [test failed on fix commit 01584c1e233740519d0e11aa20daa323d26bf598]
> 
> 
> in testcase: ltp
> version: ltp-x86_64-14c1f76-1_20230520
> with following parameters:
> 
> 	disk: 1HDD
> 	fs: xfs
> 	test: syscalls-05
> 
> 
> 
> compiler: gcc-12
> test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G 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/202306192248.1ece4c29-oliver.sang@intel.com
> 
> 
> 
> <<<test_start>>>
> tag=ioprio_set03 stime=1687153195
> cmdline="ioprio_set03"
> contacts=""
> analysis=exit
> <<<test_output>>>
> tst_test.c:1558: TINFO: Timeout per run is 0h 02m 30s
> ioprio_set03.c:39: TFAIL: ioprio_set IOPRIO_CLASS_BE prio 8 should not work
> ioprio_set03.c:47: TINFO: tested illegal priority with class NONE
> ioprio_set03.c:50: TPASS: returned correct error for wrong prio: EINVAL (22)
> 
> Summary:
> passed   1
> failed   1
> broken   0
> skipped  0
> warnings 0
> <<<execution_status>>>
> initiation_status="ok"
> duration=0 termination_type=exited termination_id=1 corefile=no
> cutime=0 cstime=3
> <<<test_end>>>
> 
> 
> 
> To reproduce:
> 
>         git clone https://github.com/intel/lkp-tests.git
>         cd lkp-tests
>         sudo bin/lkp install job.yaml           # job file is attached in this email
>         bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
>         sudo bin/lkp run generated-yaml-file
> 
>         # if come across any failure that blocks the test,
>         # please remove ~/.lkp and /lkp dir to run from a clean state.
> 
> 
> 

-- 
Damien Le Moal
Western Digital Research



  reply	other threads:[~2023-06-20  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20  5:58 kernel test robot
2023-06-20  7:42 ` Damien Le Moal [this message]
2023-06-21 12:47   ` [LTP] " Cyril Hrubis
2023-06-21 15:33     ` Niklas Cassel
2023-06-22  7:32       ` Petr Vorel
2023-06-22  8:30         ` Damien Le Moal
2023-06-22  8:00       ` Cyril Hrubis
2023-07-05  8:36       ` Liu, Yujie

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=61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.petersen@oracle.com \
    --cc=niklas.cassel@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox