From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2 v7] test-case-mgmt
Date: Mon, 18 Feb 2019 10:12:15 +0000 [thread overview]
Message-ID: <f4c88aab6ff934328e03be66ade30d04a679e65f.camel@linuxfoundation.org> (raw)
In-Reply-To: <9DDD2658D1FE414E99172D2DB1E4D043481860E7@PGSMSX109.gar.corp.intel.com>
On Mon, 2019-02-18 at 09:20 +0000, Yeoh, Ee Peng wrote:
> Thank you for sharing on the selftest comparison consideration!
>
> I agreed with you that in the high level, selftest should be
> independent of which HOST_DISTRO, it shall compared 2 selftest even
> when the host distro are different.
>
> But in the case that the build have multiple set of selftest each
> with slightly different environments (eg. host distro), in that case,
> will it better to compare selftest more closely if possible with same
> host distro used?
In an ideal world, yes. In reality trying to do that and making it
conditional will complicate the code for little "real" end difference
though?
Cheers,
Richard
next prev parent reply other threads:[~2019-02-18 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 5:50 [PATCH 0/2 v7] test-case-mgmt Yeoh Ee Peng
2019-02-14 5:50 ` [PATCH 1/2 v7] resulttool: enable merge, store, report and regression analysis Yeoh Ee Peng
2019-02-14 5:50 ` [PATCH 2/2 v7] scripts/resulttool: enable manual execution and result creation Yeoh Ee Peng
2019-02-17 16:09 ` [PATCH 0/2 v7] test-case-mgmt Richard Purdie
2019-02-17 17:54 ` Richard Purdie
2019-02-17 22:45 ` Richard Purdie
2019-02-18 8:09 ` Yeoh, Ee Peng
2019-02-18 9:07 ` Richard Purdie
2019-02-18 9:20 ` Yeoh, Ee Peng
2019-02-18 10:12 ` Richard Purdie [this message]
2019-02-19 1:02 ` Yeoh, Ee Peng
2019-02-20 6:27 ` Yeoh, Ee Peng
2019-02-20 21:44 ` Richard Purdie
2019-02-21 1:19 ` Yeoh, Ee Peng
2019-02-21 1:24 ` Yeoh, Ee Peng
2019-02-18 1:28 ` Yeoh, Ee Peng
2019-02-18 8:33 ` Yeoh, Ee Peng
2019-02-18 9:17 ` Richard Purdie
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=f4c88aab6ff934328e03be66ade30d04a679e65f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ee.peng.yeoh@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox