Welcome to the Monastery | |
PerlMonks |
Re: help debugging why module install is failingby syphilis (Archbishop) |
on Nov 15, 2020 at 22:50 UTC ( [id://11123673]=note: print w/replies, xml ) | Need Help?? |
Is there anything obvious I can do to debug this further other than contacting the author? The module installs fine on native Windows (Strawberry Perl 5.32.0), where each of those 3 failing tests all pass. I therefore think the problem is likely to be in the way the Cygwin system operates - so debugging it might be quite involved. Also, the warnings issued by t/42function.t don't appear on Strawberry Perl, but there are 4 tests in that script that are skipped on Strawberry Perl (due to fork() being unavailable) that would be run on Cygwin. So maybe that's where the difference is. Paul Evans is still fairly active - so definitely worth contacting. I think it's best to file a bug report that provides the full output of the test suite, just as you've provided here. You can, of course, simply force install the module, despite its failing tests - but I'm guessing you already knew that. I recommend that you consider switching to Strawberry Perl unless you need the Unix emulation. And, if you do need Unix emulation, then you could alternatively try MSYS2. You might (I don't know) find that it doesn't suffer the bugginess that you've hit with Cygwin. Cheers, Rob
In Section
Seekers of Perl Wisdom
|
|