Ah, I now see what you guys mean. Yes, the latest image as published by the reform-system-image CI pipeline does something that it should not: it boots from eMMC instead of the SD-Card and if you don’t have a sysimage-v3 on your eMMC, then your system doesn’t boot. This is why I didn’t see any problems a few messages earlier because my system booted just fine but I didn’t notice that what booted was my eMMC system and not the system I flashed on the SD-Card.
Since an image that I build locally boots from SD-Card just fine, maybe @minute can quickly re-trigger the reform-system-image pipeline for the sysimage-v3 branch? If that build works then all good and if not, then there is a more fundamental problem in how images are created on the CI pipeline.
EDIT: I now know why the image produced by the latest pipeline run doesn’t boot: it’s missing a boot.scr on the first partition. I don’t yet know why this is, especially because an image created locally contains a boot.scr just fine. But this explains why the current image boots from eMMC: u-boot on the latest CI image will first try reading boot.scr from SD-Card and cannot find it. It tries eMMC next and will boot that if the first partition on eMMC contains boot.scr. If your eMMC doesn’t contain a sysimage-v3 then it will just not boot.
Maybe just re-running the pipeline will fix the problem. There was a recent upload of flash-kernel (which is responsible for creating boot.scr) to Debian which integrated MNT Reform support. And maybe the image built at a time when the Debian mirror used by the CI didn’t have a flash-kernel version that was new enough yet.