From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex DAMIAN <alexandru.damian@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 06/13] bitbake: build: add link to logfile for Task events
Date: Tue, 10 Sep 2013 15:01:49 +0100 [thread overview]
Message-ID: <1378821709.3484.156.camel@ted> (raw)
In-Reply-To: <4509f2ed87581c11ff26c10586f37516b4766503.1378743829.git.alexandru.damian@intel.com>
On Mon, 2013-09-09 at 17:40 +0100, Alex DAMIAN wrote:
> From: Alexandru DAMIAN <alexandru.damian@intel.com>
>
> We add a pointer to the logfile for Task events, so
> that we can trace that in the Bitbake database
>
> Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
> ---
> bitbake/lib/bb/build.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/bitbake/lib/bb/build.py b/bitbake/lib/bb/build.py
> index 1265bdc..4abbe48 100644
> --- a/bitbake/lib/bb/build.py
> +++ b/bitbake/lib/bb/build.py
> @@ -73,6 +73,7 @@ class TaskBase(event.Event):
> self._task = t
> self._package = d.getVar("PF", True)
> self._file = d.getVar("FILE", True)
> + self.logfile = d.getVar("BB_LOGFILE", True)
> self.taskfile = self._file
> self.taskname = self._task
> event.Event.__init__(self)
This leaves the TaskFailed() events still manually passing in logfile as
a separate parameter. I think we might as well adjust the code to always
pass the logfile to the events instead of this, mainly as it makes it
explictly clear where and when the logfile is uses. BB_LOGFILE is really
meant more for external usage than for bitbake itself.
Cheers,
Richard
next prev parent reply other threads:[~2013-09-10 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 16:40 [PATCH 00/13] webhob related changes in bitbake Alex DAMIAN
2013-09-09 16:40 ` [PATCH 01/13] bitbake: cooker: clean up code and avoid duplication Alex DAMIAN
2013-09-09 16:40 ` [PATCH 02/13] bitbake: runqueue: Add runQueueTaskSkipped event Alex DAMIAN
2013-09-09 16:40 ` [PATCH 03/13] bitbake: runqueue: added prebuild detailed information Alex DAMIAN
2013-09-09 16:40 ` [PATCH 04/13] bitbake: runqueue, build: event data change Alex DAMIAN
2013-09-10 13:52 ` Richard Purdie
2013-09-09 16:40 ` [PATCH 05/13] bitbake: runqueue: add sceneQueueTaskCompleted event Alex DAMIAN
2013-09-09 16:40 ` [PATCH 06/13] bitbake: build: add link to logfile for Task events Alex DAMIAN
2013-09-10 14:01 ` Richard Purdie [this message]
2013-09-09 16:40 ` [PATCH 07/13] bitbake: cooker, command: add a command to return global data Alex DAMIAN
2013-09-13 14:52 ` Richard Purdie
2013-09-09 16:40 ` [PATCH 08/13] bitbake: cooker: use prepareTreeData when computing environment Alex DAMIAN
2013-09-09 16:41 ` [PATCH 09/13] bitbake: event: do not abort on UI handlers error Alex DAMIAN
2013-09-09 16:49 ` Richard Purdie
2013-09-09 16:41 ` [PATCH 10/13] bitbake: add SinglePackageInfo event Alex DAMIAN
2013-09-09 16:41 ` [PATCH 11/13] bitbake: event: adding an event to pass build file sizes Alex DAMIAN
2013-09-09 16:41 ` [PATCH 12/13] bitbake: xmlrpc: delete unused code BitBakeUIEventServer Alex DAMIAN
2013-09-09 16:41 ` [PATCH 13/13] bitbake: cooker: add extra recipe information Alex DAMIAN
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=1378821709.3484.156.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandru.damian@intel.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.