Skip Menu |

This queue is for tickets about the App-TestOnTap CPAN distribution.

Report information
The Basics
Id: 121332
Status: resolved
Priority: 0/
Queue: App-TestOnTap

People
Owner: knth [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

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



Subject: t/11-fail.t ... fails (0.032)
Some (but not all) of my smokers show the following failure: ... # Failed test 'Expected failure' # at t/11-fail.t line 16. # '# Looks like you failed 1 test of 3.' # doesn't match '(?^:^At least 1 test\(s\) failed!$)' # Looks like you failed 1 test of 6. t/11-fail.t .................. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/6 subtests ... I don't see a pattern across perl versions (fails happen for perl 5.10.1 .. 5.25.12) or OS versions (linux + freebsd).
Hi, Hi, Thanks for calling it in - I recently noticed a failure in this test for a prior version, and tracked it down to changes in Test::More (or rather Test::Simple where it resides), and found the change: 1.302077 2017-02-19 14:34:30-08:00 America/Los_Angeles (TRIAL RELEASE) - Fix #762, newlines for todo subtest - Revisit #637, fix rare race condition it created which caused a previously empty line to disappear and throw my tests out of whack. All made sense with what I could see and I could also repro it, so I upped my dependencies, changed the test and submitted a new version. However... I now got a flurry of fails showing the reverse problem, so apparently there's more to it. I've just submitted a new version with a dependency on the the full & latest Test::Simple package to see if this makes the shoe drop . If it remains I'll just have to try harder to reproduce locally. ken1
Can't repro it, and after the latest flurry of fails, I bit the bullet and rewrote the tests slightly. It's just a matter of sometimes getting a new line on some output and sometimes not, which has no bearing on correctness. I hope 0.033 squashes the problem. ken1
We'll after rewriting the test slightly it now passes, so I'll consider this fixed. ken1