Re: rhel8 test failure confirmation?

[Bogdan]

Bogdan <bogdro_rep@gmx.us>, Fri Mar 03 2023 14:56:07 GMT+0100 (Central 
European Standard Time)
> Bogdan <bogdro_rep@gmx.us>, Fri Mar 03 2023 11:21:25 GMT+0100 (Central 
> European Standard Time)
> > Karl Berry <karl@freefriends.org>, 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://git.savannah.gnu.org/automake.git
> > >    cd automake
> > >    ./bootstrap
> > >    ./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/nodef.sh t/backcompat2.sh t/backcompat3.sh 
> > t/get-sysconf.sh t/lex-depend.sh 
> > t/remake-aclocal-version-mismatch.sh t/subdir-add2-pr46.sh 
> > t/testsuite-summary-reference-log.sh'
> >
> >   I get failures in t/backcompat2.sh. 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.


[...]


>   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.


Never mind. The tests are failing again. Sorry for the noise.


--
Regards - Bogdan ('bogdro') D.                 (GNU/Linux & FreeDOS)
X86 assembly (DOS, GNU/Linux):    http://bogdro.evai.pl/index-en.php
Soft(EN): http://bogdro.evai.pl/soft  http://bogdro.evai.pl/soft4asm
www.Xiph.org  www.TorProject.org  www.LibreOffice.org  www.GnuPG.org