Skip Menu |

This queue is for tickets about the Future-AsyncAwait CPAN distribution.

Report information
The Basics
Id: 124351
Status: stalled
Priority: 0/
Queue: Future-AsyncAwait

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

Bug Information
Severity: (no value)
Broken in:
  • 0.15
  • 0.16
Fixed in: (no value)



Subject: Fails on threaded perls below 5.24
As yet unsure the reasons why, because I can't see the actual test reports, but there's a definite trend on http://fast-matrix.cpantesters.org/?dist=Future-AsyncAwait+0.15 for below-5.24 perls to fail, and most of those failures are on threaded perls. -- Paul Evans
On Wed Feb 07 07:25:38 2018, PEVANS wrote: Show quoted text
> As yet unsure the reasons why, because I can't see the actual test > reports, but there's a definite trend on
A test report generated by ilmari, on 5.16.3 + threads -- Paul Evans
Subject: perl-5.16.3+threads.txt
t/00use.t .............. ok t/01async-immediate.t .. ok t/02await-immediate.t .. ok # Failed test 'async/await respects stack discipline' # at t/03await.t line 56. # Structures begin differing at: # $got->[2][3] = undef # $expected->[2][3] = '6' # Looks like you failed 1 test of 17. t/03await.t ............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/17 subtests # Failed test '$f2 created' # at t/04await-twice.t line 31. Can't call method "done" on an undefined value at t/04await-twice.t line 33. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 2. t/04await-twice.t ...... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 1/2 subtests # Failed test '$fret yields correct result for mid-expression await' # at t/05await-expr.t line 23. # got: '3' # expected: '6' # Looks like you failed 1 test of 1. t/05await-expr.t ....... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/06await-nested.t ..... ok Can't use string ("") as a subroutine ref while "strict refs" in use at t/10pad.t line 38. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 3. t/10pad.t .............. Dubious, test returned 255 (wstat 65280, 0xff00) All 3 subtests passed # Failed test '$fret now ready after done' # at t/11contexts.t line 30. # got: undef # expected: 'true' t/11contexts.t ......... Failed 1/5 subtests # Failed test 'result of async sub' # at t/12closure.t line 56. # got: '1' # expected: '45' # Looks like you failed 1 test of 4. t/12closure.t .......... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests # Failed test '$fret now ready after done' # at t/20context-block.t line 39. # got: undef # expected: 'result' # Failed test '$fret now ready after done with padrange' # at t/20context-block.t line 65. # got: undef # expected: 'done' # Looks like you failed 2 tests of 6. t/20context-block.t .... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/6 subtests # Failed test '$fret now ready after while loop with body finishes' # at t/21context-while.t line 31. # got: undef # expected: 'end while' # Failed test '$fret now ready after while loop with cond finishes' # at t/21context-while.t line 52. # got: undef # expected: 'end while' # Failed test '$fret now ready after while loop with last' # at t/21context-while.t line 72. # got: undef # expected: 'end while' # Failed test '$fret now ready after while loop with next' # at t/21context-while.t line 95. # got: undef # expected: 'end while' # Looks like you failed 4 tests of 4. t/21context-while.t .... Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests # Failed test '$fret now ready after foreach(ARRAY) loop' # at t/22context-foreach.t line 31. # got: undef # expected: 'end foreach' # Failed test '$fret now ready after foreach(LIST) loop' # at t/22context-foreach.t line 53. # got: undef # expected: 'end foreach' # Failed test '$fret now ready after foreach(LAZY IV) loop' # at t/22context-foreach.t line 75. # got: undef # expected: 'end foreach' # Failed test '$fret now ready after foreach(LAZY SV) loop' # at t/22context-foreach.t line 97. # got: undef # expected: 'end foreach' # Failed test '$fret now ready after foreach with two awaits' # at t/22context-foreach.t line 119. # got: undef # expected: 'awaited twice' # Looks like you failed 5 tests of 7. t/22context-foreach.t .. Dubious, test returned 5 (wstat 1280, 0x500) Failed 5/7 subtests # Failed test '$fret->failure message contains function name' # at t/40croak.t line 24. # 'Can't use string ("") as a subroutine ref while "strict refs" in use at t/40croak.t line 18. # ' # doesn't match '(?^:main::with_failure)' # Looks like you failed 1 test of 1. t/40croak.t ............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/80await+try.t ........ skipped: Syntax::Keyword::Try >= 0.07 is not available t/99pod.t .............. skipped: Test::Pod 1.00 required for testing POD Test Summary Report ------------------- t/03await.t (Wstat: 256 Tests: 17 Failed: 1) Failed test: 6 Non-zero exit status: 1 t/04await-twice.t (Wstat: 65280 Tests: 2 Failed: 1) Failed test: 2 Non-zero exit status: 255 Parse errors: No plan found in TAP output t/05await-expr.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/10pad.t (Wstat: 65280 Tests: 3 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output t/11contexts.t (Wstat: 11 Tests: 5 Failed: 1) Failed test: 2 Non-zero wait status: 11 Parse errors: No plan found in TAP output t/12closure.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 3 Non-zero exit status: 1 t/20context-block.t (Wstat: 512 Tests: 6 Failed: 2) Failed tests: 3, 5 Non-zero exit status: 2 t/21context-while.t (Wstat: 1024 Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 t/22context-foreach.t (Wstat: 1280 Tests: 7 Failed: 5) Failed tests: 1-5 Non-zero exit status: 5 t/40croak.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=16, Tests=74, 1 wallclock secs ( 0.06 usr 0.02 sys + 0.90 cusr 0.10 csys = 1.08 CPU) Result: FAIL Failed 10/16 test programs. 17/74 subtests failed.
Retested just now using Future::AsyncAwait 0.16 on perl 5.22.3 + threads and it runs fine. But definitely still seeing some failures on cpantesters on 5.20 and earlier, so I suspect the issue still remains. -- Paul Evans
For now I'm just going to declare thready perls 5.20 and earlier as "OS unsupported", so they turn into NA reports. Since it works from 5.22 onwards, that's already 4 major releases of perl that are supported under threads, which I feel is reasonable to be getting on with. If anyone really wants thready builds of earlier perls to be supported, then they can enquire and I may look into it, but for now I'll just park this one. -- Paul Evans