From: Tudor Florea <tudor.florea@enea.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] util-linux: Add ptest
Date: Thu, 26 Nov 2015 01:00:18 +0200 [thread overview]
Message-ID: <56563D81.4060403@enea.com> (raw)
In-Reply-To: <CAJTo0LbNcwn0wxdoFvtitdyOVXEZ=HVsStN0JLdt9LFNOgkJJg@mail.gmail.com>
On 25/11/2015 23:33, Burton, Ross wrote:
>
> On 23 November 2015 at 23:41, Tudor Florea <tudor.florea@enea.com
> <mailto:tudor.florea@enea.com>> wrote:
>
> +--- a/tests/run.sh 2015-11-18 15:09:05.517018566 +0100 ++++
> b/tests/run.sh 2015-11-18 20:02:15.492749213 +0100
>
>
> Would it be possible to keep run.sh as it is but pass --parallel 1
> from run-ptest so it doesn't run the jobs in parallel?
Short answer is no. In the latest version the package run.sh has been
adapted to work with parallel test driver (only). Ptest however works
with serial test driver only at this moment.
Partly off-topic: This automake patch [1] would we a good step toward
having Ptest working in parallel. However the patch was not yet
applied in poky and upstream still haven't answered the query [2]
> Or, do we care if it runs the tests in parallel?
Running tests in parallel have the benefit of spending less time with
testing. Otherwise, the results should be the same.
> I'm looking at that patch and thinking it's going to be a nightmare
> to maintain when upstream modifies their script.
I agree is not the best patch. I simply revert to the file used in
version 2.24.2 ( plus a minor grep option addition) to make it work.
We will get rid of this patch when we eventually make Ptest run with
parallel test driver.
Another option is to ignore run.sh wrapper and add the logic "run all
testcases" into run-ptest.
>
> Ross
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2014-November/098932.html
[2] https://lists.gnu.org/archive/html/bug-automake/2014-11/msg00005.html
Regards,
Tudor.
next prev parent reply other threads:[~2015-11-25 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 23:41 [PATCH 0/1] util-linux: Add ptest Tudor Florea
2015-11-23 23:41 ` [PATCH 1/1] " Tudor Florea
2015-11-25 21:33 ` Burton, Ross
2015-11-25 23:00 ` Tudor Florea [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 3:08 Tudor Florea
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=56563D81.4060403@enea.com \
--to=tudor.florea@enea.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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