develooper Front page | perl.perl5.porters | Postings from February 2008

Re: Change 33313 causing failures

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
February 15, 2008 02:11
Subject:
Re: Change 33313 causing failures
Message ID:
20080215101058.GR38653@plum.flirble.org
On Fri, Feb 15, 2008 at 10:50:51AM +0100, Rafael Garcia-Suarez wrote:
> On 14/02/2008, Jerry D. Hedden <jdhedden@cpan.org> wrote:
> > Change 33313 is causing test suite failures:
> >
> >  t/op/pat......................................................FAILED--unexpected
> >  output at test 1308
> >  t/op/pat_thr..................................................FAILED--unexpected
> >  output at test 1308
> 
> That happens with TEST, not with harness, which explains why I didn't saw it :(
> 
> >  Capturing the relevant test output:
> >
> >  ok 1307 - $+{C} Line 3788
> >  not ok 1308 - $+{D}     Line 3788 # TODO 1
> >  not # Failed test at line 3788
> >  # expected: '???xfoo'
> >  #   result: ''
> >  ok 1309 - 18446744073709551615~=/(?<D>(?<A>foo)s+(?<B>bar)?s+(?<C>baz))/        Line
> >  3793
> >
> >  The 'failure' is the extra 'not' before the pound sign.
> >  I tried to figure out what's causing it, but couldn't.

Is it possible to put the TAP parser into a strict mode where it would detect
and fault these sorts of things?

(I think most specifically "these things" are lines that aren't /^ok/,
/^not ok/ or /^#/ )

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About