From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "kergoth@gmail.com" <kergoth@gmail.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Larson, Chris" <chris.larson@siemens.com>,
"chris.larson@seimens.com" <chris.larson@seimens.com>
Subject: Re: [PATCH 7/9] cibuilder.py: add -S support to the bitbake method
Date: Wed, 3 Apr 2024 07:12:50 +0000 [thread overview]
Message-ID: <d8b3600286a4260632feb277c8b0c83cee856cff.camel@siemens.com> (raw)
In-Reply-To: <20240402172813.418770-8-chris.larson@siemens.com>
On Tue, 2024-04-02 at 17:28 +0000, kergoth@gmail.com wrote:
> From: Christopher Larson <chris.larson@seimens.com>
>
> This allows a test writer to call `bitbake -S none`, to generate
> signature data in tmp/stamps.
Is there a particular reason why we don't use the long version of the
parameters? In case this parameter ever changes, it is much easier to
find all locations if the long form is used.
Felix
>
> Signed-off-by: Christopher Larson <chris.larson@siemens.com>
> ---
> testsuite/cibuilder.py | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/testsuite/cibuilder.py b/testsuite/cibuilder.py
> index fa30c2f5..e968d14d 100755
> --- a/testsuite/cibuilder.py
> +++ b/testsuite/cibuilder.py
> @@ -188,7 +188,7 @@ def move_in_build_dir(self, src, dst):
> if os.path.exists(self.build_dir + '/' + src):
> shutil.move(self.build_dir + '/' + src, self.build_dir +
> '/' + dst)
>
> - def bitbake(self, target, bitbake_cmd=None, **kwargs):
> + def bitbake(self, target, bitbake_cmd=None, sig_handler=None,
> **kwargs):
> self.check_init()
>
> self.log.info('===================================================')
> self.log.info('Building ' + str(target))
> @@ -200,6 +200,9 @@ def bitbake(self, target, bitbake_cmd=None,
> **kwargs):
> if bitbake_cmd:
> cmdline.append('-c')
> cmdline.append(bitbake_cmd)
> + if sig_handler:
> + cmdline.append('-S')
> + cmdline.append(sig_handler)
> if isinstance(target, list):
> cmdline.extend(target)
> else:
> --
> 2.39.2
>
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-04-03 7:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 17:28 [PATCH 0/9] Add more signature cachability tests to the testsuite kergoth
2024-04-02 17:28 ` [PATCH 1/9] isar-bootstrap: avoid forced early expansion of key vars kergoth
2024-04-03 6:54 ` MOESSBAUER, Felix
2024-04-03 21:42 ` Larson, Chris
2024-04-04 6:26 ` MOESSBAUER, Felix
2024-04-02 17:28 ` [PATCH 2/9] isar-ci-ssh-setup: avoid abs path in signatures kergoth
2024-04-02 17:28 ` [PATCH 3/9] isar-sstate: lint: check for absolute paths in SRC_URI kergoth
2024-04-03 6:56 ` MOESSBAUER, Felix
2024-04-02 17:28 ` [PATCH 4/9] isar-sstate: lint: add support for checking stamps kergoth
2024-04-03 7:02 ` MOESSBAUER, Felix
2024-04-03 21:42 ` Larson, Chris
2024-04-02 17:28 ` [PATCH 5/9] isar-sstate: lint: ignore more image tasks kergoth
2024-04-03 7:08 ` MOESSBAUER, Felix
2024-04-02 17:28 ` [PATCH 6/9] isar-sstate: add --excluded-tasks argument kergoth
2024-04-03 7:10 ` MOESSBAUER, Felix
2024-04-03 21:41 ` Larson, Chris
2024-04-03 21:44 ` Larson, Chris
2024-04-04 6:28 ` MOESSBAUER, Felix
2024-04-02 17:28 ` [PATCH 7/9] cibuilder.py: add -S support to the bitbake method kergoth
2024-04-03 7:12 ` MOESSBAUER, Felix [this message]
2024-04-03 21:41 ` Larson, Chris
2024-04-02 17:28 ` [PATCH 8/9] testsuite: add perform_signature_lint method kergoth
2024-04-02 17:28 ` [PATCH 9/9] testsuite: add signature cachability checks kergoth
2024-04-05 16:31 [PATCHv2 0/9] Add more signature cachability tests to the testsuite chris.larson
2024-04-05 16:31 ` [PATCH 7/9] cibuilder.py: add -S support to the bitbake method chris.larson
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=d8b3600286a4260632feb277c8b0c83cee856cff.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=chris.larson@seimens.com \
--cc=chris.larson@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=kergoth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox