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

2009-01-31 Thread Tim Bunce 
On Thu, Jan 29, 2009 at 10:16:15PM +0100, Andreas J. Koenig wrote:
> > On Wed, 28 Jan 2009 13:50:05 +, Tim Bunce  
> > said:
> 
>   > 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 failures - assuming there is a pattern.
> 
> The tool exists: CPAN::Testers::ParseReport comes with the program
> ctgetreports. Pay attention to the --solve parameter.

Wonderful! Many thanks Andreas.

> Unfortunately,
> in your case no findings except what David Golden already mentioned:
> 
> Regression 'meta:from'
> 
> Name   Theta  StdErr T-stat   
> [0='const']   1.  0.1574   6.35
> [...]
> [2='eq_bin...@cpan.org'] -0.9412  0.1619  -5.81
> 
> which tells us that normally the tests succeed but if the tester is
> bin...@cpan.org, there is only 6% PASS.
> 
> Indeed, bingos reported one PASS: 3151674

I'm coming to the conclusion that should release anyway as *no one* has
been able to reproduce the specific fault in the bingos failures.

Very strange though...

Tim.

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

2009-01-30 Thread Andreas J. Koenig 
> On Wed, 28 Jan 2009 13:50:05 +, Tim Bunce  said:

  > 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 failures - assuming there is a pattern.

The tool exists: CPAN::Testers::ParseReport comes with the program
ctgetreports. Pay attention to the --solve parameter. Unfortunately,
in your case no findings except what David Golden already mentioned:

Regression 'meta:from'

Name   Theta  StdErr T-stat   
[0='const']   1.  0.1574   6.35
[...]
[2='eq_bin...@cpan.org'] -0.9412  0.1619  -5.81

which tells us that normally the tests succeed but if the tester is
bin...@cpan.org, there is only 6% PASS.

Indeed, bingos reported one PASS: 3151674


-- 
andreas

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

2009-01-29 Thread Vincent Pit 

> The common denominator appears to be that they're all from BinGOs.  Which
> means they're all CPANPLUS-based smoke tests running on virtual machines.
> I'm not sure what impact that has.
>   
I'm also using CPANPLUS with 64 bits threaded perls for smoking on linux
and Solaris, and I couldn't make it to fail.
So I really don't know what's causing this.

Vincent.

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

2009-01-28 Thread David Golden 
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
>
>
The common denominator appears to be that they're all from BinGOs.  Which
means they're all CPANPLUS-based smoke tests running on virtual machines.
I'm not sure what impact that has.

He's pretty responsive so you can email him at his cpan.org address.
(bin...@...)

For future reference, these kinds of questions are better directed to the
cpan-testers-discuss mailing list, which is regularly monitored by most of
the high-volume testers.

-- David

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

2009-01-28 Thread Jan Dubois 
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 my 64 bit threaded AMD builds, but
> from looking carefully at my -V it seems that they might not be 64 bit
> after all - despite building with '-de -Duse64bitall -Dusethreads', I
> have intsize=4 (but longsize=8 and ivtype=long), so I'm not sure if my
> perl is truly 64 bit or not.
> http://www.nntp.perl.org/group/perl.cpan.testers/2009/01/msg3116778.html

That is a 64-bit Perl. The important %Config value to look at is
ptrsize. If it is set to 8, then you have a full 64-bit Perl. If the
ivtype is set to a type that is 8 bytes, but ptrsize is 4, then you have
a 32-bit Perl with 64-bit integers (which from the OS point of view is a
32-bit process).

Cheers,
-Jan

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

2009-01-28 Thread David Cantrell 
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 common to all 
> the failures and unless I missed one looked missing from the successes.

It passed on what I thought were my 64 bit threaded AMD builds, but from
looking carefully at my -V it seems that they might not be 64 bit after
all - despite building with '-de -Duse64bitall -Dusethreads', I have
intsize=4 (but longsize=8 and ivtype=long), so I'm not sure if my perl
is truly 64 bit or not.
  http://www.nntp.perl.org/group/perl.cpan.testers/2009/01/msg3116778.html

-- 
header   FROM_DAVID_CANTRELLFrom =~ /david.cantrell/i
describe FROM_DAVID_CANTRELLMessage is from David Cantrell
scoreFROM_DAVID_CANTRELL15.72 # This figure from experimentation

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

2009-01-28 Thread David Cantrell 
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 the drop-downs on the right, choose:

dist maturity: all releases

then select 2.07_94 in the "version summary" box below that.  You can
then use the dropdowns to switch back and forth between PASS and FAIL
reports to look for patterns.

I see that all the failures are on architecture *-thread-multi-64int.
There is also one pass with that, but that's also the only result for
perl 5.8.7.

This tool will convert from a report id to the tester's email address,
hopefully one of them will be able to help you:
  http://stats.cpantesters.org/cpanmail.html

-- 
David Cantrell | Enforcer, South London Linguistic Massive

"Every normal man must be tempted at times to spit on his hands,
 hoist the black flag, and begin slitting throats." -- H. L. Mencken

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

2009-01-28 Thread Martin Evans 

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 associated
with failures - assuming there is a pattern.

Meanwhile, can anyone reproduce the failure? (I've not been able to.)

Tim.




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.


Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

What's the common denominator in these NYTProf failures?

2009-01-28 Thread Tim Bunce 
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 failures - assuming there is a pattern.

Meanwhile, can anyone reproduce the failure? (I've not been able to.)

Tim.