develooper Front page | perl.perl5.porters | Postings from July 2019

[perl #134295] t/op/blocks.t failing tests 9-11 on Windows

Thread Next
From:
Tony Cook via RT
Date:
July 19, 2019 00:46
Subject:
[perl #134295] t/op/blocks.t failing tests 9-11 on Windows
Message ID:
rt-4.0.24-1550-1563497178-1533.134295-15-0@perl.org
On Thu, 18 Jul 2019 13:47:55 -0700, shay wrote:
> This is a bug report for perl from steve.m.hay@googlemail.com,
> generated with the help of perlbug 1.41 running under perl 5.31.2.
> 
> 
> -----------------------------------------------------------------
> [Please describe your issue here]
> 
> t/op/blocks.t is failing tests 9-11 on Windows, at least in GCC
> builds. (I've not tested VC++ yet because the build is currently
> broken - see RT#134221.)
> 
> This is also seen in Smoke reports from other users, e.g.
> https://perl5.test-smoke.org/report/91300
> 
> C:\Dev\Git\perl\t>.\perl harness op\blocks.t
> op/blocks.t .. 4/22 # Failed test 9 - BEGIN{exit 0} should exit at
> ./test.pl line 1062
> # got "begin\nunitcheck\ncheck"
> # expected "begin\nunitcheck\ncheck\nend"
> # PROG:
> # BEGIN { $| = 1; } BEGIN { print "begin\n"; } UNITCHECK { print
> "unitcheck\n"; } CHECK { print "check\n"; } INIT { print "init\n"; }
> END { print "end\n"; } print "main\n"; BEGIN { exit 0; }
> # STATUS: 0
> # Failed test 10 - UNITCHECK{exit 0} should exit at ./test.pl line 1062
> #      got "begin\nunitcheck\ncheck"
> # expected "begin\nunitcheck\ncheck\nend"
> # PROG:
> # BEGIN { $| = 1; } BEGIN { print "begin\n"; } UNITCHECK { print
> "unitcheck\n"; } CHECK { print "check\n"; } INIT { print "init\n"; }
> END { print "end\n"; } print "main\n"; UNITCHECK { exit 0; }
> # STATUS: 0
> # Failed test 11 - CHECK{exit 0} should exit at ./test.pl line 1062
> #      got "begin\nunitcheck\ncheck"
> # expected "begin\nunitcheck\ncheck\nend"
> # PROG:
> # BEGIN { $| = 1; } BEGIN { print "begin\n"; } UNITCHECK { print
> "unitcheck\n"; } CHECK { print "check\n"; } INIT { print "init\n"; }
> END { print "end\n"; } print "main\n"; CHECK { exit 0; }
> # STATUS: 0
> op/blocks.t .. Failed 3/22 subtests
>         (less 6 skipped subtests: 13 okay)
> 
> Test Summary Report
> -------------------
> op/blocks.t (Wstat: 0 Tests: 22 Failed: 3)
>   Failed tests:  9-11
> Files=1, Tests=22,  1 wallclock secs ( 0.00 usr +  0.01 sys =  0.01
> CPU)
> Result: FAIL

Reverting 64a9c780950becebc7326a31d067801ec9b187a2 fixes this, but per #132863 leads to some other problems.

I'll take a look at this next week.

Tony

---
via perlbug:  queue: perl5 status: new
https://rt.perl.org/Ticket/Display.html?id=134295

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About