On Wed, Mar 19, 2025 at 02:52:43PM +0100, Philippe Mathieu-Daudé wrote: > Cc'ing CI maintainers. > > On 19/3/25 03:30, Tanish Desai wrote: > > The issue started after commit > > https://github.com/qemu/qemu/commit/59f4d65584bd3372070e2484876436c8d02505e4 > > > > Reproduction: > > 1. In the build directory on MacOS (haven't tried on other OS), run: > > ../configure --enable-rust --target-list=aarch64-softmmu > > This config isn't covered on our CI, we only test --enable-rust on > Linux. Should we also test it for all non-Linux hosts? I'd rather not...
Bear in mind that Rust is still an experimental feature. If it is broken in some build scenarios & not exhaustively tested, so be it, that's what it means to be "experimental". When we make Rust an on-by-default feature, then we'll get coverage across all CI scenarios automatically. Of course we then have the reverse question of CI testing of "rust disabled" scenarios, Ideally we make Rust mandatory and thus avoid those non-Rust scenarios. So I agree we don't need to expand CI coverage currently, just fix bugs when they're pointed out. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
