[Top][All Lists]

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

Re: rhel8 test failure confirmation?

From: Bogdan
Subject: Re: rhel8 test failure confirmation?
Date: Fri, 3 Mar 2023 14:56:07 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0

Bogdan <>, Fri Mar 03 2023 11:21:25 GMT+0100 (Central European Standard Time)
Karl Berry <>, Wed Mar 01 2023 20:01:26 GMT+0100 (Central European Standard Time)
Does anyone have access to an RHEL 8-based machine? Alma Linux, Rocky Linux,
original RHEL, or even (sort of) CentOS 8? It would be nice if someone
could run a make check there (from automake dev).
   git clone -q git://
   cd automake
   ./configure && make >&cm.out
   make -j8 VERBOSE=1 check keep_testdirs=yes >&ch8.out
(choose whatever -j value you like)


 This, along with my observation (below), MAY actually point to some issue with Autoconf. Old systems work, new don't.

 I take that back (for now). See below.

  When I run

make check TESTS='t/ t/ t/ t/ t/ t/ t/ t/'

 I get failures in t/ Sometimes, like once-twice in ten runs.
  I've added a simple 'debug' in the form of the 'stat' command and:




 Note that 'config.h' is older (4 seconds) than './configure', which shouldn't be the case as it should get updated with new values.

 What's funny, when I run just the failing test alone, it works 10 times in a row. A "Schroedinger bug" - when you try to observe, you change the environment and the bug disappears :).
  I'll try to do some more digging later.

Done a bit more digging into how AM_INIT_AUTOMAKE works. No idea how or if caching of M4 'defines' works, but from a programming point of view, I see setting the [no-define] option conditionally:

        m4_ifval([$3], [_AM_SET_OPTION([no-define])])dnl

and checking it unconditionally:


and I ask myself: what if on the next run the value is still (un)defined when it shouldn't be? It shouldn't be defined, because we start with the empty value as the third parameter in the t/ test, but...

Anyway, to the point: I did a simple change - un-define the value on the "else" path. Diff attached (not pretty, because it's just for testing). Since the change, I've done 22 test runs of the same test set (the one with 8 tests, not the single one which always passed) and saw completely no failures. If it works for everybody, then perhaps some _AM_UNSET_OPTION macro should be created in options.m4, to keep the code nice, and that committed to the main code instead of my patch.
 If it works, there may be other places worth checking.

Regards - Bogdan ('bogdro') D.                 (GNU/Linux & FreeDOS)
X86 assembly (DOS, GNU/Linux):

Attachment: init-add-undef.diff
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]