From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Petter Mabäcker" <petter@technux.se>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake: runqueue: add warning in invalidate task
Date: Mon, 29 Jul 2013 16:02:45 +0100 [thread overview]
Message-ID: <3332347.m6ksvx6N6L@helios> (raw)
In-Reply-To: <c8e2317302a86e93bdbe8746b02f0a42be91abcf.1375088734.git.petter@technux.se>
Hi Petter,
On Monday 29 July 2013 11:19:31 Petter Mabäcker wrote:
> Add a warning if 'bitbake -C' is executed with a task that does not
> exist.
>
> Fixes [YOCTO #4877]
>
> Signed-off-by: Petter Mabäcker <petter@technux.se>
> ---
> bitbake/lib/bb/runqueue.py | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
> index fce08ee..539e9af 100644
> --- a/bitbake/lib/bb/runqueue.py
> +++ b/bitbake/lib/bb/runqueue.py
> @@ -720,6 +720,9 @@ class RunQueueData:
>
> def invalidate_task(fn, taskname, error_nostamp):
> taskdep = self.dataCache.task_deps[fn]
> + fnid = self.taskData.getfn_id(fn)
> + if taskname not in taskData.tasks_lookup[fnid]:
> + logger.warn("Task %s does not exist, invalidate this task
> will have no effect" % taskname) if 'nostamp' in taskdep and taskname in
> taskdep['nostamp']: if error_nostamp:
> bb.fatal("Task %s is marked nostamp, cannot invalidate
> this task" % taskname)
This has now been merged with a slight tweak to the message and shortlog.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-07-29 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 9:18 [PATCH 0/1] bitbake: runqueue: add warning in invalidate task Petter Mabäcker
2013-07-29 9:19 ` [PATCH 1/1] " Petter Mabäcker
2013-07-29 15:02 ` 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=3332347.m6ksvx6N6L@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=petter@technux.se \
/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.