Skip Menu |

This queue is for tickets about the Device-BusPirate CPAN distribution.

Report information
The Basics
Id: 129316
Status: resolved
Priority: 0/
Queue: Device-BusPirate

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

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



Subject: Test suite fails with perl 5.26.x and older
See subject. Log excerpt with the failing parts: ... Future::AsyncAwait panic: TODO: Unsure how to handle savestack entry of 10 t/20spi.t ..... All 4 subtests passed # Failed test '->read returns bytes' # at t/30i2c.t line 76. # got: 'V' # expected: 'Vx' # Failed test '->read: all methods called' # at t/30i2c.t line 79. Expected syswrite("04"), got ("03") at /home/cpansand/.cpan/build/2019042600/Device-BusPirate-0.18-uWZBts/blib/lib/Device/BusPirate.pm line 152. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 8. TODO: free saved slot type 49 TODO: free frame->itervar t/30i2c.t ..... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 2/8 subtests ... t/20spi.t seems to fail with a SIGABRT.
On 2019-04-26 02:11:26, SREZIC wrote: Show quoted text
> See subject. Log excerpt with the failing parts: > > ... > Future::AsyncAwait panic: TODO: Unsure how to handle savestack entry > of 10 > t/20spi.t ..... > All 4 subtests passed > > # Failed test '->read returns bytes' > # at t/30i2c.t line 76. > # got: 'V' > # expected: 'Vx' > > # Failed test '->read: all methods called' > # at t/30i2c.t line 79. > Expected syswrite("04"), got ("03") at > /home/cpansand/.cpan/build/2019042600/Device-BusPirate-0.18- > uWZBts/blib/lib/Device/BusPirate.pm line 152. > # Tests were run but no plan was declared and done_testing() was not > seen. > # Looks like your test exited with 255 just after 8. > TODO: free saved slot type 49 > TODO: free frame->itervar > t/30i2c.t ..... > Dubious, test returned 255 (wstat 65280, 0xff00) > Failed 2/8 subtests > ... > > t/20spi.t seems to fail with a SIGABRT.
Sometimes the test failure looks differently: ... Future::AsyncAwait panic: ARGH CXt_LOOP_LIST frame tried to steal stack values or marks t/30i2c.t ..... All 5 subtests passed ... Here it also fails with a SIGBART.
These are two (new) separate issues with Future::AsyncAwait. I've opened some tickets there instead. https://rt.cpan.org/Ticket/Display.html?id=129319 https://rt.cpan.org/Ticket/Display.html?id=129320 -- Paul Evans
On Fri Apr 26 08:21:41 2019, PEVANS wrote: Show quoted text
> These are two (new) separate issues with Future::AsyncAwait. I've > opened some tickets there instead. > > https://rt.cpan.org/Ticket/Display.html?id=129319 > > https://rt.cpan.org/Ticket/Display.html?id=129320
With those two fixed, this issue is resolved. -- Paul Evans