From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v6 5/9] CI: Fix used chroot recipe name
Date: Fri, 21 Jul 2023 07:53:58 +0200 [thread overview]
Message-ID: <20230721055402.13764-6-ubely@ilbers.de> (raw)
In-Reply-To: <20230721055402.13764-1-ubely@ilbers.de>
From: Anton Mikanovich <amikan@ilbers.de>
We've moved to schroot, so need to adjust recipe names for sstate test
case in CI.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
testsuite/cibase.py | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/testsuite/cibase.py b/testsuite/cibase.py
index df8b350e..d9641377 100755
--- a/testsuite/cibase.py
+++ b/testsuite/cibase.py
@@ -151,7 +151,7 @@ class CIBaseTest(CIBuilder):
if not all([
check_executed_tasks('isar-bootstrap-target',
['do_bootstrap_setscene', '!do_bootstrap']),
- check_executed_tasks('buildchroot-target',
+ check_executed_tasks('sbuild-chroot-target',
['do_rootfs_install_setscene', '!do_rootfs_install']),
check_executed_tasks('isar-image-base-*',
['do_rootfs_install_setscene', '!do_rootfs_install'])
@@ -175,8 +175,8 @@ class CIBaseTest(CIBuilder):
if not all([
check_executed_tasks('isar-bootstrap-target',
['do_bootstrap_setscene']),
- check_executed_tasks('buildchroot-target',
- ['!do_buildchroot_deploy']),
+ check_executed_tasks('sbuild-chroot-target',
+ ['!do_sbuildchroot_deploy']),
check_executed_tasks('hello',
['do_dpkg_build_setscene', 'do_deploy_deb', '!do_dpkg_build'])
]):
@@ -189,7 +189,7 @@ class CIBaseTest(CIBuilder):
if not all([
check_executed_tasks('isar-bootstrap-target',
['do_bootstrap_setscene', '!do_bootstrap']),
- check_executed_tasks('buildchroot-target',
+ check_executed_tasks('sbuild-chroot-target',
['do_rootfs_install_setscene', '!do_rootfs_install']),
check_executed_tasks('hello',
['do_fetch', 'do_dpkg_build']),
--
2.20.1
next prev parent reply other threads:[~2023-07-21 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 5:53 [PATCH v6 0/9] Imager schroot migration Uladzimir Bely
2023-07-21 5:53 ` [PATCH v6 1/9] isar-apt: Move cleanup to postprocessing Uladzimir Bely
2023-07-21 5:53 ` [PATCH v6 2/9] imager: Migrate from buildchroot to schroot Uladzimir Bely
2023-07-21 5:53 ` [PATCH v6 3/9] imager: Move image types " Uladzimir Bely
2023-07-21 5:53 ` [PATCH v6 4/9] imager: Split imager deps between image types Uladzimir Bely
2023-07-21 5:53 ` Uladzimir Bely [this message]
2023-07-21 5:53 ` [PATCH v6 6/9] meta: Remove buildchroot Uladzimir Bely
2023-07-21 5:54 ` [PATCH v6 7/9] dpkg-gbp: Remove unused mounts Uladzimir Bely
2023-07-21 5:54 ` [PATCH v6 8/9] doc: Update chroot documentation Uladzimir Bely
2023-07-21 5:54 ` [PATCH v6 9/9] RECIPE-API-CHANGELOG.md: Describe imager changes Uladzimir Bely
2023-08-25 4:20 ` [PATCH v6 0/9] Imager schroot migration Uladzimir Bely
2023-09-12 8:25 ` Uladzimir Bely
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=20230721055402.13764-6-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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