public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 7/7] oeqa/selftest: fix test_force_task so it doesn't taint the entire build
Date: Tue, 23 Dec 2014 16:20:40 +0000	[thread overview]
Message-ID: <7282604.Fxp2EgJ73Q@peggleto-mobl5.ger.corp.intel.com> (raw)
In-Reply-To: <14ec1988201a830d4da2328607f499fe6c6d5f26.1419350817.git.paul.eggleton@linux.intel.com>

On Tuesday 23 December 2014 16:08:48 Paul Eggleton wrote:
> Using -f sets a taint on the specified task

Hmm, that would be -C in this case, not -f. I've adjusted the commit message 
on the branch.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2014-12-23 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 16:08 [PATCH 0/7] oe-selftest QA test fixes Paul Eggleton
2014-12-23 16:08 ` [PATCH 1/7] oeqa/utils: replace some tabs with spaces Paul Eggleton
2014-12-23 16:08 ` [PATCH 2/7] oeqa/utils: fix testcase decorator to allow calling tests individually Paul Eggleton
2014-12-23 16:08 ` [PATCH 3/7] oeqa/selftest: fix test_event_handler for changes in bitbake output Paul Eggleton
2014-12-23 16:08 ` [PATCH 4/7] oeqa/selftest: skip test_incremental_image_generation if not using rpm Paul Eggleton
2014-12-23 16:08 ` [PATCH 5/7] oeqa/selftest: improve failure messages for devtool tests Paul Eggleton
2014-12-23 16:08 ` [PATCH 6/7] oeqa/selftest: populate pkgdata/shlibs in test_recipetool_create_git Paul Eggleton
2014-12-23 16:08 ` [PATCH 7/7] oeqa/selftest: fix test_force_task so it doesn't taint the entire build Paul Eggleton
2014-12-23 16:20   ` Paul Eggleton [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=7282604.Fxp2EgJ73Q@peggleto-mobl5.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.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