name}{$osvers}{$archname}{$tester}).
Otherwise,
$unique{$version}{$perl}{$osname}{$osvers}{$archname}{$tester} is set
to the report ID (arbitrary).
- The report order is reversed (i.e., lowest ID to highest) by changing
"push @reports, $report" to "unshift @reports, $report"
> Subject: Re: FAIL threads-1.09 MSWin32-x86-multi-thread 4.0
> From: Max Maischein <[EMAIL PROTECTED]>
> Date: Wed, March 15, 2006 4:43 pm
> To: "Jerry D. Hedden" <[EMAIL PROTECTED]>
>
> Jerry D. Hedden wrote:
> > Would you mind running this again?
Adam Kennedy wrote:
> Part of the problem comes in defining "bogus".
This is a red herring. Consider the original proposal:
If a tester sends in a 'updated' report (matching all the appropriate
criteria), then the update should overwrite/mask the original.
There is no need to define the criteri
Today, I filed a bug report against CPANPLUS because it
sometimes fails to detect missing prerequisites, resulting
in bogus FAIL reports being generated against modules:
http://rt.cpan.org/Ticket/Display.html?id=18144
Here are two examples of such failures:
http://www.nntp.perl.org/group/perl
