Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Cc: joshua.g.lock@intel.com
Subject: Re: [PATCHv3 00/30] oeqa core and oe-selftest threaded enablement
Date: Fri, 21 Jul 2017 09:11:04 +0100	[thread overview]
Message-ID: <1500624664.22282.97.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1500327589.git.anibal.limon@linux.intel.com>

On Mon, 2017-07-17 at 16:45 -0500, Aníbal Limón wrote:
> This v3 makes changes on tinfoil busy status patch and adds an
> environment variable to oe-seltest script to specify number of
> threads. 
> There are patches for bitbake [3] and meta-yocto-bsp [4] that was
> send
> to their specific ML.
> 
> The first 6 patches previous enable support of threads in oeqa core
> are independent and can be merged first.
> 
> The v2 address comments did by Patrick about add better explanation
> on the commit messages and some typos.
> 
> Other interesting information to add is that with this series we will
> able to execute oe-selftest in around half [1] of the original time
> [2], (9406.782s vs 17303.014s).

I tested this, admittedly on top of the server rework changes and see
some odd failures on the autobuilder. Things aren't looking very
deterministic and I'm a little worried about merging them.

(e.g. https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/
397)

The second issue I'd like to ask questions about is whether the tinfoil
changes and server rework we've just done remove the need for some of
this patchset?

I ask since now I'm hoping the "main thread" issues might be resolved
and we truly can have independent tinfoil connections. There were
issues there but I believe Paul has resolved those.

For that reason I'm going to defer this patchset from M2 (I did take
some of the initial patches) and ask that we review the patchset in
light of the server rework and tinfoil changes that just merged.

I do know that for example, "oeqa/selftest/case: Support bitbake memres
mode in per build director" is no obsolete as we removed the memres
init script and the -t option to bitbake.

Cheers,

Richard


  parent reply	other threads:[~2017-07-21  8:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 21:45 [PATCHv3 00/30] oeqa core and oe-selftest threaded enablement Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 01/30] oeqa/core/loader: Generate function _make_failed_test dynamically Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 02/30] selftest/cases/package: Call parent setUpClass method Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 03/30] oeqa/selftest/{context, case}: Handle KeyboardInterrupt/SIGINT and SIGTERM Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 04/30] bb/server/process: Handle EINTR on idle_commands select Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 05/30] bb/tinfoil: run_command handle busy status in bitbake server Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 06/30] oe/copy_buildsystem: check_sstate_task_list also pop BBPATH from env Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 07/30] oeqa/core/threaded: Enable support to use the main thread Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 08/30] oeqa/core/threaded: Add support to run into a thread at end of execution Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 09/30] oeqa/core/threaded: logSummary add skipped tests info Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 10/30] oeqa/core/tests: Update test_loader threaded to cover main thread usage Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 11/30] oeqa/selftest/{case, context}: Add builddir by test class and context Aníbal Limón
2017-07-18 15:16   ` Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 12/30] oeqa/selftest/case: Add wrappers to utils.commands modules Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 13/30] oeqa/selftest/case: Creates meta-selftest layer per class Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 14/30] oeqa/selftest/case: tearDown extra commands print what actually fails Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 15/30] oeqa/selftest/case: Support bitbake memres mode in per build directory Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 16/30] oeqa/selftest/cases: Use testlayer_path instead of call get_test_layer() Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 17/30] oeqa/selftest/cases: Use builddir from class instead of get from environment Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 18/30] oeqa/selftest/cases: Use wrapper methods from OESelfTestCase class and enable threaded runs Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 19/30] oeqa/selftest/cases: imagefeatures " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 20/30] oeqa/selftest/cases: runqemu " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 21/30] oeqa/selftest/cases: runtime " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 22/30] oeqa/selftest/cases: eSDK " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 23/30] oeqa/selftest/cases: devtool " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 24/30] oeqa/selftest/cases: recipetool enable for " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 25/30] oeqa/selftest/cases: Move devtool deploy test case to own module Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 26/30] selftest/cases/devtool{, end}: Move update/finish_modify tests to its " Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 27/30] seltest/cases/devtool: Build dbus on test_devtool_add_git_local Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 28/30] argparse_oe: Add int_positive type Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 29/30] oeqa/selftest/context: Enable support for threaded runs Aníbal Limón
2017-07-17 21:45 ` [PATCHv3 30/30] oeqa/selftest/cases: systemd_boot enable " Aníbal Limón
2017-07-17 22:01 ` ✗ patchtest: failure for oeqa core and oe-selftest threaded enablement (rev3) Patchwork
2017-07-21  8:11 ` Richard Purdie [this message]
2017-07-21 16:15   ` [PATCHv3 00/30] oeqa core and oe-selftest threaded enablement 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=1500624664.22282.97.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=anibal.limon@linux.intel.com \
    --cc=joshua.g.lock@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