On 27 March 2017 at 16:10, Dan Collins wrote:
> I've had a chance to make sure that this test environment isn't horribly
> broken...
Yeah, there's enough broken you sort of need a double-testing system.
Start with =0 , and then upon hitting a failure, retry with =1 ...
TL;DR:
- Testers, please set PERL_USE_UNSAFE_INC=0 to make the bugs actually show up.
- P5P: I don't know what to say, but testers aren't yet to really even
start showing the real . in @INC Bugs, please proceed with caution.
I'm getting a little afraid that not enough testers are running in
I started the process of running a cpan smoke test for this and noticed
that even CPAN::Reporter and YAML::Syck fail under PERL_USE_UNSAFE_INC=0.
I'll start uploading reports and sharing results with the list once I've
had a chance to make sure that this test environment isn't horribly
broken...
This is great! I've been wanting a Vagrant-ized smoker for a while. I'm going
to try this out on my home machine this week. Do you think this could be ported
to work with linux boxes too?
Also, I see you're using perlbrew, does it work with multiple Perls installed?
Ray's been working on a
Hello folks,
I'm please to tell you that I finally finished my POC of using Vagrant
to provision a OpenBSD 6 as a CPAN Smoker.
The project is located at:
https://github.com/glasswalk3r/cpan-openbsd-smoker
You can 'git clone' it or download only the Vagrantfile if you will.
Anyway, there is