From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: lkp ncompare result interpetation
Date: Tue, 04 Feb 2020 14:42:51 +0800 [thread overview]
Message-ID: <20200204064251.GA20734@intel.com> (raw)
In-Reply-To: <CACOpkY697dr7H6Q58gADTDLDKtb1iUbC6-Dr=Z63RUuEEmyR5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
On Tue, Feb 04, 2020 at 11:15:11AM +0530, Bincy Philip wrote:
> *Hi,*
>
> *I am new to lkp test suite.I have installed it and found useful in
> comparing different kernel versions.*
Thanks Bincy for trying it. Would you mind submitting an issue at
https://github.com/intel/lkp-tests, we will have member to support it.
Thanks
>
> *Can somebody help me to understand it better way.Attached is the lkp
> compare test result.Column headings are unclear to me.*
>
> *What does 5322 and 379 mean in the attached result?How can I say which
> kernel is good from the result?*
>
>
> lkp ncompare -s commit="3.10.0-1062.9.1.el7.x86_64" -o commit="3.18.0-rc5" -a
> =======================
> ==================================================================
> compiler/ipc/kconfig/mode/nr_threads/rootfs/tbox_group/testcase:
> gcc-7/pipe/x86_64-rhel-7.6/process/1600%/centos/bn1dhcp244-49.mvista.com/hackbench
>
> commit:
> 3.10.0-1062.9.1.el7.x86_64
> 3.18.0-rc5
>
> 3.10.0-1062.9.1. 3.18.0-rc5
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> 5322:1 -494373% 379:1 dmesg.timestamp:last
> 5322:1 -494373% 379:1 kmsg.timestamp:last
>
>
> Thanks in Advance!!!
>
> Bincy
> _______________________________________________
> LKP mailing list -- lkp(a)lists.01.org
> To unsubscribe send an email to lkp-leave(a)lists.01.org
next prev parent reply other threads:[~2020-02-04 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 5:45 lkp ncompare result interpetation Bincy Philip
2020-02-04 6:42 ` Philip Li [this message]
2020-02-04 7:44 ` Bincy Philip
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=20200204064251.GA20734@intel.com \
--to=philip.li@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.