From: richard.purdie@linuxfoundation.org
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] oeqa/concurrencytest: fix for locating meta-selftest
Date: Thu, 20 Dec 2018 12:19:32 +0000 [thread overview]
Message-ID: <75d63f87f2ea25effa7707b735b2123ed2156ea4.camel@linuxfoundation.org> (raw)
In-Reply-To: <50ccbdb3-12b8-e381-5931-b52b5b5efdf5@windriver.com>
On Thu, 2018-12-20 at 18:43 +0800, Robert Yang wrote:
>
> On 12/20/18 6:14 PM, Richard Purdie wrote:
> > On Wed, 2018-12-19 at 23:43 -0800, Robert Yang wrote:
> > Sorry, but this change just swaps one problem for another. meta-
> > selftest is part of OE-Core so its position relative to bitbake
> > isn'tfixed.
>
> I always thought that bitbake must be in oe-core, otherwise it didn't
> work, but seemed that it was incorrect?
bitbake doesn't have a fixed location relative to oe-core. It may
expose bugs but people do put it in different locations.
> > How about we use
> >
> > from oeqa.utils.commands import get_test_layer
>
> Thanks, that is much better, Updated in the repo:
>
> commit 9d03cf9e726232a9df544435cadfe520020ef631
> Author: Robert Yang <liezhi.yang@windriver.com>
> Date: Tue Dec 18 18:38:00 2018 -0800
>
> oeqa/concurrencytest: fix for locating meta-selftest
>
> The previous code assumed builddir and meta-selftest are in the
> same dir, but
> this isn't always true, builddir can be anywhere, use
> get_test_layer() to
> locate meta-selftest can fix the problem.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>
> diff --git a/meta/lib/oeqa/core/utils/concurrencytest.py
> b/meta/lib/oeqa/core/utils/concurrencytest.py
> index f050289..6c403ac 100644
> --- a/meta/lib/oeqa/core/utils/concurrencytest.py
> +++ b/meta/lib/oeqa/core/utils/concurrencytest.py
> @@ -25,6 +25,7 @@ from itertools import cycle
> from subunit import ProtocolTestCase, TestProtocolClient
> from subunit.test_results import AutoTimingTestResultDecorator
> from testtools import ThreadsafeForwardingResult, iterate_tests
> +from oeqa.utils.commands import get_test_layer
>
> import bb.utils
> import oe.path
> @@ -166,7 +167,7 @@ def fork_for_tests(concurrency_num, suite):
> if 'BUILDDIR' in os.environ:
> builddir = os.environ['BUILDDIR']
> newbuilddir = builddir + "-st-" + str(ourpid)
> - selftestdir = os.path.abspath(builddir +
> "/../meta-selftest")
> + selftestdir = get_test_layer()
> newselftestdir = newbuilddir + "/meta-selftest"
>
> bb.utils.mkdirhier(newbuilddir)
This broke on our autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/61
It basically creates a "stampeding herd" of bitbake startups as if you
specify -j 40, it would do this 40 times nearly all at once and that
causes retry problems.
We need to move the call outside the for loop as the value doesn't
change.
Cheers,
Richard
next prev parent reply other threads:[~2018-12-20 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 7:43 [PATCH 0/1] oeqa/concurrencytest: fix for locating meta-selftest Robert Yang
2018-12-20 7:43 ` [PATCH 1/1] " Robert Yang
2018-12-20 10:14 ` Richard Purdie
2018-12-20 10:43 ` Robert Yang
2018-12-20 12:19 ` richard.purdie [this message]
2018-12-20 15:06 ` Richard Purdie
2018-12-21 6:46 ` Yang, Liezhi
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=75d63f87f2ea25effa7707b735b2123ed2156ea4.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox