All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/2] bitbake: fix setscene task start/failure handling
Date: Tue, 28 Feb 2012 17:11:50 +0000	[thread overview]
Message-ID: <2039899.xPofPYZzs0@helios> (raw)
In-Reply-To: <CAEsOVNcu_viCVVsoO9jg-eB9bA8GYBs33B4_7KYidqyuh9Ft8w@mail.gmail.com>

On Tuesday 28 February 2012 16:32:29 McClintock Matthew-B29882 wrote:
> I was referring to when the setscene tasks fails and we emit an ERROR
> when it's not really a fatal error as we can just rerun the real task.
> It's still an "issue" - but when I check my build logs for issues I
> grep for ERROR and I'd rather leave ERROR for FATAL ERRORS.

I agree and I'm happy to look at that as a separate issue if it is indeed 
still occurring in master; my immediate concern was not getting any message at 
all though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-02-28 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 18:54 [PATCH 0/2] bitbake patches Paul Eggleton
2012-02-27 18:54 ` [PATCH 1/2] bitbake: fix setscene task start/failure handling Paul Eggleton
2012-02-27 19:15   ` McClintock Matthew-B29882
2012-02-27 23:45     ` Paul Eggleton
2012-02-28 16:32       ` McClintock Matthew-B29882
2012-02-28 17:11         ` Paul Eggleton [this message]
2012-02-27 18:54 ` [PATCH 2/2] bitbake/runqueue: make dry-run do everything except execute Paul Eggleton

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=2039899.xPofPYZzs0@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=B29882@freescale.com \
    --cc=bitbake-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.