Hi, On Tue, Jun 30, 2020 at 09:28:34PM +0200, Andrea Bolognani wrote: > On Sat, May 16, 2020 at 03:00:46PM +0300, Adrian Bunk wrote: > > Source: libvirt > > Version: 6.0.0-7 > > Severity: serious > > Tags: ftbfs > > > > https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=all&ver=6.0.0-7&stamp=1589452859&raw=0 > > https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=i386&ver=6.0.0-7&stamp=1589494701&raw=0 > > > > ... > > make check-TESTS > > make[4]: Entering directory '/<<PKGBUILDDIR>>/debian/build/tests' > > make[5]: Entering directory '/<<PKGBUILDDIR>>/debian/build/tests' > > PASS: sockettest > > PASS: virbuftest > > PASS: virhostcputest > [...] > > PASS: virsh-vcpupin > > PASS: virsh-optparse > > PASS: virt-aa-helper-test > > E: Build killed with signal TERM after 150 minutes of inactivity > > Has anyone managed to reproduce this? I've built 6.0.0-7 from source > in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder > and in a sid:i386 VM, without encountering a single failure.
I tried to reproduce too when this came in and couldn't. -- Guido > > The latest build attempt on i386 also failed: > > > https://buildd.debian.org/status/fetch.php?pkg=libvirt&arch=i386&ver=6.4.0-1&stamp=1593097042&raw=0 > > However, the failure in this case was not limited to i386 and the > error was completely different, caused this time by > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963704 > > All I can think of at this point is a temporary glitch of the > buildd. In a couple of weeks, when we upload 6.5.0, we'll hopefully > see that build fine on all architectures, i386 included... > > Does anyone have any better theories? Or a way to dig further? > > -- > Andrea Bolognani <e...@kiyuko.org> > Resistance is futile, you will be garbage collected. > _______________________________________________ > Pkg-libvirt-maintainers mailing list > pkg-libvirt-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers