On 15 Feb 2008, at 10:10, Nicholas Clark wrote:
On Fri, Feb 15, 2008 at 10:50:51AM +0100, Rafael Garcia-Suarez wrote:
On 14/02/2008, Jerry D. Hedden <[EMAIL PROTECTED]> 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 /^#/ )
I presume the lines beginning with # above are on STDERR and that what
you're seeing is a mix of STDERR and STDOUT? So what the parser is
seeing on STDOUT is either
not ok 1309
or
not
ok 1309
?
Unfortunately that second version is a special case for tests on VMS
that don't output "not" and "ok" on the same line - I wonder if that's
what's causing the problem.
--
Andy Armstrong, Hexten
