Hello Dan,
This information is on the report I sent below (Karen post). The backtrace
looks like the same I got from trying to test Moose.
De: Dan Collins <dcolli...@gmail.com>
Para: CPAN Testers Discuss <cpan-testers-discuss@perl.org>
Enviadas: Sexta-feira, 9 de Setembro de 2016 1:27
Assunto: Re: Your smoke testing reports
Have you considered using Valgrind or GDB to locate the source of the SEGV? Is
it always the same line of code? Does Sub::Name's test suite always fail after
the exact same test, or is it intermittent/variable?
On Thu, Sep 8, 2016 at 10:59 PM, Karen Etheridge <p...@froods.org> wrote:
Here is that Sub-Name report: http://www.cpantesters.org/
cpan/report/3a995cce-760c- 11e6-a32c-cd9de3776ab1
On Thu, Sep 8, 2016 at 2:48 PM, Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss <cpan-testers-discuss@perl.org > wrote:
I checked all those reports and despite the "BSD" part, I don't see much that
can be related that they have in common. There are different configurations of
perl (some with ithreads, others without it) and SO versions. Also, all have in
common this failure (but not always for the same tests):
Non-zero wait status: 139
Parse errors: No plan found in TAP output
One thing that is not easy to detected is if those system are running under
virtualization or not (maybe we could add this to reports as static
information?). My newest OpenBSD was a VM running on Virtualbox 5 and the host
Microsoft Windows 7.
My older VM was also running on Virtualbox, but under Linux and version 4.3.36.
You can check the PASS report here: http://www.cpantesters.org/cpa
n/report/20aa9630-7430-11e6-a7 54-2713ddf53d17
I'm don't know about the other BSD OSes, but OpenBSD hasn't a good reputation
on VMs, but I never was able to confirm an issue with Virtualbox.
After my first success on installing Moose, I took a chance to upgrade all
installed modules. After that, I manually checked the reports and see that
there was a failure with Sub::Name. Since Moose was already at the latest
version, nothing was executed related to it.
I tried to manually install Sub::Name from the CPAN shell. It failed due a core
dump. Since I was saving the reports on disk, I manually included information
to the report and submit it. I'm not sure if this will work, but let me know if
doesn't, I have a copy and can send it by e-mail in private (or to the group if
it accepts text attachments).
The interesting part is that I did "look Sub::Name" after the failure, execute
"make clean" and repeat all the process for test it again... and it passed all
tests and got installed.
Went back again to install Moose... I couldn't even pass the Makefile.PL step.
It fails and generates a large core dump on the VM.
So, my guess is that we have something wrong with Sub::Name.
Em 06-09-2016 16:31, Karen Etheridge escreveu:
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/cpa n/report/eef9bd38-6704-11e6-ab 41-c893a58a4b8c
http://www.cpantesters.org/cpa n/report/8665c62c-73c0-11e6-88 07-814d1da4c10f
NetBSD (Nigel Horne):
http://www.cpantesters.org/cpa n/report/8d46746e-73b1-11e6-b8 50-10220ec14a5e
http://www.cpantesters.org/cpa n/report/42d3ed70-73ad-11e6-b8 50-10220ec14a5e
http://www.cpantesters.org/cpa n/report/ae162bf6-73ae-11e6-b8 50-10220ec14a5e
http://www.cpantesters.org/cpa n/report/3ec4326c-73ad-11e6-b8 50-10220ec14a5e
http://www.cpantesters.org/cpa n/report/98868544-73b1-11e6-b8 50-10220ec14a5e
http://www.cpantesters.org/cpa n/report/a34aa63c-73b0-11e6-b8 50-10220ec14a5e
