From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex Franco <alejandro.franco@linux.intel.com>
Cc: david.nystrom@enea.com, clarson@kergoth.com,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCHv3 1/1] Allow bitbake commands starting with do_
Date: Tue, 01 Sep 2015 22:44:22 +0100 [thread overview]
Message-ID: <1441143862.24871.24.camel@linuxfoundation.org> (raw)
In-Reply-To: <1441054569-1661-2-git-send-email-alejandro.franco@linux.intel.com>
On Mon, 2015-08-31 at 15:56 -0500, Alex Franco wrote:
> The output of "bitbake, -c listtasks pkg" lists tasks with their real names
> (starting with "do_"), but then "bitbake -c do_task" fails, as "do_" always
> gets unconditionally prepended to task names. This patch handles this error
> by always removing "do_" from the beginning of task names when the runqueue
> is being constructed.
>
> [YOCTO #7818]
>
> Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com>
> ---
> bitbake/lib/bb/runqueue.py | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
> index 0f99e5a..7b25e31 100644
> --- a/bitbake/lib/bb/runqueue.py
> +++ b/bitbake/lib/bb/runqueue.py
> @@ -634,6 +634,10 @@ class RunQueueData:
>
> fnid = taskData.build_targets[targetid][0]
> fn = taskData.fn_index[fnid]
> +
> + if target[1].startswith("do_"):
> + target[1] = target[1][3:]
> +
> self.target_pairs.append((fn, target[1]))
>
> if fnid in taskData.failed_fnids:
I tried this on the autobuilder and we saw cascades of failures, e.g:
https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/468/steps/BuildImages/logs/stdio
so clearly we need more thought on this. I prefer the .startswith over
the regex as in general its much faster code than loading the re engine.
Cheers,
Richard
prev parent reply other threads:[~2015-09-01 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:56 [PATCHv3 0/1] Allow bitbake commands starting with do_ Alex Franco
2015-08-31 20:56 ` [PATCHv3 1/1] " Alex Franco
2015-09-01 21:44 ` Richard Purdie [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=1441143862.24871.24.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alejandro.franco@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=david.nystrom@enea.com \
/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.