I'm still trying to test and eliminate the possibilities.
I discarded my previous OpenBSD VM and took an older one to validate if I could
install Moose on it. All tests passed, you will get the report because I
submitted it.
Today I created a new VM from scratch on OpenBSD 5.9. My first attempted with
default perl and local::lib failed all the tests with a generated core dump.
I'm still to tests with a custom perl installed through perlbrew (it fails a
hash test during the test phase, but I think it's harmless, see my post on
OpenBSD for details). I also submitted this test.
What was different from my brand new VM and the older one (where the tests
succeeded)? Well, I didn't upgrade all the modules installed using "cpan -u"
before trying to install a new version of Moose.
I'll let you know if I find something new.
De: Karen Etheridge <p...@froods.org>
Para: Alceu R. de Freitas Jr. <glasswal...@yahoo.com.br>
Cc: Alceu R. de Freitas Jr. via cpan-testers-discuss
<cpan-testers-discuss@perl.org>
Enviadas: Terça-feira, 6 de Setembro de 2016 16:31
Assunto: Re: Your smoke testing reports
I don't know if this is helpful, but I've been seeing widespread issues with
FreeBSD and NetBSD as well lately. I've been receiving a lot of FAIL reports
containing segmentation faults from FreeBSD and NetBSD that look similar to the
OpenBSD issues, for example:
FreeBSD (BinGOs):
http://www.cpantesters.org/cpan/report/eef9bd38-6704-11e6-ab41-c893a58a4b8c
http://www.cpantesters.org/cpan/report/8665c62c-73c0-11e6-8807-814d1da4c10f
NetBSD (Nigel Horne):
http://www.cpantesters.org/cpan/report/8d46746e-73b1-11e6-b850-10220ec14a5e
http://www.cpantesters.org/cpan/report/42d3ed70-73ad-11e6-b850-10220ec14a5e
http://www.cpantesters.org/cpan/report/ae162bf6-73ae-11e6-b850-10220ec14a5e
http://www.cpantesters.org/cpan/report/3ec4326c-73ad-11e6-b850-10220ec14a5e
http://www.cpantesters.org/cpan/report/98868544-73b1-11e6-b850-10220ec14a5e
http://www.cpantesters.org/cpan/report/a34aa63c-73b0-11e6-b850-10220ec14a5e
On Sun, Sep 4, 2016 at 8:31 AM, Alceu R. de Freitas Jr. via
cpan-testers-discuss <cpan-testers-discuss@perl.org> wrote:
Hello Slaven,
It is a possibility that the default perl on OpenBSD is causing the issues.
I won't say that is heavily patched, but there is obviously differences from
standard interpreter. In initial attempts with OpenBSD (5.8) I found that that
I was unable to compile any perl with perlbrew since all of them failed the
tests. In this thread here: installation of Perl on OpenBSD 5.8 with perlbrew
fails due crypt.h there are more details about that.
| |
| | | | | | | |
| installation of Perl on OpenBSD 5.8 with perlbrew fails ...Hi there,My name
is Alceu and I'm a newbie with OpenBSD. I hope I reached the right mailing list
to ask about compiling Perl with perlbrew on OpenBSD. Advertisin... |
| |
| Visualizar em www.mail-archiv... | Visualizado por Yahoo |
| |
| |
Of course I can try to compile the interpreter without perlbrew, but that leads
to the questions: are we looking for to validate CPAN modules against the
interpreter shipped with OpenBSD or the standard perl?
De: Slaven Rezic <sla...@rezic.de>
Para: Alceu R. de Freitas Jr. via cpan-testers-discuss
<cpan-testers-discuss@perl.org >
Cc: Karen Etheridge <p...@froods.org>; Alceu R. de Freitas Jr.
<glasswal...@yahoo.com.br>
Enviadas: Domingo, 4 de Setembro de 2016 12:11
Assunto: Re: Your smoke testing reports
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
