diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-25 19:52:46 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-25 19:52:46 -0400 |
| commit | d84ddbb80e00af4799ce8c69ddf7a717f3eb956e (patch) | |
| tree | 4d6357e82e438f85c81cfc5f1f7c1ba9381b6cdb /scripts/testing/README.org | |
| parent | 97360b810f303a0795e74361ec78b4a2af606e7a (diff) | |
| download | archsetup-d84ddbb80e00af4799ce8c69ddf7a717f3eb956e.tar.gz archsetup-d84ddbb80e00af4799ce8c69ddf7a717f3eb956e.zip | |
test(archsetup): branch boot/backup checks on the ZFS boot path
The Testinfra boot and backup checks asserted btrfs behavior unconditionally, so they failed on a ZFS root once the ZFS VM path started running them. ZFS boots via ZFSBootMenu, not GRUB. archsetup skips the systemd-hook switch and the mkinitcpio rebuild on ZFS, and on a ZFS+virtio VM it never edits mkinitcpio.conf at all. Branch each check on the existing zfs_root/has_nvme fixtures: assert the ZFSBootMenu EFI binary on ZFS (GRUB on btrfs), gate the mkinitcpio.conf backup on archsetup actually editing the file, and check the console font in /etc/vconsole.conf on ZFS (the initramfs on non-ZFS).
Surfaced by the first full ZFS VM run, which completed archsetup cleanly (exit 0). These were the only 3 failures.
Diffstat (limited to 'scripts/testing/README.org')
0 files changed, 0 insertions, 0 deletions
