All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: ChenQi <Qi.Chen@windriver.com>,
	Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] oeqa: Add selftest parallelisation support
Date: Thu, 26 Jul 2018 12:11:56 +0100	[thread overview]
Message-ID: <56d1a5ca98936388dccf918519b87558ea1b6228.camel@linuxfoundation.org> (raw)
In-Reply-To: <1b2cb46a-2bea-eed0-c9df-254ffb3c1f99@windriver.com>

On Thu, 2018-07-26 at 17:37 +0800, ChenQi wrote:
> On 07/26/2018 05:18 PM, Robert Yang wrote:
> > 
> > 
> > On 07/26/2018 05:10 PM, richard.purdie@linuxfoundation.org wrote:
> > > On Thu, 2018-07-26 at 14:00 +0800, Robert Yang wrote:
> > > > 
> > > > On 07/26/2018 11:03 AM, Robert Yang wrote:
> > > > > Hi RP,
> > > > > 
> > > > > On 07/17/2018 12:33 AM, Richard Purdie wrote:
> > > > > > This allows oe-selftest to take a -j option which specifies
> > > > > > how
> > > > > > much test
> > > > > > parallelisation to use. Currently this is "module" based
> > > > > > with
> > > > > > each module
> > > > > > being split and run in a separate build directory. Further
> > > > > > splitting could
> > > > > > be done but this seems a good compromise between test setup
> > > > > > and
> > > > > > parallelism.
> > > > > > 
> > > > > > You need python-testtools and python-subunit installed to
> > > > > > use
> > > > > > this but only
> > > > > > when the -j option is specified.
> > > > > 
> > > > > Should we add python-testtools-native and python-subunit-
> > > > > native,
> > > > > please ?
> > > > > 
> > > > > And add them to TESTIMAGEDEPENDS ?
> > > > 
> > > > After talked with Qi, this won't work since we use host's
> > > > python3. So
> > > > we need install them on host, or use buildtools-tarball.
> > > 
> > > Correct, this is why the modules are only loaded if you use the
> > > -j
> > > option, so the dependency is only needed if you use bitbake -j.
> > > That at
> > >   least minimises the cross-section of users affected.
> > 
> > There might be a bug since we don't use -j in our build farm, but
> > I 
> > see the no
> > testtools module error, I will do more investigations on it.
> > 
> 
> In testsdk.bbclass, we have:
> processes = d.getVar("TESTIMAGE_NUMBER_THREADS") or 
> d.getVar("BB_NUMBER_THREADS")
> ....
>          if processes:
>              result = tc.runTests(processes=int(processes))
>          else:
>              result = tc.runTests()
> 
> processes will not be None even if we don't set 
> TESTIMAGE_NUMBER_THREADS. I think this is not expected.

Ah, yes, that was not intentional. We should perhaps put a:

try: 
    import testools, subunit
except ImportError: 
    xxx

in there...

Cheers,

Richard




  reply	other threads:[~2018-07-26 11:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 16:33 [PATCH 1/6] oeqa: Add selftest parallelisation support Richard Purdie
2018-07-16 16:33 ` [PATCH 2/6] oeqa/core/threaded: Remove in favour of using concurrenttests Richard Purdie
2018-07-16 16:33 ` [PATCH 3/6] oeqa/runner: Simplify code Richard Purdie
2018-07-16 16:33 ` [PATCH 4/6] oeqa: Remove xmlrunner Richard Purdie
2018-07-16 16:33 ` [PATCH 5/6] testsdk: Enable multiprocess execution Richard Purdie
2018-07-16 16:33 ` [PATCH 6/6] oeqa/decorator: Improve reliability Richard Purdie
2018-07-26  3:03 ` [PATCH 1/6] oeqa: Add selftest parallelisation support Robert Yang
2018-07-26  6:00   ` Robert Yang
2018-07-26  9:10     ` richard.purdie
2018-07-26  9:18       ` Robert Yang
2018-07-26  9:37         ` ChenQi
2018-07-26 11:11           ` richard.purdie [this message]
2018-07-27  3:18             ` Robert Yang

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=56d1a5ca98936388dccf918519b87558ea1b6228.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Qi.Chen@windriver.com \
    --cc=liezhi.yang@windriver.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 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.