From: "Anuj Mittal" <anuj.mittal@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.50][PATCH 0/5] Review request
Date: Thu, 16 Sep 2021 07:19:33 +0800 [thread overview]
Message-ID: <cover.1631747835.git.anuj.mittal@intel.com> (raw)
Please review these changes for 1.50. Tested with oe-core and no issues
seen.
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2592
Thanks,
Anuj
The following changes since commit c7b506d11df78cfc4610db6578745eaa6220b13a:
server: Fix early parsing errors preventing zombie bitbake (2021-09-09 09:41:51 +0100)
are available in the Git repository at:
git://push.openembedded.org/bitbake-contrib stable/1.50-next
Joshua Watt (1):
cooker: Allow upstream for local hash equivalence server
Richard Purdie (4):
runqueue: Avoid deadlock avoidance task graph corruption
runqueue: Fix issues with multiconfig deferred task deadlock messages
runqueue: Improve multiconfig deferred task issues
build: Catch and error upon circular task references
lib/bb/build.py | 2 ++
lib/bb/cooker.py | 7 ++++-
lib/bb/runqueue.py | 67 +++++++++++++++++++++++++++-------------------
3 files changed, 48 insertions(+), 28 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-15 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 23:19 Anuj Mittal [this message]
2021-09-15 23:19 ` [1.50][PATCH 1/5] runqueue: Avoid deadlock avoidance task graph corruption Anuj Mittal
2021-09-15 23:19 ` [1.50][PATCH 2/5] runqueue: Fix issues with multiconfig deferred task deadlock messages Anuj Mittal
2021-09-15 23:19 ` [1.50][PATCH 3/5] cooker: Allow upstream for local hash equivalence server Anuj Mittal
2021-09-15 23:19 ` [1.50][PATCH 4/5] runqueue: Improve multiconfig deferred task issues Anuj Mittal
2021-09-15 23:19 ` [1.50][PATCH 5/5] build: Catch and error upon circular task references Anuj Mittal
-- strict thread matches above, loose matches on Subject: below --
2021-04-26 3:27 [1.50][PATCH 0/5] review request Anuj Mittal
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=cover.1631747835.git.anuj.mittal@intel.com \
--to=anuj.mittal@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 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).