Yes, I've received similar problematic reports from you, for example: http://www.cpantesters.org/cpan/report/f06f0a70-7095-11e6-b0d4-db1a5d222160 http://www.cpantesters.org/cpan/report/f066dbca-7095-11e6-b0d4-db1a5d222160
I believe some testers check over all their reports before sending them; perhaps you could do this for a while as well, to be sure that the failure reports you are submitting are genuine as opposed to a misconfigured system? On Sat, Sep 3, 2016 at 3:43 PM, Alceu R. de Freitas Jr. via cpan-testers-discuss <cpan-testers-discuss@perl.org> wrote: > Hello all, > > I just receive this e-mail and would like to know if any of you share the > same idea regarding my Smoker having issues, since most probably all of you > are also contributors to CPAN. > > Considering the results of OpenBSD Tester Leaderboard ( > http://stats.cpantesters.org/leaders/leaders-openbsd-all.html) nobody > else is running a Smoker over OpenBSD. > > Thanks, > > Alceu > > > > ----- Mensagem encaminhada ----- > *De:* Peter Flanigan <no-re...@roxsoft.co.uk> > *Para:* arfrei...@cpan.org > *Enviadas:* Sábado, 3 de Setembro de 2016 14:01 > *Assunto:* Your smoke testing reports > > Alceu, > > Please consider the following reports from your smoker > > http://www.cpantesters.org/cpan/report/efe5df0c-7095- > 11e6-b0d4-db1a5d222160 > > http://www.cpantesters.org/cpan/report/f0892d4c-7095- > 11e6-b0d4-db1a5d222160 > > Your smoker has now reached the point where it cannot even > run the tool chain. Please either; > > 1. Take it offline (I know I'm not the only one who has > had issues with the reports your smoker generates) so > this would be a popular solution > > 2. Put my PAUSE id (pjfl) in your configuration to > prevent it from smoking any of my distributions > > -- > > TIA > > >
