Re: What's the common denominator in these NYTProf failures?

On Wed, Jan 28, 2009 at 8:50 AM, Tim Bunce wrote: > I'm strugling to find a common denominator in these test results: > > > http://bbbike.radzeit.de/~slaven/cpantestersmatrix.cgi?dist=Devel-NYTProf+2.07_94 > > Th

Re: TAP and the exit code

Eric Wilhelm wrote: > # from Michael G Schwern > # on Tuesday 27 January 2009 18:16: > >> For example, if a test program knows that it is going to >> exit abnormally, even after it has finished emitting TAP according to >> its plan, it should emit one final "not ok" line before exiting. > > So, >

RE: What's the common denominator in these NYTProf failures?

On Wed, 28 Jan 2009, David Cantrell wrote: > On Wed, Jan 28, 2009 at 03:56:28PM +, Martin Evans wrote: > > Not intel 64 bit int and multi-threaded perl then? Looked common to > > all the failures and unless I missed one looked missing from the > > successes. > > It passed on what I thought were

Re: TAP and the exit code

# from Ovid # on Wednesday 28 January 2009 07:57: >> How would such a UI handle situations where all the tests pass, but >> the plan fails (too many tests, too few tests or a missing plan)? If >> those become flashing/stripped lines as well, then the current spec >> works as written. If not, we sh

Re: What's the common denominator in these NYTProf failures?

On Wed, Jan 28, 2009 at 03:56:28PM +, Martin Evans wrote: > Tim Bunce wrote: > >I'm strugling to find a common denominator in these test results: > > > >http://bbbike.radzeit.de/~slaven/cpantestersmatrix.cgi?dist=Devel-NYTProf+2.07_94 > Not intel 64 bit int and multi-threaded perl then? Looked

Re: What's the common denominator in these NYTProf failures?

On Wed, Jan 28, 2009 at 01:50:05PM +, Tim Bunce wrote: > I'm strugling to find a common denominator in these test results: > http://bbbike.radzeit.de/~slaven/cpantestersmatrix.cgi?dist=Devel-NYTProf+2.07_94 Try http://www.cpantesters.org/show/Devel-NYTProf.html (requires Javascript), then in

Re: TAP and the exit code

- Original Message > From: Gaurav Vaidya > As I understand it, the idea behind the final 'not ok' isn't as an > additionally > failed test, but as a way of forcing the plan to fail. That'll work as long > as > you don't have 'N' tests, and exactly 'N-1' tests finish before the suite

Re: What's the common denominator in these NYTProf failures?

Tim Bunce wrote: I'm strugling to find a common denominator in these test results: http://bbbike.radzeit.de/~slaven/cpantestersmatrix.cgi?dist=Devel-NYTProf+2.07_94 It would be wonderful if there was some tool that would analyse the perl -V output and help identify the combinations of settings

Re: TAP and the exit code

Hey, On Jan 28, 2009, at 5:19 PM, Ovid wrote: That being said, 'not ok - test exited prematurely' is not terribly structured and doesn't necessarily let an advanced TAP consumer present this information any better. As I understand it, the idea behind the final 'not ok' isn't as an additiona

What's the common denominator in these NYTProf failures?

I'm strugling to find a common denominator in these test results: http://bbbike.radzeit.de/~slaven/cpantestersmatrix.cgi?dist=Devel-NYTProf+2.07_94 It would be wonderful if there was some tool that would analyse the perl -V output and help identify the combinations of settings associated with fai

Re: TAP and the exit code

Eric Wilhelm wrote: 1. TAP::Harness should store that when archiving? It would be nice if TAP::Harness::Archive noted the exit code in the meta.yml file included in the archive. -- Michael Peters Plus Three, LP

Re: TAP and the exit code

- Original Message > From: Eric Wilhelm > >For example, if a test program knows that it is going to > >exit abnormally, even after it has finished emitting TAP according to > > its plan, it should emit one final "not ok" line before exiting. > > So, > > 1. TAP::Harness should store t