Hello.
I've checked and this seems to be enough to reproduce the hang on any system:
taskset -c 0 dpkg-buildpackage -uc -us -b
My proposal to fix the FTBFS bug, since the exit status for
dh_auto_test is already ignored, would be not to run the tests
at all on systems on which we know the build hangs.
The attached patch would do that.
Please tell me what do you think about this, as I'd like to see
the FTBFS bug eventually fixed in stable.
Thanks.
--- a/debian/rules
+++ b/debian/rules
@@ -14,6 +14,8 @@ export DH_GOLANG_INSTALL_EXTRA := \
export BUILDTESTDIR=$(CURDIR)/buildtest
+NUM_CPUS := $(shell nproc)
+
# some arches need more than 10 min to run TestTestsToRegexpLive
ARCHES_SLOW_TEST := mips64el mipsel
ifneq ($(findstring $(DEB_BUILD_ARCH),$(ARCHES_SLOW_TEST)),)
@@ -51,8 +53,11 @@ override_dh_auto_clean:
# build-time tests for github.com/ncw/rclone/vfs access the config file
# so provide a null config
override_dh_auto_test:
- -export RCLONE_CONFIG="/notfound"; \
- dh_auto_test -- $(EXTRA_TESTFLAGS)
+ifeq ($(NUM_CPUS),1)
+ @echo "Skipping dh_auto_test, known to hang autobuilder when there is
only one CPU."
+else
+ -export RCLONE_CONFIG="/notfound"; dh_auto_test -- $(EXTRA_TESTFLAGS)
+endif
override_dh_fixperms:
dh_fixperms
