From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>,
yang.wang@windriver.com,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: add ptest support
Date: Tue, 28 Aug 2018 10:10:02 +0100 [thread overview]
Message-ID: <ddceb5bb2230ea780e27601a1ba289dd69351ea3.camel@linuxfoundation.org> (raw)
In-Reply-To: <39d4429f-e3c6-33fc-3073-8cea08d81794@windriver.com>
On Mon, 2018-08-27 at 20:57 -0400, Randy MacLeod wrote:
> On 08/27/2018 06:17 PM, Yang Wang wrote:
> > Not sure if it's worth to run the Ptest on QEMU though, I also run
> > Ptest
> > on SIMICS simulators, thousands of tests didn't get run, looks like
> > the
> > result was not good as well.
> >
> > Now my nightly Ptest runs on x86 device and gets consistent result
> > every
> > day:
> >
> > 2018-08-27T06:26 -- 2018-08-27T09:52
> > Passed: 40518
> > Failed: 289
> > Skipped: 1876
>
> Consistent results are good and > 90% pass rate is very good.
> What are the stats using qemux86-64 and/or simics?
>
> I don't expect that qemu results would be as close to real hardware
> as Simics but it is quite good and freely available.
I think this is an example of where we may need to start adding "stage
2" testing to the autobuilder. The first stage tests would be enough to
get patches merged and be the faster ones, the second stage would be
the longer running things which we'd only trigger when stage one had
passed, maybe on milestone releases.
We'd put off doing this due to the old creaking codebase. With the new
autobuilder codebase, this should be much more straightforward to do...
boost ptest would be something I'd put in the second stage.
Cheers,
Richard
next prev parent reply other threads:[~2018-08-28 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 8:55 [PATCH] boost: add ptest support mingli.yu
2018-06-11 6:18 ` Yu, Mingli
2018-08-27 20:27 ` Randy MacLeod
2018-08-27 22:17 ` Yang Wang
2018-08-28 0:57 ` Randy MacLeod
2018-08-28 9:10 ` Richard Purdie [this message]
2018-08-28 14:25 ` Yang Wang
2018-08-28 17:22 ` Yang Wang
2018-08-29 1:02 ` Anuj Mittal
2018-08-28 1:51 ` Yu, Mingli
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=ddceb5bb2230ea780e27601a1ba289dd69351ea3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=yang.wang@windriver.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