Hi Alceu, it looks like you're using OpenBSD's system perl (PERL=/usr/bin/perl appears in the reports). A possibility is that this perl is heavily patched and now broken for even simple things like reading a META.yml file. If this is the case, then it would be good to find out, maybe with the help of the OpenBSD guys.
Maybe the reports would be better if you would compile perl yourself? As for checking reports: I am doing this, at least the non-pass reports, and have some scripts to help in this workflow. One of the scripts is this one: https://github.com/eserte/srezic-misc/blob/master/scripts/ctr_good_or_invalid.pl I can give you assistance if you want to go this way (but it's still time-consuming!). Regards, Slaven "Alceu R. de Freitas Jr." via cpan-testers-discuss <cpan-testers-discuss@perl.org> writes: > Hello Karen, > Thanks for the feedback. > My smoker uses a minicpan mirror, but somehow the CPAN client kept the > indexes outdated and was not refreshing from the mirror, even though I was > updating (the mirror) from time to time. After checking it, even "upgrade" > from the CPAN stopped working as supposed (trace show the error was coming > from CPAN::SQLite, which was outdated). > > I didn't notice any issue so far... I have a single OpenBSD smoker, it is > months old and was not getting 100% failures for all distributions attempted. > Its off now and I'm upgrading/reinstalling as errors come by and discarding > the tests results. I'll keep an eye. I configured the smoker to install > modules on success, which surely make this more complicated. > > But I don't think its feasible to check all reports from time to time after I > think its ready. Any tips on that would be appreciated. > > I'm willing to fix the smoker as long as I got a positive feedback (like > yours). On the other hand, "turn off your smoker or block my id" hardly > qualifies as positive. > > > De: Karen Etheridge <p...@froods.org> > Para: Karen Etheridge <p...@froods.org> > Cc: Alceu R. de Freitas Jr. via Cpan-testers-discuss > <cpan-testers-discuss@perl.org>; Alceu R. de Freitas Jr. > <glasswal...@yahoo.com.br> > Enviadas: Sábado, 3 de Setembro de 2016 20:13 > Assunto: Re: Your smoke testing reports > > And here are some more, where a segmentation fault happened for no apparent > reason: > > http://www.cpantesters.org/cpan/report/70299f0a-4f8f-11e6-af52-86b6688db7f4 > http://www.cpantesters.org/cpan/report/2e821c8e-6723-11e6-b00a-ef039efd898b > http://www.cpantesters.org/cpan/report/160e6f0c-4ee8-11e6-8ccd-ed0cba742ec1 > http://www.cpantesters.org/cpan/report/fe12276a-4931-11e6-84ff-dfbf4e0f064e > http://www.cpantesters.org/cpan/report/fd165cd2-4931-11e6-84ff-dfbf4e0f064e > http://www.cpantesters.org/cpan/report/cdbcef6e-3f1d-11e6-a514-8183992ad5f0 > http://www.cpantesters.org/cpan/report/cbb2b0c8-3f1d-11e6-a514-8183992ad5f0 > > > On Sat, Sep 3, 2016 at 4:06 PM, Karen Etheridge <p...@froods.org> wrote: > > 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.ht ml) 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/cpa n/report/efe5df0c-7095-11e6- b0d4-db1a5d222160 > > http://www.cpantesters.org/cpa n/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 -- Slaven Rezic - slaven <at> rezic <dot> de BBBike - route planner for cyclists in Berlin WWW version: http://www.bbbike.de Perl/Tk version for Unix and Windows: http://bbbike.sourceforge.net
