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
Caching problems on OS X travis machines #2742
Comments
I think we should try this first, and this is done in #2743. The idea is that when the OS X machines are not running to slow they will be able to unpack the cache in under 10m and benefit from the cache during builds and testing. When they are slow (network likely) and cannot unpack the cache in under 10 minutes then the cacher will timeout (failing silently) before the entire job times out and the build will proceed, just slowly since the cache is missing. /cc @daniel-j-h to review and merge if this seems like a worthwhile approach. |
I cleared all caches yesterday before the 5.3.1 release. They were over 2 GB in size. The main problem is not the timeout or the caching per se, the main problem is there is no way to clear the cache other than going into the UI and doing it manually. |
@daniel-j-h keep in mind that the UI at https://travis-ci.org/Project-OSRM/osrm-backend/caches lists the aggregate size for all jobs. Each cache's size can be viewed using the
|
Focusing on that issue over at -> #2745 |
Currently OS X builds may fail because downloading and unpacking the cache is so slow that it hits the travis 10m limit for one operation (https://docs.travis-ci.com/user/common-build-problems/#My-builds-are-timing-out). This is a side effect of #2684
Because the travis caching is not in our control I don't see many solutions other than:
Example of a failed job: https://travis-ci.org/Project-OSRM/osrm-backend/jobs/149749254#L47
The text was updated successfully, but these errors were encountered: