From: Julien Stephan <jstephan@baylibre.com>
To: openembedded-core@lists.openembedded.org
Cc: Julien Stephan <jstephan@baylibre.com>
Subject: [PATCH v5 0/5] Add bblock helper scripts
Date: Mon, 25 Sep 2023 10:04:47 +0200 [thread overview]
Message-ID: <20230925080452.803540-1-jstephan@baylibre.com> (raw)
Hi all,
This is v5 for bblock script.
Improvement from v4:
* Fix self test error reported by autobuilder
* Allow to specify task with/without the "do_" prefix:
example: bblock bc -t compile,do_install
* Fix test_lock_single_recipe_all_tasks
* Fix getTaskSignatures: now retrieve all tasks and filter out the
* setscene and nostamps ones
Limitations:
* Silently does nothing if given task doesn't exist
* Silently does nothing when resetting a recipe that doesn't exist
Improvement from v3:
* Add self test
* Add a new "info" level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK: this allows to
display a Note when recipe contains locked task(s)
Improvement from v2:
* Add a function in bb.cooker to compute task signatures
* Replace the findSigInfo function by the new created one. This has the
following advantages:
* findSigInfo needs the task to be already built to get the siginfo
file, meaning we cannot lock a recipe on a fresh build
* we can now generate the signatures for all available task of a given
recipe
* Check if a given task is already locked. If so, don't duplicate
entry in bblock.conf
Limitations:
* Needs to taint tasks that are locked, to display a warning
* I may be still missing some checks on user input
* Silently does nothing if given task doesn't exist
* Silently does nothing when resetting a recipe that doesn't exist
I did some tests using qemux86-64 and qemuarm but I may be missing some
corner cases.
Improvement from V1:
* Signatures are now package architecture specific meaning that if you
switch MACHINE, the lock sig will not be taken into account
* I added the -r option to unlock recipes
* I added a -d option to display the current bblock.conf
* Added an include directive for conf/bblock.conf inside bitbake.conf
* Added -t option to specify the tasks to lock/unlock
Limitations:
* I may be still missing some checks on user input
* I need to find a way to get the list of tasks ( by default still lock
only the do_compile for now, unless -t is specified)
* Do not check if a particular recipe/task is already locked when trying
to add lock. So entries may appear multiple times
* We still need the signature of the tasks to be already computed before
locking. Need to find a way to generate it if missing
V3: https://lists.openembedded.org/g/openembedded-core/message/184932
V2: https://lists.openembedded.org/g/openembedded-core/message/184697
V1: https://lists.openembedded.org/g/openembedded-core/message/184584
My branch is available here [1]
Cheers
Julien
[1]: https://git.yoctoproject.org/poky-contrib/commit/?h=jstephan/bblock
Julien Stephan (5):
bitbake.conf: include bblock.conf
bitbake: cooker: add a new function to retrieve task signatures
sstatesig: add a new info level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK
scripts/bblock: add a script to lock/unlock recipes
oeqa/selftest/bblock: add self test for bblock tool
bitbake/lib/bb/command.py | 6 +
bitbake/lib/bb/cooker.py | 31 ++++
bitbake/lib/bb/event.py | 8 +
meta/conf/bitbake.conf | 1 +
meta/lib/oe/sstatesig.py | 18 ++-
meta/lib/oeqa/selftest/cases/bblock.py | 201 +++++++++++++++++++++++++
scripts/bblock | 184 ++++++++++++++++++++++
7 files changed, 448 insertions(+), 1 deletion(-)
create mode 100644 meta/lib/oeqa/selftest/cases/bblock.py
create mode 100755 scripts/bblock
--
2.41.0
next reply other threads:[~2023-09-25 8:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 8:04 Julien Stephan [this message]
2023-09-25 8:04 ` [PATCH v5 1/5] bitbake.conf: include bblock.conf Julien Stephan
2023-09-25 8:04 ` [PATCH v5 2/5] bitbake: cooker: add a new function to retrieve task signatures Julien Stephan
2023-09-25 8:04 ` [PATCH v5 3/5] sstatesig: add a new info level for SIGGEN_LOCKEDSIGS_TASKSIG_CHECK Julien Stephan
2023-09-25 8:04 ` [PATCH v5 4/5] scripts/bblock: add a script to lock/unlock recipes Julien Stephan
2023-09-25 8:04 ` [PATCH v5 5/5] oeqa/selftest/bblock: add self test for bblock tool Julien Stephan
2023-09-27 10:16 ` [OE-core] [PATCH v5 0/5] Add bblock helper scripts Alexandre Belloni
2023-09-27 12:47 ` Julien Stephan
2023-09-27 12:58 ` Alexandre Belloni
2023-09-27 12:59 ` Alexander Kanavin
2023-09-27 13:02 ` Julien Stephan
2023-09-27 13:04 ` Alexandre Belloni
2023-09-27 21:17 ` Richard Purdie
2023-09-30 14:13 ` Julien Stephan
2023-10-02 10:24 ` Jose Quaresma
2023-10-05 8:02 ` Julien Stephan
2023-10-06 10:56 ` Alexandre Belloni
2023-10-06 10:59 ` Richard Purdie
2023-10-06 12:37 ` Julien Stephan
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=20230925080452.803540-1-jstephan@baylibre.com \
--to=jstephan@baylibre.com \
--cc=openembedded-core@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 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.