From: Zhihang Wei <wzh@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2] testsuite: Add KFAIL to qemuarm64-resolute
Date: Fri, 24 Jul 2026 17:13:25 +0200 [thread overview]
Message-ID: <20260724151325.764371-1-wzh@ilbers.de> (raw)
Currently, the following error occurs when building qemuarm64-resolute:
ERROR: mc:qemuarm64-resolute:example-module-generic-1.0-r0 do_dpkg_build: ExecutionError('/build/tmp/work/ubuntu-resolute-arm64/example-module-generic/1.0-r0/temp/run.dpkg_runbuild.155703', 3, None, None)
The task log shows:
tar: src/Makefile: Cannot open: Function not implemented
tar: src/debian: Cannot mkdir: Function not implemented
tar: src/debian/changelog: Cannot open: Function not implemented
tar: src/debian/control: Cannot open: Function not implemented
tar: src/debian/control.tmpl: Cannot open: Function not implemented
tar: src/debian/postinst: Cannot open: Function not implemented
tar: src/debian/rules: Cannot open: Function not implemented
tar: src/debian/rules.tmpl: Cannot open: Function not implemented
tar: src/example-module.c: Cannot open: Function not implemented
tar: Exiting with failure status due to previous errors
dpkg-source: error: tar -xf - --no-same-permissions --no-same-owner subprocess failed with exit status 2
E: FAILED [dpkg-source died]
This issue started to occur after Ubuntu updated tar to
tar_1.35+dfsg-4ubuntu0.2 and is also present in tar_1.35+dfsg-4ubuntu0.3
and tar_1.35+dfsg-4ubuntu0.4.
Mark this target as KFAIL until the Ubuntu tar issue is fixed.
Signed-off-by: Zhihang Wei <wzh@ilbers.de>
---
Changes since v1:
- Put vm_start test right after the build test case.
testsuite/citest.py | 22 ++++++++++++++++------
1 file changed, 16 insertions(+), 6 deletions(-)
diff --git a/testsuite/citest.py b/testsuite/citest.py
index 613cd789..66aaad65 100644
--- a/testsuite/citest.py
+++ b/testsuite/citest.py
@@ -262,7 +262,6 @@ class CrossTest(CIBaseTest):
'mc:qemuarm64-trixie:isar-image-base',
'mc:qemuarm64-focal:isar-image-base',
'mc:nanopi-neo-efi-bookworm:isar-image-base',
- 'mc:qemuarm64-resolute:isar-image-base',
'mc:qemuamd64-resolute:isar-image-base',
]
@@ -386,23 +385,34 @@ class CrossTest(CIBaseTest):
self.init()
self.vm_start('arm64', 'focal')
- # TODO: broken because of moving to UEFI
- def test_run_arm64_resolute(self):
+ def test_run_amd64_resolute(self):
"""
:avocado: tags=startvm
"""
+ self.init()
+ self.vm_start('amd64', 'resolute')
+
+ def test_cross_arm64_resolute(self):
+ targets = [
+ 'mc:qemuarm64-resolute:isar-image-base',
+ ]
+
self.init()
try:
- self.vm_start('arm64', 'resolute')
+ self.perform_build_test(targets)
except exceptions.TestFail:
self.cancel('KFAIL')
- def test_run_amd64_resolute(self):
+ # TODO: broken because of moving to UEFI
+ def test_run_arm64_resolute(self):
"""
:avocado: tags=startvm
"""
self.init()
- self.vm_start('amd64', 'resolute')
+ try:
+ self.vm_start('arm64', 'resolute')
+ except exceptions.TestFail:
+ self.cancel('KFAIL')
def test_cross_debsrc(self):
targets = [
--
2.39.5
--
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/20260724151325.764371-1-wzh%40ilbers.de.
next reply other threads:[~2026-07-24 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 15:13 Zhihang Wei [this message]
2026-07-28 15:32 ` Zhihang Wei
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=20260724151325.764371-1-wzh@ilbers.de \
--to=wzh@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