bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fabio.Berton@criticaltechworks.com, bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [1.46][PATCH 0/6] Backport multiconfig deferred fixes
Date: Fri, 17 Feb 2023 15:08:06 +0000	[thread overview]
Message-ID: <4abb802d890f3b69e54d2d590c7a2dc613d46c6e.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230215104321.1665505-1-fabio.berton@criticaltechworks.com>

On Wed, 2023-02-15 at 10:43 +0000, Fabio Berton via
lists.openembedded.org wrote:
> This series is a backport to improve multiconfig builds in 1.46 branch. Without
> these patches, some tasks run more than once for the native recipe, for example,
> the do_patch task tries to apply the same patch to each machine.  With these
> patches I can't see any duplicate tasks, and it looks like the task was properly
> deferred by bitbake.
> 
> Richard Purdie (6):
>   runqueue: Fix multiconfig deferred task sstate validity caching issue
>   runqueue: Handle deferred task rehashing in multiconfig builds
>   runqueue: Improve multiconfig deferred task issues
>   runqueue: Avoid deadlock avoidance task graph corruption
>   runqueue: Fix issues with multiconfig deferred task deadlock messages
>   runqueue: Ensure deferred tasks are sorted by multiconfig
> 
>  lib/bb/runqueue.py | 88 +++++++++++++++++++++++++++++-----------------
>  1 file changed, 55 insertions(+), 33 deletions(-)
> 


For the record, I'm happier fixing this in 1.46 now that we tracked
down that last issue ("Ensure deferred tasks are sorted by
multiconfig") since that was the real bug that was causing a lot of the
problems.

Cheers,

Richard


      parent reply	other threads:[~2023-02-17 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 10:43 [1.46][PATCH 0/6] Backport multiconfig deferred fixes Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 1/6] runqueue: Fix multiconfig deferred task sstate validity caching issue Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 2/6] runqueue: Handle deferred task rehashing in multiconfig builds Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 3/6] runqueue: Improve multiconfig deferred task issues Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 4/6] runqueue: Avoid deadlock avoidance task graph corruption Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 5/6] runqueue: Fix issues with multiconfig deferred task deadlock messages Fabio Berton
2023-02-15 10:43 ` [1.46][PATCH 6/6] runqueue: Ensure deferred tasks are sorted by multiconfig Fabio Berton
2023-02-17 15:08 ` 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=4abb802d890f3b69e54d2d590c7a2dc613d46c6e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Fabio.Berton@criticaltechworks.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;
as well as URLs for NNTP newsgroup(s).