That's what I did on Sunday - all reports go to file, and then anything
matching a few errors gets deleted, I check the rest of the fails, then
submit the whole batch. Here are the automatic filters:
if ($reporter->{'_report'} =~ /MISSING PREREQUISITES/ ||
$reporter->{'_report'} =~ /Could not execute
\("C:\\cpantest\\perl\d+\\bin\\perl\.exe"/ ||
$reporter->{'_report'} =~ /Can't locate loadable object for module/ ||
$reporter->{'_report'} =~ /ERROR LOADING MODULE: /) {
On Tue, Dec 23, 2014 at 6:58 AM, Andreas Koenig <
andreas.koenig.7os6v...@franz.ak.mind.de> wrote:
> >>>>> On Sun, 21 Dec 2014 10:27:01 -0500, Dan Collins <dcolli...@gmail.com>
> said:
>
> dc> Is it perhaps a bug (on CPANPLUS? on CPANPLUS::YACSmoke?) that it
> recognized:
>
> Have you stopped your smoker for further investigation? I mean that
> smoking with a potentially broken program may wreak havoc on a sensitive
> infrastructure. I just found these three new fails for example:
>
>
> http://matrix.cpantesters.org/?dist=Class-C3-Componentised%201.001000;os=mswin32;reports=1
>
> They look horribly broken and come after 9000 passes. Looks very
> suspicious. Similar here:
>
> http://matrix.cpantesters.org/?dist=CGI-Simple%201.115;os=mswin32;reports=1
>
> Could you perhaps run the smoker in slow motion so that it stops before
> sending a fail report and asks for manual confirmation or something like
> that?
>
> --
> andreas
>
