[core-updates-frozen] Gawk 5.1.0 test failure (non-deterministic)

DoneSubmitted by Maxim Cournoyer.
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Severity
normal
M
M
Maxim Cournoyer wrote on 19 Oct 13:49 +0200
(name . bug-guix)(address . bug-guix@gnu.org)
87h7ddi6a8.fsf@gmail.com
Hello,
While rebuilding the core-updates-core-frozen branch locally, I stumbledupon:
Toggle snippet (41 lines)1 TESTS FAILEDmake[3]: *** [Makefile:5145: pass-fail] Error 1make[3]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'make[3]: Entering directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'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 ============== _clos1way2 =============*** clos1way2.ok 2019-08-28 18:43:58.000000000 +0000--- _clos1way2 2021-10-19 04:25:01.526475198 +0000****************** 1,4 ****! gawk: clos1way2.awk:5: (FILENAME=- FNR=1) warning: fflush: cannot flush: two-way pipe `cat - 1>&2 && sleep 2' has closed write end! test gawk: clos1way2.awk:6: (FILENAME=- FNR=1) fatal: print: attempt to write to closed write end of two-way pipe EXIT CODE: 2--- 1,4 ----! gawk: clos1way2.awk:5: test! (FILENAME=- FNR=1) warning: fflush: cannot flush: two-way pipe `cat - 1>&2 && sleep 2' has closed write end gawk: clos1way2.awk:6: (FILENAME=- FNR=1) fatal: print: attempt to write to closed write end of two-way pipe EXIT CODE: 2make[3]: *** [Makefile:5154: diffout] Error 1make[3]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'make[2]: *** [Makefile:2034: check] Error 1make[2]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'make[1]: *** [Makefile:747: check-recursive] Error 1make[1]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0'make: *** [Makefile:1047: check] Error 2
Test suite failed, dumping logs.
To be investigated, but we should probably:
1. report the problem upstream;2. disable the test.
Thank you,
Maxim
M
M
Maxim Cournoyer wrote on 20 Oct 05:48 +0200
(address . 51286-done@debbugs.gnu.org)
871r4gicgd.fsf@gmail.com
Hello,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
Toggle quote (54 lines)> Hello,>> While rebuilding the core-updates-core-frozen branch locally, I stumbled> upon:>> 1 TESTS FAILED> make[3]: *** [Makefile:5145: pass-fail] Error 1> make[3]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'> make[3]: Entering directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'> 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 > ============== _clos1way2 =============> *** clos1way2.ok 2019-08-28 18:43:58.000000000 +0000> --- _clos1way2 2021-10-19 04:25:01.526475198 +0000> ***************> *** 1,4 ****> ! gawk: clos1way2.awk:5: (FILENAME=- FNR=1) warning: fflush: cannot flush: two-way pipe `cat - 1>&2 && sleep 2' has closed write end> ! test> gawk: clos1way2.awk:6: (FILENAME=- FNR=1) fatal: print: attempt to write to closed write end of two-way pipe> EXIT CODE: 2> --- 1,4 ----> ! gawk: clos1way2.awk:5: test> ! (FILENAME=- FNR=1) warning: fflush: cannot flush: two-way pipe `cat - 1>&2 && sleep 2' has closed write end> gawk: clos1way2.awk:6: (FILENAME=- FNR=1) fatal: print: attempt to write to closed write end of two-way pipe> EXIT CODE: 2> make[3]: *** [Makefile:5154: diffout] Error 1> make[3]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'> make[2]: *** [Makefile:2034: check] Error 1> make[2]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0/test'> make[1]: *** [Makefile:747: check-recursive] Error 1> make[1]: Leaving directory '/tmp/guix-build-gawk-5.1.0.drv-0/gawk-5.1.0'> make: *** [Makefile:1047: check] Error 2>> Test suite failed, dumping logs.>> To be investigated, but we should probably:>> 1. report the problem upstream;> 2. disable the test.>> Thank you,>> Maxim
Seems it had to do with using a minimal variant of Bash instead of theregular full-fledged Bash. I've fixed it on thecore-updates-frozen-batched-changes branch.
Closing.
Maxim
Closed
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send email to 51286@debbugs.gnu.org