From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: LKP report for aubrey-fast_idle/4.8.x [job.yaml]
Date: Mon, 10 Apr 2017 08:52:50 +0800 [thread overview]
Message-ID: <87lgr95bj1.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <070BEF4AC20468458C22969097656CD94BFB595A@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]
"Li, Aubrey" <aubrey.li@intel.com> writes:
> Hi Philip,
>
> It seems that I always encountered an error below so that the test is always incomplete.
> Can you please take a look?
>
> Thanks,
> -Aubrey
>
> aubrey(a)inn:/lkp/lkp$ lkp compare -at v4.8.8 ea899bd65fc285d5753d70a7879a7332821bbc02
> tests: 1
> testcase/path_params/tbox_group/run: fio-basic/1SSD-btrfs-300s-8-randwrite-4k-sync-512g-performance/lkp-bdw-ep2
>
> v4.8.8 ea899bd65fc285d5753d70a787
> ---------------- --------------------------
> fail:runs %reproduction fail:runs
> | | |
> :1 67% 2:3 stderr.ERROR:use_the-f_option_to_force_overwrite_of/dev/nvme0n1p1
> :1 67% 2:3 last_state.incomplete
> :1 100% 3:3 last_state.is_incomplete_run
The base kernel runs well, so it is possible to be a kernel specific
problem. I suggest you to test more times for both the base and head
kernel. And you can get kernel dmesg to check whether it is kernel
specific.
Best Regards,
Huang, Ying
>
>
>> -----Original Message-----
>> From: Li, Philip
>> Sent: Sunday, April 09, 2017 9:01 AM
>> To: Li, Aubrey
>> Subject: LKP report for aubrey-fast_idle/4.8.x [job.yaml]
>>
>> QUEUED JOBS [3]
>> /result/fio-basic/1SSD-btrfs-300s-8-randwrite-4k-sync-512g-performance/lkp-bd
>> w-ep2/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/ea899bd65fc285d
>> 5753d70a7879a7332821bbc02/0 INCOMPLETE
>> /result/fio-basic/1SSD-btrfs-300s-8-randwrite-4k-sync-512g-performance/lkp-bd
>> w-ep2/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/ea899bd65fc285d
>> 5753d70a7879a7332821bbc02/1 INCOMPLETE
>> /result/fio-basic/1SSD-btrfs-300s-8-randwrite-4k-sync-512g-performance/lkp-bd
>> w-ep2/debian-x86_64-2016-08-31.cgz/x86_64-rhel-7.2/gcc-6/ea899bd65fc285d
>> 5753d70a7879a7332821bbc02/2 INCOMPLETE
>>
>> Disclaimer:
>> Results have been estimated based on internal Intel analysis and are provided
>> for informational purposes only. Any difference in system hardware or software
>> design or configuration may affect actual performance.
>>
>> ---
>> 0DAY/LKP kernel testing infrastructure Open Source Technology
>> Center
>> https://lists.01.org/mailman/listinfo/lkp Intel
>> Corporation
>
> _______________________________________________
> LKP mailing list
> LKP(a)lists.01.org
> https://lists.01.org/mailman/listinfo/lkp
prev parent reply other threads:[~2017-04-10 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58e987e8.Luqil0ayGRMlDrfI%philip.li@intel.com>
2017-04-09 1:15 ` LKP report for aubrey-fast_idle/4.8.x [job.yaml] Li, Aubrey
2017-04-10 0:52 ` Huang, Ying [this message]
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=87lgr95bj1.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.