bug-gawk
[Top][All Lists]
Advanced

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

[bug-gawk] gawk 4.2.1 test failure on macOS


From: Charles Diza
Subject: [bug-gawk] gawk 4.2.1 test failure on macOS
Date: Sun, 25 Feb 2018 18:02:08 -0500

> On macOS 10.13.3, I just tried building the new gawk 4.2.1.  It builds fine, but the `make check` step fails, with this:
> ========8<=================================
> rwarray
> testext
> time
> 1 TESTS FAILED
> make[2]: *** [pass-fail] Error 1
> for i in _* ; \
> do  \
> if [ "$i" != "_*" ]; then \
> echo ============== $i ============= ; \
> base=`echo $i | sed 's/^_//'` ; \
> if [ -r ${base}.ok ]; then \
> diff -c ${base}.ok $i ; \
> else \
> diff -c "."/${base}.ok  $i ; \
> fi ; \
> fi ; \
> done | more
> ============== _nlstringtest =============
> *** nlstringtest.ok 2018-01-15 13:37:32.000000000 -0500
> --- _nlstringtest 2018-02-25 17:04:34.000000000 -0500
> ***************
> *** 1,5 ****
> ! 2 morceaux de gateau
> ! %2$s remplace %1$s.
> ! %2$s remplace %1$s.
> ! EUR remplace FF.
> --- 1,5 ----
> ! 2 pieces of cake
> ! %s is replaced by %s.
> ! %s is replaced by %s.
> ! FF is replaced by EUR.
> make[1]: *** [check] Error 1
> make: *** [check-recursive] Error 1
> ===================>8=======================
> I get this failure whether or not I build it from within Homebrew.  If I build it outside Homebrew---straight-up---the last line "! FF is replaced by EUR" is seemingly under the control of `less` or some other pager, because it will stay there indefinitely until I hit a key.  At that point, the make error shows.
> My compilation flags were:
> --disable-debug
> --disable-dependency-tracking
> --without-readline
> --without-mpfr
> --without-libsigsegv-prefix


Bisection on the gawk git repo reveals that bae14502b6389b7d81bf0841a35b4c9d9824ca10 Is the first bad gawk commit.

During bisection, some of the "bad" stages had slightly different test failures than the one I'm reporting.  I labeled those "bad" and went on with the bisection.

Also, it's `more` that the last tests gets stuck in for some reason.

-Charles


reply via email to

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