New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perl v5.20 Critical Failure #5226

Closed
wbraswell opened this Issue Dec 6, 2015 · 3 comments

Comments

Projects
None yet
4 participants
@wbraswell

wbraswell commented Dec 6, 2015

My builds started failing today on Perl v5.20 only:

https://travis-ci.org/wbraswell/rperl/jobs/95123818#L124

The following error message should never appear, there should never be a problem looking for 'strict.pm', it is built into the Perl core itself. This is a serious configuration problem with Perl or the Travis-CI virtual machine itself.

Can't locate strict.pm in @INC

You can see all the other versions of Perl (even the new v5.22) are working fine:

https://travis-ci.org/wbraswell/rperl/builds/95123812

@eserte

This comment has been minimized.

Show comment
Hide comment
@eserte

eserte Dec 6, 2015

Me too: https://travis-ci.org/eserte/bbbike/jobs/95150409#L124

As a workaround, you can switch to "5.20-shrplib", which also provides Perl v5.20.

eserte commented Dec 6, 2015

Me too: https://travis-ci.org/eserte/bbbike/jobs/95150409#L124

As a workaround, you can switch to "5.20-shrplib", which also provides Perl v5.20.

@meatballhat meatballhat changed the title from Perl v5.20 Critical Failure [precise-gce] to Perl v5.20 Critical Failure Dec 8, 2015

@BanzaiMan

This comment has been minimized.

Show comment
Hide comment
@BanzaiMan

BanzaiMan Dec 9, 2015

Member

This is a packaging issue on our side. When I created the 5.20.3 archive a while back, it did not set up the alias correctly, so that 5.20 was not recognized correctly. Specifying 5.20.3 should work right now. I am repackaging 5.20 to fix this, but the problem would persist until new image is provisioned and deployed.

Member

BanzaiMan commented Dec 9, 2015

This is a packaging issue on our side. When I created the 5.20.3 archive a while back, it did not set up the alias correctly, so that 5.20 was not recognized correctly. Specifying 5.20.3 should work right now. I am repackaging 5.20 to fix this, but the problem would persist until new image is provisioned and deployed.

@wbraswell

This comment has been minimized.

Show comment
Hide comment
@wbraswell

wbraswell Dec 10, 2015

@BanzaiMan
Seems to be working for me now, thanks!
👍

wbraswell commented Dec 10, 2015

@BanzaiMan
Seems to be working for me now, thanks!
👍

@wbraswell wbraswell closed this Dec 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment