mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Subject: [PATCH 0/5] test: arm: boot test Debian image in CI
Date: Fri,  9 Jan 2026 17:57:26 +0100	[thread overview]
Message-ID: <20260109170007.805177-1-a.fatoum@barebox.org> (raw)

So far, we had no automated tests that actually booted a kernel
on every push (or PR). This series addresses this by 
a Debian ARM64 image and trying to boot it three times:

  - via GRUB
  - directly via kernel EFI stub
  - directly without EFI

Ahmad Fatoum (5):
  test: arm: multi_v8_efiloader_defconfig: use qcow2 image
  test: py: strategy: add helpers for booting kernel and bootm
  test: py: efiloader: prepare get_dmesg for more general usage
  test: py: add more kernel boot tests
  ci: add Debian ARM64 EFI loader boot test

 .github/workflows/test-labgrid-pytest.yml  | 20 ++++++
 .gitignore                                 |  4 ++
 scripts/fetch-os.sh                        | 35 ++++++++++
 test/arm/multi_v8_efiloader_defconfig.yaml |  7 +-
 test/py/test_fit.py                        |  2 +-
 test/py/test_linux_efiloader.py            | 75 +++++++++++++++++++++-
 test/strategy.py                           | 36 ++++++++++-
 7 files changed, 171 insertions(+), 8 deletions(-)
 create mode 100755 scripts/fetch-os.sh

-- 
2.47.3




             reply	other threads:[~2026-01-09 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 16:57 Ahmad Fatoum [this message]
2026-01-09 16:57 ` [PATCH 1/5] test: arm: multi_v8_efiloader_defconfig: use qcow2 image Ahmad Fatoum
2026-01-09 16:57 ` [PATCH 2/5] test: py: strategy: add helpers for booting kernel and bootm Ahmad Fatoum
2026-01-09 16:57 ` [PATCH 3/5] test: py: efiloader: prepare get_dmesg for more general usage Ahmad Fatoum
2026-01-09 16:57 ` [PATCH 4/5] test: py: add more kernel boot tests Ahmad Fatoum
2026-01-09 16:57 ` [PATCH 5/5] ci: add Debian ARM64 EFI loader boot test Ahmad Fatoum

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=20260109170007.805177-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    /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