From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: paul.eggleton@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/36] OEQA threading support and selftest migration
Date: Mon, 29 May 2017 08:15:55 -0500 [thread overview]
Message-ID: <1496063755.26945.25.camel@linux.intel.com> (raw)
In-Reply-To: <1495841567.25229.122.camel@linuxfoundation.org>
On Sat, 2017-05-27 at 00:32 +0100, Richard Purdie wrote:
> On Fri, 2017-05-26 at 15:37 -0500, Aníbal Limón wrote:
> > This series is the integration of tree main changes into the OEQA
> > module,
> >
> > * Implement threading support into OEQA core module
> > * Enables OEQA threaded mode into {,e}SDK test component
> > * Migrate current oe-selftest to use the same framework
>
> I tried this on the autobuilder:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/
> builds/901/steps/Running%20oe-selftest/logs/stdio
>
> It was fast, the oe-selftest run which usually takes several hours took
> 30 mins. The above logs suggest we might have a coverage issue though.
BTW, the new OE/QA threading support does not support (yet, Anibal is
planning to work on it) the selftest test cases (because only one
bitbake instance can be running at a time) so we should see similar
times as before with this migration. So, those 30 minutes just comes
from executing a subset, so something may be wrong in the series.
Leo
>
> Cheers,
>
> Richard
next prev parent reply other threads:[~2017-05-29 13:07 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 20:37 [PATCH 00/36] OEQA threading support and selftest migration Aníbal Limón
2017-05-26 20:37 ` [PATCH 01/36] testsdk.bbclass: Remove unused import of OEStreamLogger Aníbal Limón
2017-05-26 20:37 ` [PATCH 02/36] oeqa/sdk/context.py: Import argparse_oe at OESDKTestContext.run method Aníbal Limón
2017-05-26 20:37 ` [PATCH 03/36] oeqa/sdk/context.py: Add return to OESDKTestContext.run() method Aníbal Limón
2017-05-26 20:37 ` [PATCH 04/36] oeqa/core: Don't expose OEStreamLogger in OETestContext Aníbal Limón
2017-05-26 20:37 ` [PATCH 05/36] oeqa/core/runner: OETestResult remove unneeded override of startTest Aníbal Limón
2017-05-26 20:37 ` [PATCH 06/36] oeqa/core: Move OETestContext.log{Summary, Details} into OETestResult Aníbal Limón
2017-05-26 20:37 ` [PATCH 07/36] oeqa/core/threaded: Add new module with OETestLoaderThreaded Aníbal Limón
2017-05-26 20:37 ` [PATCH 08/36] oeqa/core/threaded: Add OEStreamLoggerThreaded class Aníbal Limón
2017-05-26 20:37 ` [PATCH 09/36] oeqa/core/runner: OETestResult add internal _tc_map_results Aníbal Limón
2017-05-26 20:37 ` [PATCH 10/36] oeqa/core/threaded: Add OETestResultThreaded{, Internal} classes Aníbal Limón
2017-05-26 20:37 ` [PATCH 11/36] oeqa/core/threaded: Add support of OETestRunnerThreaded Aníbal Limón
2017-05-26 20:37 ` [PATCH 12/36] oeqa/core/threaded: Add OETestContextThreaded class Aníbal Limón
2017-05-26 20:37 ` [PATCH 13/36] oeqa/core/decorator/depends: Add support for threading mode Aníbal Limón
2017-05-26 20:37 ` [PATCH 14/36] oeqa/core/decorator/oetimeout: Add support for OEQA threaded mode Aníbal Limón
2017-05-26 20:37 ` [PATCH 15/36] oeqa/core/tests: Add tests of OEQA Threaded mode Aníbal Limón
2017-05-26 20:37 ` [PATCH 16/36] oeqa/sdkext/cases: Move sdk_update test into devtool module Aníbal Limón
2017-05-26 20:37 ` [PATCH 17/36] oeqa/sdk: Enable usage of OEQA thread mode Aníbal Limón
2017-05-26 20:37 ` [PATCH 18/36] oeqa/core: Add list tests support in context and runner Aníbal Limón
2017-05-26 20:37 ` [PATCH 19/36] oeqa/core: Add support for run tests by module, class and name Aníbal Limón
2017-05-26 20:37 ` [PATCH 20/36] classes/test{export, images}: Change modules to list Aníbal Limón
2017-05-26 20:37 ` [PATCH 21/36] oeqa/runtime/case: Don't use OEQA framework internal methods Aníbal Limón
2017-05-26 20:37 ` [PATCH 22/36] oeqa/core/README: Improve documentation Aníbal Limón
2017-05-26 20:37 ` [PATCH 23/36] oeqa/core/case: fix typo on comment about exception name Aníbal Limón
2017-05-26 20:37 ` [PATCH 24/36] oeqa/core/context: Raise exception when a manifest is specified but missing Aníbal Limón
2017-05-26 20:37 ` [PATCH 25/36] oeqa/core/context: Use a default iterable modules object Aníbal Limón
2017-05-26 20:37 ` [PATCH 26/36] oeqa/core/context: Omit docstring output on XMLResult Aníbal Limón
2017-05-26 20:37 ` [PATCH 27/36] oeqa/core/context: Include a _pre_run method Aníbal Limón
2017-05-26 20:37 ` [PATCH 28/36] scripts/oe-test: Move load_test_components to oeqa.utils Aníbal Limón
2017-05-26 20:37 ` [PATCH 29/36] oeqa/selftest: Move base class to case module Aníbal Limón
2017-05-26 20:37 ` [PATCH 30/36] oeqa/selftest/case: Migrate case class to the new OEQA framework Aníbal Limón
2017-05-26 20:37 ` [PATCH 31/36] scripts/oe-selftest: Move {add, remove}_include files to case Aníbal Limón
2017-05-26 20:37 ` [PATCH 32/36] oeqa/selftest/case.py: Remove machine selection logic Aníbal Limón
2017-05-26 20:37 ` [PATCH 33/36] oeqa/selftest/case: Don't figure out the testlayer inside Aníbal Limón
2017-05-26 20:38 ` [PATCH 34/36] scripts/oe-selftest: Migrate to new framework into oeqa.selftest.context Aníbal Limón
2017-05-26 20:38 ` [PATCH 35/36] oeqa/selftest/cases: Migrate test cases into the new oe-qa framework Aníbal Limón
2017-05-26 20:38 ` [PATCH 36/36] selftest: Migrate systemd_boot test case to the new framework Aníbal Limón
2017-05-26 21:01 ` ✗ patchtest: failure for OEQA threading support and selftest migration Patchwork
2017-05-26 23:32 ` [PATCH 00/36] " Richard Purdie
2017-05-29 13:15 ` Leonardo Sandoval [this message]
2017-05-29 13:19 ` Richard Purdie
2017-05-29 14:08 ` Leonardo Sandoval
2017-05-29 15:52 ` Aníbal Limón
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=1496063755.26945.25.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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