public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>, <oe-lkp@lists.linux.dev>,
	<lkp@intel.com>, <linux-fsdevel@vger.kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	<linux-doc@vger.kernel.org>, <ying.huang@intel.com>,
	<feng.tang@intel.com>, <fengwei.yin@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	<oliver.sang@intel.com>
Subject: Re: [viro-vfs:work.dcache2] [__dentry_kill()] 1b738f196e: stress-ng.sysinfo.ops_per_sec -27.2% regression
Date: Thu, 7 Dec 2023 10:29:26 +0800	[thread overview]
Message-ID: <ZXEuBnX4FTDdaqn0@xsang-OptiPlex-9020> (raw)
In-Reply-To: <CAGudoHGgqH=2mb52T4ZMx9bWtyMm7hV9wPvh+7JbtBq0x4ymYA@mail.gmail.com>

hi, Mateusz Guzik,

On Wed, Dec 06, 2023 at 07:30:36PM +0100, Mateusz Guzik wrote:
> Can I get instructions how to reproduce the unixbench regression?

I uploaded the reproducer for unixbench in
https://download.01.org/0day-ci/archive/20231207/202312070941.6190a04c-oliver.sang@intel.com

as in
https://download.01.org/0day-ci/archive/20231207/202312070941.6190a04c-oliver.sang@intel.com/reproduce

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.


> 
> I only found them for stressng.
> 
> -- 
> Mateusz Guzik <mjguzik gmail.com>

  reply	other threads:[~2023-12-07  2:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  4:54 [viro-vfs:work.dcache2] [__dentry_kill()] 1b738f196e: stress-ng.sysinfo.ops_per_sec -27.2% regression kernel test robot
2023-11-30  7:55 ` Al Viro
2023-12-01  2:13   ` Oliver Sang
2023-12-01  2:42     ` Oliver Sang
2023-12-01  4:09     ` Al Viro
2023-12-01  6:56       ` Al Viro
2023-12-01 20:04         ` Al Viro
2023-12-04 13:37           ` Oliver Sang
2023-12-04 19:53             ` Al Viro
2023-12-06  2:40               ` Oliver Sang
2023-12-06  5:49                 ` Al Viro
2023-12-06 14:56                   ` Oliver Sang
2023-12-06 16:15                     ` Al Viro
2023-12-06 16:30                       ` Mateusz Guzik
2023-12-06 16:42                         ` Mateusz Guzik
2023-12-06 17:09                           ` Al Viro
2023-12-06 17:24                             ` Mateusz Guzik
2023-12-06 18:30                               ` Mateusz Guzik
2023-12-07  2:29                                 ` Oliver Sang [this message]
2023-12-08 18:07                                   ` Mateusz Guzik
2023-12-06 21:07                               ` Al Viro
2023-12-06 21:41                                 ` Mateusz Guzik
2023-12-06 16:45                         ` Al Viro
2023-12-06 16:52                           ` Mateusz Guzik

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=ZXEuBnX4FTDdaqn0@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=brauner@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mjguzik@gmail.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ying.huang@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