From: Alex Franco <alejandro.franco@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] testimage: add/modify DEFAULT_TEST_SUITES
Date: Thu, 18 Feb 2016 12:22:56 -0600 [thread overview]
Message-ID: <56C60C00.7010606@linux.intel.com> (raw)
In-Reply-To: <1455806750.28376.85.camel@linuxfoundation.org>
So I'm currently running a couple lsb builds, but even though they
aren't finished, I think this patch may be the culprit, since I am
defining DEFAULT_TEST_SUITES_pn-core-image-lsb with exactly the tests
that are failing, so I'll most likely be sending an update soon.
Alex Franco
On 02/18/2016 08:45 AM, Richard Purdie wrote:
> On Wed, 2016-02-17 at 09:55 +0000, Alex Franco wrote:
>> - Add generic variables to reuse values in default test suites
>> - Add more default test suites variables
>> - Modify existing test suites to use generic vars when possible
>>
>> [YOCTO #8410]
>>
>> Alex Franco (2):
>> testimage: add DEFAULT_TEST_SUITES for more images
>> testimage: reuse generic test suites
> Results in failures on the autobuilder, e.g.:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/667/steps/Running%20Sanity%20Tests/logs/stdio
>
> (I'm guessing it was from these patches)
>
> Cheers,
>
> Richard
prev parent reply other threads:[~2016-02-18 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:55 [PATCH 0/2] testimage: add/modify DEFAULT_TEST_SUITES Alex Franco
2016-02-17 9:55 ` [PATCH 1/2] testimage: add DEFAULT_TEST_SUITES for more images Alex Franco
2016-02-17 9:55 ` [PATCH 2/2] testimage: reuse generic test suites Alex Franco
2016-02-18 14:45 ` [PATCH 0/2] testimage: add/modify DEFAULT_TEST_SUITES Richard Purdie
2016-02-18 18:22 ` Alex Franco [this message]
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=56C60C00.7010606@linux.intel.com \
--to=alejandro.franco@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--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