Source: remctl Version: 3.12-1 Severity: serious Tags: stretch sid User: [email protected] Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<<PKGBUILDDIR>>' > cd tests && ./runtests -l '/<<PKGBUILDDIR>>/tests/TESTS' > > Running all tests listed in TESTS. If any tests fail, run the failing > test program with runtests -o to see more details. > > client/api..............skipped (Kerberos tests not configured) > client/ccache...........skipped (Kerberos tests not configured) > client/large............skipped (Kerberos tests not configured) > client/open.............ok (skipped 15 tests) > client/remctl...........skipped (Kerberos tests not configured) > client/source-ip........skipped (Kerberos tests not configured) > client/timeout..........skipped (Kerberos tests not configured) > docs/pod................skipped (POD syntax tests normally skipped) > docs/pod-spelling.......skipped (Spelling tests only run for author) > perl/module-version.....skipped (Module version tests normally skipped) > portable/asprintf.......ok > portable/daemon.........ok > portable/getaddrinfo....ok (skipped 20 tests) > portable/getnameinfo....ok (skipped 7 tests) > portable/getopt.........ok > portable/inet_aton......ok > portable/inet_ntoa......ok > portable/inet_ntop......ok > portable/mkstemp........ok > portable/setenv.........ok > portable/snprintf.......ok > server/accept...........skipped (Kerberos tests not configured) > server/acl..............ok (skipped 4 tests) > server/acl/localgroup...ok > server/anonymous........skipped (Kerberos tests not configured) > server/bind.............skipped (Kerberos tests not configured) > server/config...........ok > server/continue.........skipped (Kerberos tests not configured) > server/empty............skipped (Kerberos tests not configured) > server/env..............skipped (Kerberos tests not configured) > server/errors...........skipped (Kerberos tests not configured) > server/help.............skipped (Kerberos tests not configured) > server/invalid..........skipped (Kerberos tests not configured) > server/logging..........ok > server/misc.............skipped (Kerberos tests not configured) > server/shell-misc.......FAILED 8 > server/ssh-parse........ok > server/stdin............skipped (Kerberos tests not configured) > server/streaming........skipped (Kerberos tests not configured) > server/sudo.............ok > server/summary..........skipped (Kerberos tests not configured) > server/user.............skipped (Kerberos tests not configured) > server/version..........skipped (Kerberos tests not configured) > util/buffer.............ok > util/gss-tokens.........skipped (Kerberos tests not configured) > util/messages...........ok > util/messages-krb5......ok > util/network/addr-ipv4..ok > util/network/addr-ipv6..ok > util/network/client.....ok > util/network/server.....ok > util/tokens.............ok > util/vector.............ok > util/xmalloc............skipped (xmalloc tests only run for author) > util/xwrite.............ok (skipped 2 tests) > > Failed Set Fail/Total (%) Skip Stat Failing Tests > -------------------------- -------------- ---- ---- ------------------------ > server/shell-misc 1/15 7% 0 0 8 > > Failed 1/1976 tests, 99.95% okay, 74 tests skipped. > Files=55, Tests=1976, 10.38 seconds (0.35 usr + 0.06 sys = 0.41 CPU) > Makefile:4060: recipe for target 'check-local' failed > make[2]: *** [check-local] Error 1 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > Makefile:3760: recipe for target 'check-am' failed > make[1]: *** [check-am] Error 2 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 The full build log is available from: http://people.debian.org/~lucas/logs/2016/08/28/remctl_3.12-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.
