[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1055388: automake-1.16: flaky autopkgtest: t/subobj.sh intermittently fails



Source: automake-1.16
Version: 1:1.16.5-1.3
Severity: important
User: debian-ci@lists.debian.org
Usertags: flaky
X-Debbugs-Cc: debian-ci@lists.debian.org
Control: affects -1 + src:glib2.0

It seems that the automake test suite is intermittently failing when run
on the autopkgtest infrastructure. This means that when packages that are
depended on by the test suite, such as glib2.0, python3-defaults and vala,
are trying to migrate to testing, the test will randomly pass or fail,
causing those packages to be detected as having caused a regression when
in fact they have not.

For example, at the moment glib2.0's migration is being prevented by a
failure on s390x, but the same test failure has also been seen on amd64
when testing new versions of cscope and python-docutils:
https://ci.debian.net/packages/a/automake-1.16/testing/s390x/
https://ci.debian.net/packages/a/automake-1.16/testing/amd64/

The fact that this is happening on both those architectures and while
testing several different proposed packages makes me think that this is
unlikely to be architecture-specific or a package-specific regression:
those particular builds were probably just unlucky.

The failure is logged as something like this:

3320s FAIL: t/subobj.sh
...
4110s ============================================================================
4110s Testsuite summary for GNU Automake 1.16.5
4110s ============================================================================
...
4110s # FAIL:  1

The relevant part of testsuite.log from one such failing build is
quoted below. I don't know automake's test suite well enough to know
what is going wrong here.

    smcv

---------------------------------------------------------------------------

FAIL: t/subobj
==============

Running from installcheck: no
Test Protocol: none
PATH = /tmp/autopkgtest-lxc.vbvr0hhv/downtmp/build.8GT/src/bin:/tmp/autopkgtest-lxc.vbvr0hhv/downtmp/build.8GT/src/t/ax:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
++ pwd
/tmp/autopkgtest-lxc.vbvr0hhv/downtmp/build.8GT/src/t/subobj.dir
+ cat
+ aclocal-1.16 -Werror
+ :
+ cat
+ mkdir sub
+ cat
+ AUTOMAKE_fails
+ AUTOMAKE_run -e 1
+ am__desc=
+ am__exp_rc=0
+ test 2 -gt 0
+ case $1 in
+ am__exp_rc=1
+ shift
+ shift
+ test 0 -gt 0
+ am__got_rc=0
+ automake-1.16 --foreign -Werror -Wall
+ am__got_rc=1
+ cat stderr
automake-1.16: warnings are treated as errors
Makefile.am:3: warning: source file 'generic/a.c' is in a subdirectory,
Makefile.am:3: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least one source file is in a subdirectory, but the 'subdir-objects'
automake-1.16: automake option hasn't been enabled.  For now, the corresponding output
automake-1.16: object file(s) will be placed in the top-level directory.  However, this
automake-1.16: behavior may change in a future Automake major version, with object
automake-1.16: files being placed in the same subdirectory as the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option throughout your
automake-1.16: project, to avoid future incompatibilities.
Makefile.am:3: warning: source file 'another/z.cxx' is in a subdirectory,
Makefile.am:3: but option 'subdir-objects' is disabled
sub/Makefile.am:1: warning: source file 'generic/b.c' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
sub/Makefile.am:1: warning: source file 'more/r.y' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
+ cat stdout
+ test none = none
+ test 1 -eq 1
+ return
+ grep '^Makefile\.am:3:.*'\''generic/a\.c'\''.* in a subdirectory' stderr
Makefile.am:3: warning: source file 'generic/a.c' is in a subdirectory,
+ grep '^Makefile\.am:[34]:.*'\''another/z\.cxx'\''.* in a subdirectory' stderr
Makefile.am:3: warning: source file 'another/z.cxx' is in a subdirectory,
+ grep '^sub/Makefile\.am:1:.*'\''generic/b\.c'\''.* in a subdirectory' stderr
sub/Makefile.am:1: warning: source file 'generic/b.c' is in a subdirectory,
+ grep 'option '\''subdir-objects'\'' is disabled' stderr
Makefile.am:3: but option 'subdir-objects' is disabled
Makefile.am:3: but option 'subdir-objects' is disabled
sub/Makefile.am:1: but option 'subdir-objects' is disabled
sub/Makefile.am:1: but option 'subdir-objects' is disabled
+ for msg in "possible forward-incompatibility" "For now,.* corresponding" "advi[sc]e.* 'subdir-objects' option throughout"
++ grep -c 'possible forward-incompatibility' stderr
+ test 1 -eq 1
+ for msg in "possible forward-incompatibility" "For now,.* corresponding" "advi[sc]e.* 'subdir-objects' option throughout"
++ grep -c 'For now,.* corresponding' stderr
+ test 1 -eq 1
+ for msg in "possible forward-incompatibility" "For now,.* corresponding" "advi[sc]e.* 'subdir-objects' option throughout"
++ grep -c 'advi[sc]e.* '\''subdir-objects'\'' option throughout' stderr
+ test 1 -eq 1
+ grep 'subdir-object([^s]|$)' stderr
+ automake-1.16 --foreign -Werror -Wall -Wno-unsupported
+ echo AUTOMAKE_OPTIONS = subdir-objects
+ AUTOMAKE_fails
+ AUTOMAKE_run -e 1
+ am__desc=
+ am__exp_rc=0
+ test 2 -gt 0
+ case $1 in
+ am__exp_rc=1
+ shift
+ shift
+ test 0 -gt 0
+ am__got_rc=0
+ automake-1.16 --foreign -Werror -Wall
+ am__got_rc=1
+ cat stderr
automake-1.16: warnings are treated as errors
sub/Makefile.am:1: warning: source file 'generic/b.c' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least one source file is in a subdirectory, but the 'subdir-objects'
automake-1.16: automake option hasn't been enabled.  For now, the corresponding output
automake-1.16: object file(s) will be placed in the top-level directory.  However, this
automake-1.16: behavior may change in a future Automake major version, with object
automake-1.16: files being placed in the same subdirectory as the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option throughout your
automake-1.16: project, to avoid future incompatibilities.
sub/Makefile.am:1: warning: source file 'more/r.y' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
+ cat stdout
+ test none = none
+ test 1 -eq 1
+ return
+ grep '^Makefile\.am' stderr
+ grep '^sub/Makefile\.am:.*'\''generic/b\.c'\''.* in a subdirectory' stderr
sub/Makefile.am:1: warning: source file 'generic/b.c' is in a subdirectory,
+ grep 'option '\''subdir-objects'\'' is disabled' stderr
sub/Makefile.am:1: but option 'subdir-objects' is disabled
sub/Makefile.am:1: but option 'subdir-objects' is disabled
+ sed 's/^AM_INIT_AUTOMAKE/&([subdir-objects])/' configure.ac
+ mv -f configure.tmp configure.ac
+ aclocal-1.16 -Werror --force
+ automake-1.16 --foreign -Werror -Wall
automake-1.16: warnings are treated as errors
sub/Makefile.am:1: warning: source file 'generic/b.c' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
automake-1.16: warning: possible forward-incompatibility.
automake-1.16: At least one source file is in a subdirectory, but the 'subdir-objects'
automake-1.16: automake option hasn't been enabled.  For now, the corresponding output
automake-1.16: object file(s) will be placed in the top-level directory.  However, this
automake-1.16: behavior may change in a future Automake major version, with object
automake-1.16: files being placed in the same subdirectory as the corresponding sources.
automake-1.16: You are advised to start using 'subdir-objects' option throughout your
automake-1.16: project, to avoid future incompatibilities.
sub/Makefile.am:1: warning: source file 'more/r.y' is in a subdirectory,
sub/Makefile.am:1: but option 'subdir-objects' is disabled
+ am_exit_trap 1
+ exit_status=1
+ set +e
+ cd /tmp/autopkgtest-lxc.vbvr0hhv/downtmp/build.8GT/src
+ test none = tap
+ case $am_explicit_skips in
+ test 1 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
FAIL t/subobj.sh (exit status: 1)


Reply to: