public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Clara Kowalsky <clara.kowalsky@siemens.com>
Subject: [PATCH 2/4] image: include rootfs manifests in sstate artifacts
Date: Thu, 29 Oct 2026 11:20:25 +0100	[thread overview]
Message-ID: <20261029102027.1974884-2-clara.kowalsky@siemens.com> (raw)
In-Reply-To: <20261029102027.1974884-1-clara.kowalsky@siemens.com>

do_rootfs_install writes the manifest and dpkg_status files to
DEPLOY_DIR_IMAGE, but sstate captures DEPLOYDIR. After restoring the
sstate, the files are missing from the deploy directory.
Running:

scripts/run-tests.sh testsuite/citest.py:SstateTest.test_sstate \
  -p rootless=0 --debug

fails with:

ERROR| mc:qemuamd64-bullseye:isar-image-base: files missing from deploy
dir after rebuild with sstate cache:
{'/isar/build/build-sstate/tmp/deploy/images/qemuamd64/
isar-image-base-debian-bullseye-qemuamd64.manifest',
'/isar/build/build-sstate/tmp/deploy/images/qemuamd64/
isar-image-base-debian-bullseye-qemuamd64.dpkg_status'}

This error happens independently of commit "testsuite: fix sstate test
with relocated build directory". Fix this by defaulting both output
directories to DEPLOYDIR, so sstate captures and restores the files.

Fixes: c7a637508ac6 ("rootfs: fold do_rootfs_postprocess task into do_rootfs_install")
Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
---
 meta/classes-recipe/image.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes-recipe/image.bbclass b/meta/classes-recipe/image.bbclass
index d9125d05..ce19ae1c 100644
--- a/meta/classes-recipe/image.bbclass
+++ b/meta/classes-recipe/image.bbclass
@@ -106,8 +106,8 @@ ROOTFS_FEATURES += "\
     "
 ROOTFS_PACKAGES += "${IMAGE_PREINSTALL} ${@isar_multiarch_packages('IMAGE_INSTALL', d)}"
 ROOTFS_VARDEPS += "IMAGE_INSTALL"
-ROOTFS_MANIFEST_DEPLOY_DIR ?= "${DEPLOY_DIR_IMAGE}"
-ROOTFS_DPKGSTATUS_DEPLOY_DIR ?= "${DEPLOY_DIR_IMAGE}"
+ROOTFS_MANIFEST_DEPLOY_DIR ?= "${DEPLOYDIR}"
+ROOTFS_DPKGSTATUS_DEPLOY_DIR ?= "${DEPLOYDIR}"
 ROOTFS_PACKAGE_SUFFIX ?= "${PN}-${DISTRO}-${MACHINE}"
 
 CACHE_DEB_SRC = "${@bb.utils.contains('BASE_REPO_FEATURES', 'cache-deb-src', '1', '0', d)}"
-- 
2.55.0

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20261029102027.1974884-2-clara.kowalsky%40siemens.com.

  reply	other threads:[~2026-10-29 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 10:20 [PATCH 1/4] testsuite: fix sstate test with relocated build directory 'Clara Kowalsky' via isar-users
2026-10-29 10:20 ` 'Clara Kowalsky' via isar-users [this message]
2026-10-29 10:20 ` [PATCH 3/4] initramfs: include manifest in sstate artifacts 'Clara Kowalsky' via isar-users
2026-10-29 10:20 ` [PATCH 4/4] meta-test: stage rootfs CI manifest in DEPLOYDIR 'Clara Kowalsky' via isar-users

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=20261029102027.1974884-2-clara.kowalsky@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.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