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: Mon, 27 Feb 2012 23:45:47 +0000 [thread overview]
Message-ID: <2548258.gq2qYr9CFK@helios> (raw)
In-Reply-To: <CAEsOVNdC8Xh4E32Lep8g0BjNXFQHJzGVZ3s3gTied6UYqNnCYA@mail.gmail.com>
On Monday 27 February 2012 19:15:46 McClintock Matthew-B29882 wrote:
> On Mon, Feb 27, 2012 at 12:54 PM, Paul Eggleton
>
> <paul.eggleton@linux.intel.com> wrote:
> > + if isinstance(event, bb.runqueue.sceneQueueTaskFailed):
> > + logger.warn("Setscene task %s (%s) failed with exit code
> > '%s' - real task will be run instead", +
> > event.taskid, event.taskstring, event.exitcode)
> This removes the "ERROR:" message, right?
If a failure logs an ERROR itself then no, this would still be printed.
However, in the case of an error situation such as one I simulated (unable to
read from the sstate-cache file) nothing was being printed at all, which is not
particularly helpful. Thus this part of the change.
Cheers,
Paull
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-27 23:55 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 [this message]
2012-02-28 16:32 ` McClintock Matthew-B29882
2012-02-28 17:11 ` Paul Eggleton
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=2548258.gq2qYr9CFK@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox