From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target
Date: Wed, 20 Dec 2017 22:11:15 +0200 [thread overview]
Message-ID: <9aab6e2c-eb38-efa2-d191-7d7b3e03b1f7@linux.intel.com> (raw)
In-Reply-To: <CAJTo0Lbj3Qr888ai7c9jG84_gLyt9A5Uu-PzbtBMNqD2fq8cKg@mail.gmail.com>
On 12/20/2017 07:23 PM, Burton, Ross wrote:
> So the context was that so many ptests were failing that the test
> couldn't be done automatically and expected to succeed. Bugs were filed
> and the problem chipped away at, but last I looked it wasn't in a state
> to be enabled.
>
> If a core-image-sato passes with ptests enabled then that's great, but
> I'll be surprised if it does!
It doesn't. In fact, it never finishes, because bluez ptest hangs
forever. That shouldn't be a problem though, because ptests are not
included by default in any of the standard images, and so the test is
simply skipped (see patch 1 of 3). The point of this patch is to
eliminate misleading passing behaviour when people do include ptests -
either for everything in their image or for specific packages they
maintain, and want, for example, to check for regressions on version
upgrades.
Alex
prev parent reply other threads:[~2017-12-20 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 15:45 [PATCH 1/3] runtime/cases/ptest.py: do not require ptest-pkgs in IMAGE_FEATURES Alexander Kanavin
2017-12-20 15:45 ` [PATCH 2/3] testimage.bbclass: add ptest to the list of runtime tests whenever possible Alexander Kanavin
2017-12-20 15:45 ` [PATCH 3/3] runtime/cases/ptest.py: fail when ptests fail on target Alexander Kanavin
2017-12-20 17:23 ` Burton, Ross
2017-12-20 20:11 ` Alexander Kanavin [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=9aab6e2c-eb38-efa2-d191-7d7b3e03b1f7@linux.intel.com \
--to=alexander.kanavin@linux.intel.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