Skip Menu |
 

This queue is for tickets about the Syntax-Keyword-Try CPAN distribution.

Report information
The Basics
Id: 129975
Status: open
Priority: 0/
Queue: Syntax-Keyword-Try

People
Owner: Nobody in particular
Requestors: leonerd-cpan [...] leonerd.org.uk
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.10
Fixed in: (no value)

Attachments


Subject: t/11loop.t stalls on perl 5.31.2
Download (untitled) / with headers
text/plain 842b
(from https://rt.perl.org/Public/Bug/Display.html?id=134258) Show quoted text
> The problem is that this distro's t/11loop.t now hangs indefinitely and > has to be Ctrl-C-ed. All other files in the distro's test suite PASS.
... Show quoted text
> This commit removes the deferred mechanism, and instead > makes use of the newish OP_PARENT mechanism to iterate over > the optree, following each kid, then back up via the parent > pointer to the next sibling etc.
... Ah. I wonder then, whether this might be something that Syntax::Keyword::Try has to fix. I do some rather awkward optree fiddling in there, and I don't recall needing to take care of OP_PARENT so far. https://metacpan.org/source/PEVANS/Syntax-Keyword-Try-0.10/lib/Syntax/Keyword/Try.xs#L257 https://metacpan.org/source/PEVANS/Syntax-Keyword-Try-0.10/lib/Syntax/Keyword/Try.xs#L283 -- Paul Evans
Download (untitled) / with headers
text/plain 370b
Confirmed reproducible: $ bleadperl -v This is perl 5, version 31, subversion 2 (v5.31.2 (v5.31.1-122-g82651abe60)) built for x86_64-linux ... $ bleadperl Build test t/00use.t .............. ok t/01trycatch.t ......... ok t/02tryfinally.t ....... ok t/03trycatchfinally.t .. ok t/10snail.t ............ ok t/11loop.t ............. ^C -- Paul Evans
Download (untitled) / with headers
text/plain 1.3k
Actually, further debugging reveals more breakage on any -DDEBUGGING perl, because of extra assertion failures. perl: op.c:1888: Perl_scalar: Assertion `0' failed. Aborted on most .t files. bisected down to this core perl commit: db18005b26986d1d422fcb53989eece313134db5 is the first bad commit commit db18005b26986d1d422fcb53989eece313134db5 Author: David Mitchell <davem@iabyn.com> Date: Wed May 29 11:03:26 2019 +0100 Perl_scalar() tail-call optimise The part of this function that scans the children of e.g. $scalar = do { void; void; scalar } applying scalar context only to the last child: tail call optimise that call to Perl_scalar(). It also adds some extra 'warnings' tests. An earlier attempt at this patch caused some unrelated tests to start emitting spurious 'useless in void context' messages, which are covered by the new tests. This also showed up that the current method for updating PL_curcop while descending optrees in Perl_scalar/scalarvoid/S_scalarseq is a bit broken. It gets updated every time a newstate op is seen, but haphazardly (and sometimes wrongly) restored to &PL_compiling when going back up the tree. One of the tests is TODO based on PL_curcop being wrong and so the 'no warnings "void"' leaking into an outer scope. This commit maintains the status quo. -- Paul Evans
Download (untitled) / with headers
text/plain 1.5k
On Tue Jul 09 15:54:22 2019, PEVANS wrote: Show quoted text
> Actually, further debugging reveals more breakage on any -DDEBUGGING > perl, because of extra assertion failures. > > perl: op.c:1888: Perl_scalar: Assertion `0' failed. > Aborted > > on most .t files. > > bisected down to this core perl commit: > > db18005b26986d1d422fcb53989eece313134db5 is the first bad commit > commit db18005b26986d1d422fcb53989eece313134db5 > Author: David Mitchell <davem@iabyn.com> > Date: Wed May 29 11:03:26 2019 +0100 > > Perl_scalar() tail-call optimise > > The part of this function that scans the children of e.g. > > $scalar = do { void; void; scalar } > > applying scalar context only to the last child: tail call optimise > that > call to Perl_scalar(). > > It also adds some extra 'warnings' tests. An earlier attempt at this > patch caused some unrelated tests to start emitting spurious 'useless > in > void context' messages, which are covered by the new tests. > > This also showed up that the current method for updating PL_curcop > while descending optrees in Perl_scalar/scalarvoid/S_scalarseq is a > bit > broken. It gets updated every time a newstate op is seen, but > haphazardly > (and sometimes wrongly) restored to &PL_compiling when going back up > the > tree. One of the tests is TODO based on PL_curcop being wrong and so > the > 'no warnings "void"' leaking into an outer scope. > > This commit maintains the status quo.
Additional failures found when testing this distribution against perl-5.31.2 on FreeBSD-12, using cpanm as the installer: see attached.
Subject: rtc122975-test-failures.txt
### Syntax-Keyword-Try test_output => [ "Building and testing Syntax-Keyword-Try-0.10", "Building Syntax-Keyword-Try", "cc -I/home/jkeenan/var/tad/testing/perl-5.31.2/lib/5.31.2/amd64-freebsd-thread-multi/CORE -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -DPIC -fPIC -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_FORTIFY_SOURCE=2 -O2 -pipe -fstack-protector -fno-strict-aliasing -o lib/Syntax/Keyword/Try.o lib/Syntax/Keyword/Try.c", "ExtUtils::Mkbootstrap::Mkbootstrap('blib/arch/auto/Syntax/Keyword/Try/Try.bs')", "cc -shared -L/usr/local/lib -fstack-protector-strong -o blib/arch/auto/Syntax/Keyword/Try/Try.so lib/Syntax/Keyword/Try.o", "t/00use.t .............. ok", "t/01trycatch.t ......... ", "No subtests run ", "t/02tryfinally.t ....... ", "No subtests run ", "t/03trycatchfinally.t .. ok", "t/10snail.t ............ ok", "-> FAIL Timed out (> 1800s). Use --verbose to retry.", [Syntax-Keyword-Try-0.10] $ thisprove t/12return.t t/13die-in-finally.t t/14try-localises.t t/20try-do.t t/21try-do-finally.t t/80await+try.t t/90rt123547.t t/90rt125971.t t/99pod.t t/12return.t .......... No subtests run t/13die-in-finally.t .. ok 1 - die in both try{} and finally{} is still fatal ok 2 - die in finally{} does not corrupt $@ 1..2 ok t/14try-localises.t ... ok 1 - $@ before try/catch ok 2 - $@ after try/catch 1..2 ok t/20try-do.t .......... No subtests run t/21try-do-finally.t .. No subtests run t/80await+try.t ....... # Future::AsyncAwait 0.30, Syntax::Keyword::Try 0.10 ok 1 - $fdone for successful await in try/catch ok 2 - $ffail for failed await in try/catch ok 3 - $fdone for successful await in try/catch with return ok 4 - fallthrough after try{return} did not happen ok 5 - $fret for await in try/finally 1..5 ok t/90rt123547.t ........ ok 1 - try/catch/finally correct result ok 2 - try/catch/finally correct result ok 3 - Did not crash 1..3 ok t/90rt125971.t ........ ok 1 - No extra data in return 1..1 ok t/99pod.t ............. 1..1 ok 1 - POD test for blib/lib/Syntax/Keyword/Try.pm ok Test Summary Report ------------------- t/12return.t (Wstat: 139 Tests: 0 Failed: 0) Non-zero wait status: 139 Parse errors: No plan found in TAP output t/20try-do.t (Wstat: 139 Tests: 0 Failed: 0) Non-zero wait status: 139 Parse errors: No plan found in TAP output t/21try-do-finally.t (Wstat: 139 Tests: 0 Failed: 0) Non-zero wait status: 139 Parse errors: No plan found in TAP output Files=9, Tests=14, 2 wallclock secs ( 0.08 usr 0.03 sys + 0.90 cusr 0.83 csys = 1.84 CPU) Result: FAIL


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.