From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Cal Sullivan <california.l.sullivan@intel.com>,
openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCHv2 1/3] runtime/cases/ptest.py: do not require ptest-pkgs in IMAGE_FEATURES
Date: Thu, 4 Jan 2018 11:20:48 +0200 [thread overview]
Message-ID: <25dc03f3-8f01-9da5-cfcf-2f02fcee4c97@linux.intel.com> (raw)
In-Reply-To: <9db5a39d-2057-01b7-67a3-09845a119fea@intel.com>
On 01/03/2018 10:42 PM, Cal Sullivan wrote:
> Looks like it doesn't skip the test correctly:
>> + status, output = self.target.run('which ptest-runner', 0)
>> + if len(output) == 0:
>> + self.skipTest("No -ptest packages are installed in the image")
>> +
Looks like there are no less than three versions of 'which' (busybox,
debianutils, gnu), and one of them is noisy when the argument is not
found. I'll fix and resend the patchset.
Alex
prev parent reply other threads:[~2018-01-04 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 12:44 [PATCHv2 1/3] runtime/cases/ptest.py: do not require ptest-pkgs in IMAGE_FEATURES Alexander Kanavin
2017-12-21 12:44 ` [PATCHv2 2/3] testimage.bbclass: add ptest to the list of runtime tests whenever possible Alexander Kanavin
2018-01-03 14:09 ` Richard Purdie
2017-12-21 12:45 ` [PATCHv2 3/3] runtime/cases/ptest.py: fail when ptests fail on target Alexander Kanavin
2018-01-03 20:42 ` [PATCHv2 1/3] runtime/cases/ptest.py: do not require ptest-pkgs in IMAGE_FEATURES Cal Sullivan
2018-01-04 9:20 ` 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=25dc03f3-8f01-9da5-cfcf-2f02fcee4c97@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=california.l.sullivan@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