-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Travis builds failing due to build timeouts #23
Comments
We should be able to add |
Thanks Phil - with the additions in icyrockcom@b2d0f09 the last Travis build now takes 7 mins (though without the latest word-count exercise that's pending approval) vs 21 / 23 / 24 / 34 mins. This is a nice speed up, but not as much as I hoped so. Does it make sense to cache bower_components, too? |
Yes, we can cache |
Latest build of the above icyrockcom@3226c6e finished in 3:39. While the variations are obviously great, this version promises to be perhaps 25-50% faster, so I'd go with it. If nothing else, there's less noise in the build logs. |
Any comments on this one or changes I should make? If this looks good, I can rebase on top of the current master for you to merge, let me know. |
Looks good to me, thanks :) |
Thanks @lpil, rebased. The build finished in 7:09, so quite slower than the other day, but still quite faster than current builds. For some reason, the project is being built even though it should be in the cache, e.g.:
so we are not getting the full speedup here. I could not reproduce locally, I'll have to look into it. If you have a moment, please merge into master, as current builds are failing. For example, @paf31 merged word-count the other day, but the build failed after 50 minutes. |
Can you please make a PR? |
Closed by #24 |
Travis builds are failing due to build timeouts:
https://travis-ci.org/exercism/xpurescript/builds/209606731.
The message is:
The job exceeded the maximum time limit for jobs, and has been terminated.
The above build took ~50m.
Chatted on gitter:
https://gitter.im/exercism/support?at=58c22a41872fc8ce62e00614
The recommendation is to start caching builds to shorten the build time, since
pulp
is recompiling everything every time.The text was updated successfully, but these errors were encountered: