Source: libics Version: 1.6.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>' > PASS: test_ics1.sh > PASS: test_ics2b.sh > PASS: test_ics2a.sh > PASS: test_strides.sh > PASS: test_strides2.sh > PASS: test_strides3.sh > PASS: test_history.sh > FAIL: test_metadata1.sh > PASS: test_metadata2.sh > PASS: test_compress.sh > PASS: test_gzip.sh > ==================================== > libics 1.6.3: ./test-suite.log > ==================================== > > # TOTAL: 11 > # PASS: 10 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: test_metadata1.sh > ======================= > > Different history key/value pair read back > FAIL test_metadata1.sh (exit status: 255) > > ============================================================================ > Testsuite summary for libics 1.6.3 > ============================================================================ > # TOTAL: 11 > # PASS: 10 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > ============================================================================ > See ./test-suite.log > ============================================================================ > make[3]: *** [Makefile:1014: test-suite.log] Error 1 > make[3]: Leaving directory '/<<PKGBUILDDIR>>' > make[2]: *** [Makefile:1122: check-TESTS] Error 2 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > make[1]: *** [Makefile:1399: check-am] Error 2 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/libics_1.6.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
