Control: retitle 991110 python3.9: Please exclude test_concurrent_futures also on armhf and alpha Control: severity 991110 serious Control: retitle 991111 python3.10: Please exclude test_concurrent_futures also on armhf and alpha Control: severity 991111 serious
The same failure happened now on the buildds for both python3.9 and python3.10 when building for armhf: https://buildd.debian.org/status/fetch.php?pkg=python3.9&arch=armhf&ver=3.9.6-1&stamp=1626524274&raw=0 https://buildd.debian.org/status/logs.php?pkg=python3.10&arch=armhf One suspect why this broke is: 12:55 < aurel32> bunk: arm-ubc-0{4,5,6} are now using QEMU from backports and the host is also running the kernel from backports. This was need to fix the regular VM crashes from 32-bit VMs 16:01 < aurel32> bunk: that was done on 2021-05-11 according to my IRC logs of the #debian-admin channel cu Adrian On Wed, Jul 14, 2021 at 06:49:24PM +0300, Adrian Bunk wrote: > Source: python3.9 > Severity: important > Tags: patch ftbfs > Control: clone -1 -2 > Control: reassign -2 python3.10 > Control: retitle -2 python3.10: Please exclude test_concurrent_futures also > on alpha > > test_concurrent_futures frequently hangs during the build on alpha: > > https://buildd.debian.org/status/package.php?p=python3.9&suite=experimental > https://buildd.debian.org/status/logs.php?pkg=python3.9&arch=alpha > > ... > 23:57:55 load avg: 0.00 running: test_concurrent_futures (23 hour 51 min) > ... > > > Workaround: > > --- python3.9-3.9.6/debian/rules.old 2021-07-14 14:46:00.200490919 +0000 > +++ python3.9-3.9.6/debian/rules 2021-07-14 14:46:18.848548468 +0000 > @@ -542,7 +542,7 @@ > TEST_EXCLUDES += test_gdb > endif > > -ifneq (,$(filter $(DEB_HOST_ARCH), riscv64)) > +ifneq (,$(filter $(DEB_HOST_ARCH), alpha riscv64)) > TEST_EXCLUDES += test_concurrent_futures > endif >
