Processed: Re: Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
Processing control commands: > severity -1 important Bug #897535 [src:openafs] openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2 Severity set to 'important' from 'serious' -- 897535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
Control: severity -1 important On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote: >... > > volser/vos..FAILED 5 > > bucoord/backup-man..ok > > kauth/kas-man...ok > > > > Failed Set Fail/Total (%) Skip Stat Failing Tests > > -- -- > > > > volser/vos1/6 17%00 5 > > > > Failed 1/710 tests, 99.86% okay. > > Files=23, Tests=710, 16.66 seconds (1.13 usr + 1.99 sys = 3.12 CPU) > > make[2]: *** [Makefile:25: check] Error 1 > > make[2]: Leaving directory '/<>/tests' > > make[1]: *** [Makefile:644: test] Error 2 > > make[1]: Leaving directory '/<>' > > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2 > > The full build log is available from: >http://aws-logs.debian.net/2018/05/02/openafs_1.8.0-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. The same sources built on the autobuilder 3 days after this bug report was submitted: https://buildd.debian.org/status/logs.php?pkg=openafs=amd64 There might be some problem somewhere, but when it builds on the autobuilders it is usually not considered RC. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
(ditto) On Wed, May 30, 2018 at 11:18:11AM -0500, Benjamin Kaduk wrote: > (resetting autoremoval timer) > > On Fri, May 11, 2018 at 12:44:01PM -0500, Benjamin Kaduk wrote: > > ping? > > > > I cannot reproduce locally either on bare metal or in schroot. > > > > -Ben > > > > On Fri, May 04, 2018 at 09:15:51AM -0500, Benjamin Kaduk wrote: > > > Hi Lucas, > > > > > > On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote: > > > > > > > > During a rebuild of all packages in sid, your package failed to build on > > > > amd64. > > > > > > > > Relevant part (hopefully): > > > > > rx/perf.ok > > > > > volser/vos-man..ok > > > > > volser/vos..FAILED 5 > > > > > bucoord/backup-man..ok > > > > > kauth/kas-man...ok > > > > > > > > > > Failed Set Fail/Total (%) Skip Stat Failing Tests > > > > > -- -- > > > > > > > > > > volser/vos1/6 17%00 5 > > > > > > Unfortunately the upstream build system does not capture verbose > > > test output for display in case of failure, but from the test number > > > we can deduce that what is failing is that an outputted list of > > > addresses does not match the expected string: > > > char expecting[] = > > > "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n" > > > > > > "10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n" > > >"10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n" > > >"10.0.0.14\n10.0.0.15\n"; > > > > > > I note that this test is disabled when the system's hostname > > > resolves to a loopback address because those addresses are forbidden > > > from being entered into the database as fileserver addresses, but > > > even when I change my local configuration to avoid that, I still > > > cannot reproduce the test failure locally. > > > > > > I surmise that the AWS machine may be getting assigned a 10/8 > > > address as its primary address, and perhaps that would interfere > > > with some of what the test is doing. Do you happen to know more > > > about the network configuration on the AWS systems used for these > > > autopkgtests? > > > > > > Thanks, > > > > > > Ben
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
(resetting autoremoval timer) On Fri, May 11, 2018 at 12:44:01PM -0500, Benjamin Kaduk wrote: > ping? > > I cannot reproduce locally either on bare metal or in schroot. > > -Ben > > On Fri, May 04, 2018 at 09:15:51AM -0500, Benjamin Kaduk wrote: > > Hi Lucas, > > > > On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote: > > > > > > During a rebuild of all packages in sid, your package failed to build on > > > amd64. > > > > > > Relevant part (hopefully): > > > > rx/perf.ok > > > > volser/vos-man..ok > > > > volser/vos..FAILED 5 > > > > bucoord/backup-man..ok > > > > kauth/kas-man...ok > > > > > > > > Failed Set Fail/Total (%) Skip Stat Failing Tests > > > > -- -- > > > > > > > > volser/vos1/6 17%00 5 > > > > Unfortunately the upstream build system does not capture verbose > > test output for display in case of failure, but from the test number > > we can deduce that what is failing is that an outputted list of > > addresses does not match the expected string: > > char expecting[] = "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n" > >"10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n" > >"10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n" > >"10.0.0.14\n10.0.0.15\n"; > > > > I note that this test is disabled when the system's hostname > > resolves to a loopback address because those addresses are forbidden > > from being entered into the database as fileserver addresses, but > > even when I change my local configuration to avoid that, I still > > cannot reproduce the test failure locally. > > > > I surmise that the AWS machine may be getting assigned a 10/8 > > address as its primary address, and perhaps that would interfere > > with some of what the test is doing. Do you happen to know more > > about the network configuration on the AWS systems used for these > > autopkgtests? > > > > Thanks, > > > > Ben
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
ping? I cannot reproduce locally either on bare metal or in schroot. -Ben On Fri, May 04, 2018 at 09:15:51AM -0500, Benjamin Kaduk wrote: > Hi Lucas, > > On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote: > > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > > > Relevant part (hopefully): > > > rx/perf.ok > > > volser/vos-man..ok > > > volser/vos..FAILED 5 > > > bucoord/backup-man..ok > > > kauth/kas-man...ok > > > > > > Failed Set Fail/Total (%) Skip Stat Failing Tests > > > -- -- > > > > > > volser/vos1/6 17%00 5 > > Unfortunately the upstream build system does not capture verbose > test output for display in case of failure, but from the test number > we can deduce that what is failing is that an outputted list of > addresses does not match the expected string: > char expecting[] = "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n" >"10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n" >"10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n" >"10.0.0.14\n10.0.0.15\n"; > > I note that this test is disabled when the system's hostname > resolves to a loopback address because those addresses are forbidden > from being entered into the database as fileserver addresses, but > even when I change my local configuration to avoid that, I still > cannot reproduce the test failure locally. > > I surmise that the AWS machine may be getting assigned a 10/8 > address as its primary address, and perhaps that would interfere > with some of what the test is doing. Do you happen to know more > about the network configuration on the AWS systems used for these > autopkgtests? > > Thanks, > > Ben
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
Hi Lucas, On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote: > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > rx/perf.ok > > volser/vos-man..ok > > volser/vos..FAILED 5 > > bucoord/backup-man..ok > > kauth/kas-man...ok > > > > Failed Set Fail/Total (%) Skip Stat Failing Tests > > -- -- > > > > volser/vos1/6 17%00 5 Unfortunately the upstream build system does not capture verbose test output for display in case of failure, but from the test number we can deduce that what is failing is that an outputted list of addresses does not match the expected string: char expecting[] = "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n" "10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n" "10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n" "10.0.0.14\n10.0.0.15\n"; I note that this test is disabled when the system's hostname resolves to a loopback address because those addresses are forbidden from being entered into the database as fileserver addresses, but even when I change my local configuration to avoid that, I still cannot reproduce the test failure locally. I surmise that the AWS machine may be getting assigned a 10/8 address as its primary address, and perhaps that would interfere with some of what the test is doing. Do you happen to know more about the network configuration on the AWS systems used for these autopkgtests? Thanks, Ben
Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
Source: openafs Version: 1.8.0-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20180502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/tests/rx' > gcc -I./../.. -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g -O > -I/<>/src/config -I/<>/include -I. -I. > -I/usr/include/heimdal -pthread -D_REENTRANT -DAFS_PTHREAD_ENV -o event-t.o > -c event-t.c > /bin/bash ../../libtool --quiet --mode=link --tag=CC gcc -static > -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/heimdal > -L/usr/lib/x86_64-linux-gnu/heimdal -g -O -I./../.. -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -g -O -I/<>/src/config > -I/<>/include -I. -I. -I/usr/include/heimdal -pthread > -D_REENTRANT -DAFS_PTHREAD_ENV -o event-t event-t.o ../tap/libtap.a > /<>/src/rx/liboafs_rx.la -lroken -lresolv > make[3]: Leaving directory '/<>/tests/rx' > MAKECHECK=1 ./libwrap /<>/lib \ > ./runtests /<>/tests/TESTS > > Running all tests listed in TESTS. If any tests fail, run the failing > test program with runtests -o to see more details. > > util/ktime..ok > util/exec-alt...ok > auth/keys...ok > auth/superuser..ok > auth/authconok > auth/realms.ok > cmd/command.ok > opr/dictok > opr/fmt.ok > opr/jhash...ok > opr/queues..ok > opr/rbtree..ok > opr/softsig.ok > opr/timeok > opr/uuidok > ptserver/pt_utilok > ptserver/pts-manok > rx/eventok > rx/perf.ok > volser/vos-man..ok > volser/vos..FAILED 5 > bucoord/backup-man..ok > kauth/kas-man...ok > > Failed Set Fail/Total (%) Skip Stat Failing Tests > -- -- > volser/vos1/6 17%00 5 > > Failed 1/710 tests, 99.86% okay. > Files=23, Tests=710, 16.66 seconds (1.13 usr + 1.99 sys = 3.12 CPU) > make[2]: *** [Makefile:25: check] Error 1 > make[2]: Leaving directory '/<>/tests' > make[1]: *** [Makefile:644: test] Error 2 > make[1]: Leaving directory '/<>' > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2 The full build log is available from: http://aws-logs.debian.net/2018/05/02/openafs_1.8.0-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.
