From: Zhihang Wei <wzh@ilbers.de>
To: Cedric Hombourger <cedric.hombourger@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 0/4] Add test-cases for dracut-based initrds
Date: Wed, 12 Nov 2025 17:37:08 +0100 [thread overview]
Message-ID: <14c15020-fbdc-42f4-9df9-3ec87f0884ef@ilbers.de> (raw)
In-Reply-To: <20251101111326.600581-1-cedric.hombourger@siemens.com>
Applied to next, thanks.
Best regards,
Zhihang
On 11/1/25 12:13, 'Cedric Hombourger' via isar-users wrote:
> [1] is adding support for dracut as the initrd generator. That
> patch series missed to add tests. Add several smoke tests.
> Note that a small change (add "set -e" to the sudo script used
> to generate the initrd) is needed for all initrd tests to pass.
>
> Build results with pristine "Add support for dracut" v5:
>
> builder@ed1e0b7e8d4e:/work/testsuite$ trun --max-parallel-tasks=1 -p sstate=1 -t initrd citest.py
> JOB ID : f1601d733e2a811ad04738eef7a1bdba28dbcd52
> JOB LOG : /tmp/tmp72bozbdi/avocado/job-results/job-2025-11-01T10.19-f1601d7/job.log
> (1/5) citest.py:InitRdTest.test_dracut_in_image: STARTED
> (1/5) citest.py:InitRdTest.test_dracut_in_image: PASS (206.52 s)
> (2/5) citest.py:InitRdTest.test_dracut_build_initrd: STARTED
> (2/5) citest.py:InitRdTest.test_dracut_build_initrd: PASS (57.86 s)
> (3/5) citest.py:InitRdTest.test_dracut_build_failure: STARTED
> (3/5) citest.py:InitRdTest.test_dracut_build_failure: FAIL: Bitbake suceeded but was expected to fail! (159.91 s)
> (4/5) citest.py:InitRdCrossTests.test_dracut_in_image: STARTED
> (4/5) citest.py:InitRdCrossTests.test_dracut_in_image: PASS (1000.05 s)
> (5/5) citest.py:InitRdCrossTests.test_dracut_build_initrd: STARTED
> (5/5) citest.py:InitRdCrossTests.test_dracut_build_initrd: PASS (233.79 s)
> RESULTS : PASS 4 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
> JOB TIME : 1663.01 s
>
> With the suggested change:
>
> builder@ed1e0b7e8d4e:/work/testsuite$ trun --max-parallel-tasks=1 -p sstate=1 -t initrd citest.py
> JOB ID : dc55f13f05f5997669aaccce9760bca4bed7a400
> JOB LOG : /tmp/tmp72bozbdi/avocado/job-results/job-2025-11-01T11.54-dc55f13/job.log
> (1/5) citest.py:InitRdTest.test_dracut_in_image: STARTED
> (1/5) citest.py:InitRdTest.test_dracut_in_image: PASS (117.49 s)
> (2/5) citest.py:InitRdTest.test_dracut_build_initrd: STARTED
> (2/5) citest.py:InitRdTest.test_dracut_build_initrd: PASS (30.33 s)
> (3/5) citest.py:InitRdTest.test_dracut_build_failure: STARTED
> (3/5) citest.py:InitRdTest.test_dracut_build_failure: PASS (73.31 s)
> (4/5) citest.py:InitRdCrossTests.test_dracut_in_image: STARTED
>
> (4/5) citest.py:InitRdCrossTests.test_dracut_in_image: PASS (430.85 s)
> (5/5) citest.py:InitRdCrossTests.test_dracut_build_initrd: STARTED
> (5/5) citest.py:InitRdCrossTests.test_dracut_build_initrd: PASS (55.30 s)
> RESULTS : PASS 5 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
> JOB TIME : 711.89 s
>
> [1] https://lists.isar-build.org/isar-users/20251030094451.1303871-1-Quirin.Gylstorff@siemens.com/T/#t
>
> Cedric Hombourger (4):
> CI: support negative build tests
> CI: add smoke-tests for switch to dracut in isar-image-ci
> CI: add build tests for isar-dracut initrd images
> CI: check if the build fails when dracut fails
>
> testsuite/cibase.py | 4 +--
> testsuite/cibuilder.py | 12 ++++---
> testsuite/citest.py | 81 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 91 insertions(+), 6 deletions(-)
>
--
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/14c15020-fbdc-42f4-9df9-3ec87f0884ef%40ilbers.de.
prev parent reply other threads:[~2025-11-12 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 11:13 'Cedric Hombourger' via isar-users
2025-11-01 11:13 ` [PATCH 1/4] CI: support negative build tests 'Cedric Hombourger' via isar-users
2025-11-01 11:13 ` [PATCH 2/4] CI: add smoke-tests for switch to dracut in isar-image-ci 'Cedric Hombourger' via isar-users
2025-11-07 13:09 ` Zhihang Wei
2025-11-07 13:42 ` 'cedric.hombourger@siemens.com' via isar-users
2025-11-11 13:58 ` Zhihang Wei
2025-11-11 14:09 ` 'Jan Kiszka' via isar-users
2025-11-11 16:05 ` 'cedric.hombourger@siemens.com' via isar-users
2025-11-01 11:13 ` [PATCH 3/4] CI: add build tests for isar-dracut initrd images 'Cedric Hombourger' via isar-users
2025-11-01 11:13 ` [PATCH 4/4] CI: check if the build fails when dracut fails 'Cedric Hombourger' via isar-users
2025-11-12 16:37 ` Zhihang Wei [this message]
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=14c15020-fbdc-42f4-9df9-3ec87f0884ef@ilbers.de \
--to=wzh@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--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