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
Fix travis timeout #1384
Comments
|
Can you confirm the distro Travis runs on? And which version. Depending on the distro, different options are available to give rakudos for Travis to eat. |
It looks like we've specified it be 12.04. We can probably change it. It's specified here: |
|
Ubuntu 12.04 reached end-of-life in April 28. It's a very good idea to choose a more recent version. |
|
It looks like it's some kind of limitation of travis itself 😞 You can use trusty but it's still in beta: https://docs.travis-ci.com/user/trusty-ci-environment/ |
|
Note that if you want the most recent rakudo, then I can expose whateverable builds in some way so that it will be possible to just pull any version you want at any time. Just ping me if this is needed. |
|
@AlexDaniel sounds good to me. I guess the process would be:
|
|
There's also this rakudo docker container that is only 500megs and takes
very little to run (compared to compiling) :-)
|
|
@JJ that might be the way to go because then we can have zef in the docker image too. FYI you can reduce the size by rm -r the rakudo src directory. I have been doing some work in the same direction as you recently and managed to get a 33mb alpine-based rakudo docker image. |
|
I'll do that in the next release, with the updated rakudo. I was actually wondering what I could safely remove to reduce size. Thanks! |
To tell you the truth, I had to discover it myself... It's easier if you create a Dockerfile using this one as a base, since you can just `RUN` `zef` inside it. Not so intuitive if you want to do it by hand. Hope this closes #1, thanks to @moritz and @loltimo for the suggestion. If someone can test if this helps for Raku/doc#1384 that would be great.
|
I have already setup travis to archive rakudo, and build files so just get it to build the latest release instead of building a nightly maybe. It backs up many of the build files, though it likely could be optimized. Maybe more folders need to be added to be archived and restored on the next build. Also I have nightly appimages that build as well if anybody wants to try with that: https://github.com/samcv/rakudo-appimage-module-test-automation/tree/gh-pages The appimages are only 7 MB |
|
@samcv great work. Minor nitpick: It's not good practice to store AppImages (or any other binaries) in git repositories. There's GitHub Releases for that, check it out. |
|
@samcv So we can close this ticket. Or does it still timeout sometimes when it has to re-cache? |
|
Given that nobody is complaining, I'll close this. If there's still an issue, let's open a new ticket and link this one. |
docs build sometimes takes so long travis times out. IMO: The solution that involves the least work is to use rakudo binaries rather than building rakudo before building to docs.
The text was updated successfully, but these errors were encountered: