Skip Menu |

This queue is for tickets about the Text-Tradition-Analysis CPAN distribution.

Report information
The Basics
Id: 113593
Status: resolved
Priority: 0/
Queue: Text-Tradition-Analysis

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

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



Subject: t/analysis.t fails (with newer Moose versions?)
My smokers report failures in t/analysis.t: ... # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 195. # Failed test 'Got expected genealogical result for rank 73' # at t/analysis.t line 190. # got: 'genealogical' # expected: 'reverted' ... (snip) ... # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 253. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 253. # Failed test 'Got a solution for the stated problem' # at t/analysis.t line 253. # Looks like you failed 271 tests of 397. t/analysis.t ........................ Dubious, test returned 254 (wstat 65024, 0xfe00) Failed 271/397 subtests Statistical analysis suggests that this failure could be caused by newer Moose versions (2.1604 and newer): **************************************************************** Regression 'mod:Moose' **************************************************************** Name Theta StdErr T-stat [0='const'] 0.0000 0.1320 0.00 [1='eq_2.1403'] -0.0000 0.1867 -0.00 [2='eq_2.1405'] 1.0000 0.1400 7.14 [3='eq_2.1600'] 0.9412 0.1358 6.93 [4='eq_2.1603'] 1.0000 0.1392 7.19 [5='eq_2.1604'] 0.0000 0.1353 0.00 [6='eq_2.1605'] 0.0000 0.1446 0.00 [7='eq_2.1700'] 0.0000 0.1867 0.00 R^2= 0.939, N= 62, K= 8 ****************************************************************
On 2016-04-06 22:15:38, SREZIC wrote: Show quoted text
> Statistical analysis suggests that this failure could be caused by > newer Moose versions (2.1604 and newer):
I think this is a red herring -- 2.1604 and 2.1605 had no substantive changes in them. I looked at how Text::Tradition::Analysis was using native array traits, and it seems to think that first_index will return undef when the element is not found. This is false -- the return value in this case is -1.
Subject: Re: [rt.cpan.org #113593] t/analysis.t fails (with newer Moose versions?)
Date: Thu, 07 Apr 2016 18:25:09 +0000
To: bug-Text-Tradition-Analysis [...] rt.cpan.org
From: Tara Andrews <tla [...] mit.edu>
I concur that the problem is unrelated to changes in Moose; it almost certainly has to do with the disappearance of a web service upon which the test relies. On Thu, Apr 7, 2016 at 6:51 PM Karen Etheridge via RT < bug-Text-Tradition-Analysis@rt.cpan.org> wrote: Show quoted text
> Queue: Text-Tradition-Analysis > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=113593 > > > On 2016-04-06 22:15:38, SREZIC wrote: >
> > Statistical analysis suggests that this failure could be caused by > > newer Moose versions (2.1604 and newer):
> > I think this is a red herring -- 2.1604 and 2.1605 had no substantive > changes in them. > > I looked at how Text::Tradition::Analysis was using native array traits, > and it seems to think that first_index will return undef when the element > is not found. This is false -- the return value in this case is -1. >
The problem was to do with a URL change in a service the tests rely on. It should be fixed in 2.0.3.
RT-Send-CC: tla [...] mit.edu
On 2016-04-11 02:53:26, AURUM wrote: Show quoted text
> The problem was to do with a URL change in a service the tests rely > on. It should be fixed in 2.0.3.
It mostly works with 2.0.3, but still there are occasional fail reports like this one: http://www.cpantesters.org/cpan/report/2d71b3c8-ffda-11e5-829f-59a5aef69d38 Is it due to the external service being unreliable? If so, then is it possible to improve the diagnostics?
On Mon Apr 11 16:33:21 2016, SREZIC wrote: Show quoted text
> On 2016-04-11 02:53:26, AURUM wrote:
> > The problem was to do with a URL change in a service the tests rely > > on. It should be fixed in 2.0.3.
> > It mostly works with 2.0.3, but still there are occasional fail > reports like this one: > http://www.cpantesters.org/cpan/report/2d71b3c8-ffda-11e5-829f- > 59a5aef69d38 > Is it due to the external service being unreliable? If so, then is it > possible to improve the diagnostics?
Actually it was due to the dependency on HTTPS, and thus LWP::Protocol::https, for the testing. Oops.