Source: remctl
Version: 3.11-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 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/stdin............skipped (Kerberos tests not configured)
> server/streaming........skipped (Kerberos tests not configured)
> server/summary..........skipped (Kerberos tests not configured)
> server/user.............skipped (Kerberos tests not configured)
> server/version..........skipped (Kerberos tests not configured)
> 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.....FAILED 21-22
> util/network/server.....ok
> util/tokens.............FAILED 10
> 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
> -------------------------- -------------- ---- ----  ------------------------
> util/network/client           2/21    10%    1    0  21-22
> util/tokens                   1/12     8%    0    0  10
> 
> Failed 3/1832 tests, 99.84% okay, 75 tests skipped.
> Files=51,  Tests=1832,  18.19 seconds (0.36 usr + 0.05 sys = 0.40 CPU)
> make[2]: *** [check-local] Error 1
> Makefile:3570: recipe for target 'check-local' failed
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> make[1]: *** [check-am] Error 2
> Makefile:3274: recipe for target 'check-am' failed
> 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/07/14/remctl_3.11-1_unstable_gcc5.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.

Reply via email to