On 06/04/2022 08:22, Jan Beulich wrote: > On 05.04.2022 16:53, osstest service owner wrote: >> flight 169170 xen-4.14-testing real [real] >> http://logs.test-lab.xenproject.org/osstest/logs/169170/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-amd64-xl 18 guest-localmigrate fail REGR. vs. >> 168506 >> build-arm64-xsm 6 xen-build fail REGR. vs. >> 168506 > Urgh: > > CC hw/virtio/virtio-bus.o > CC hw/virtio/virtio-rng.o > CC hw/virtio/virtio-pci.o > CC hw/virtio/virtio-mmio.o > CC hw/virtio/virtio-pmem-pci.o > CC hw/virtio/vhost-stub.o > cc: internal compiler error: Segmentation fault signal terminated program cc1 > Please submit a full bug report, > with preprocessed source if appropriate. > See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions. > make: *** > [/home/osstest/build.169170.build-arm64-xsm/xen/tools/qemu-xen-dir/rules.mak:69: > hw/virtio/vhost-stub.o] Error 4 > > If this is going to recur, I don't see what we ought to do about this. > This doesn't look to have any relation to the recently added two > commits on the respective qemu stable tree. > > However, if this wouldn't recur it would be similarly alarming: That > would suggest the build environment to not be stable. > > Thoughts anyone?
The version of debian was recently bumped to work around the usual OSSTest issues when it gets too out of date. Guess we picked up a new, broken, compiler. ~Andrew
