aboutsummaryrefslogtreecommitdiff
path: root/CLAUDE.md
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-25 19:52:46 -0400
committerCraig Jennings <c@cjennings.net>2026-06-25 19:52:46 -0400
commiteb379c38383f3f46e7c19ca5d1f4980182ff7ce2 (patch)
tree658fd65db999aaad42d9905c9995a6e6c6ab58a6 /CLAUDE.md
parent05ec096cb2dcab3e1bde6081d1ddb9028b501afd (diff)
downloadarchsetup-eb379c38383f3f46e7c19ca5d1f4980182ff7ce2.tar.gz
archsetup-eb379c38383f3f46e7c19ca5d1f4980182ff7ce2.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 'CLAUDE.md')
0 files changed, 0 insertions, 0 deletions