From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: RE: [bitbake-devel] [PATCH] runqueue: Fix runall option handling
Date: Mon, 8 Nov 2021 18:37:24 +0000 [thread overview]
Message-ID: <f66cdbb0b09c49d491bbcbf9abfe5c55@axis.com> (raw)
In-Reply-To: <20211108162823.3736163-1-richard.purdie@linuxfoundation.org>
> -----Original Message-----
> From: bitbake-devel@lists.openembedded.org <bitbake-
> devel@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 8 november 2021 17:28
> To: bitbake-devel@lists.openembedded.org
> Subject: [bitbake-devel] [PATCH] runqueue: Fix runall option handling
>
> The previous fix for runall option handling had a small but in it, it
Typo: but -> bug
//Peter
> didn't clear the originally processed task list which meant it was running
> too many tasks. Fix this so the list is reset and rebuild correctly.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> lib/bb/runqueue.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py
> index 7d4cbed775..957c2d1806 100644
> --- a/lib/bb/runqueue.py
> +++ b/lib/bb/runqueue.py
> @@ -933,6 +933,7 @@ class RunQueueData:
> for tid in list(self.runtaskentries.keys()):
> if tid not in runq_build:
> reduced_tasklist.remove(tid)
> + runq_build = {}
>
> for task in self.cooker.configuration.runall:
> if not task.startswith("do_"):
> --
> 2.32.0
prev parent reply other threads:[~2021-11-08 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 16:28 [PATCH] runqueue: Fix runall option handling Richard Purdie
2021-11-08 18:37 ` Peter Kjellerstedt [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=f66cdbb0b09c49d491bbcbf9abfe5c55@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.