All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement
Date: Fri, 07 Apr 2017 15:18:35 +0800	[thread overview]
Message-ID: <87efx48z3o.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <070BEF4AC20468458C22969097656CD94BFB573E@shsmsx102.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 731 bytes --]

"Li, Aubrey" <aubrey.li@intel.com> writes:

>> 
>> For this kind of test, to avoid pollute the results of 0-Day, it is better for you to
>> take the machine out of 0-Day to do the test.  You can test with lkp-tests with
>> the same job file.
>
> Can you please specify how to take the machine out of 0-day but still test with
> lkp-tests with the same job file?  
>
> setup lkp test on my own? how to prevent lkp schedule task on this machine?

Lei will take care of take the machine out of 0-day.

To run lkp-tests on your own, please refer to,

https://docs.google.com/a/intel.com/presentation/d/1c1qDq8przc1jJTJWq1VDhiIfjC7uhuRsaPdeZmOn-qQ/edit?usp=sharing

Best Regards,
Huang, Ying

> Thanks,
> -Aubrey

  reply	other threads:[~2017-04-07  7:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05  7:12 [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement kernel test robot
2017-04-06  5:56 ` Li, Aubrey
2017-04-06  6:26   ` Ye Xiaolong
2017-04-06 13:54     ` Li, Aubrey
2017-04-07  1:33       ` Huang, Ying
2017-04-07  1:47         ` Li, Aubrey
2017-04-07  2:21           ` Huang, Ying
2017-04-07  3:10             ` Li, Aubrey
2017-04-07  1:46       ` Ye Xiaolong
2017-04-07  2:12         ` Li, Aubrey
2017-04-07  2:24           ` Huang, Ying
2017-04-07  5:26             ` Li, Aubrey
2017-04-07  6:02               ` Huang, Ying
2017-04-07  6:06                 ` Li, Aubrey
2017-04-07  6:11                   ` Ye Xiaolong
2017-04-07  6:16                     ` Li, Aubrey
2017-04-07  6:25                       ` Huang, Ying
2017-04-07  6:41                         ` Li, Aubrey
2017-04-07  6:44                           ` Huang, Ying
2017-04-07  6:51                             ` Li, Aubrey
2017-04-07  6:58                               ` Huang, Ying
2017-04-07  6:12                   ` Huang, Ying
2017-04-07  3:34         ` Li, Aubrey
2017-04-07  3:44           ` Ye Xiaolong
2017-04-07  6:58         ` Li, Aubrey
2017-04-07  7:03           ` Huang, Ying
2017-04-07  7:12             ` Li, Aubrey
2017-04-07  7:18               ` Huang, Ying [this message]
2017-04-07  8:32               ` Du, Julie
2017-04-07  8:39                 ` Li, Aubrey
2017-04-07  8:43                   ` Huang, Ying
2017-04-07  8:48                     ` Li, Aubrey
2017-04-07  8:53                     ` Li, Aubrey

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=87efx48z3o.fsf@yhuang-dev.intel.com \
    --to=ying.huang@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 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.