Skip Menu |

This queue is for tickets about the Tickit-Widget-Scroller CPAN distribution.

Report information
The Basics
Id: 120636
Status: open
Priority: 0/
Queue: Tickit-Widget-Scroller

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

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



Subject: Tests fail (with Tickit 0.62?)
On my smoker systems I see the following test failures: ... $win->clear has been removed at t/12resize-bottom.t line 35. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 1. t/12resize-bottom.t ... Dubious, test returned 255 (wstat 65280, 0xff00) All 1 subtests passed $win->clear has been removed at t/12resize-top.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 1. t/12resize-top.t ...... Dubious, test returned 255 (wstat 65280, 0xff00) All 1 subtests passed ... This seems to happen with Tickit 0.62. Statistical analysis: **************************************************************** Regression 'mod:Tickit::Pen' **************************************************************** Name Theta StdErr T-stat [0='const'] 1.0000 0.0381 26.24 [1='eq_0.58'] 0.0000 0.1292 0.00 [2='eq_0.59'] 0.0000 0.1787 0.00 [3='eq_0.60'] -0.1667 0.0561 -2.97 [4='eq_0.61'] 0.0000 0.0546 0.00 [5='eq_0.62'] -1.0000 0.0512 -19.52 R^2= 0.871, N= 88, K= 6 ****************************************************************
On Thu Mar 16 14:57:59 2017, SREZIC wrote: Show quoted text
> On my smoker systems I see the following test failures: > > ... > $win->clear has been removed at t/12resize-bottom.t line 35. > # Tests were run but no plan was declared and done_testing() was not seen. > # Looks like your test exited with 255 just after 1.
Show quoted text
> This seems to happen with Tickit 0.62. Statistical analysis:
Oh; yes. I had a fix for that in local development copy that I've not yet CPAN'ed. I should do that. It is at least just a test-time failure; the actual running code is fine. -- Paul Evans