Cache Caffe and Torch builds in Travis for 1 week #788
Conversation
.travis.yml
Outdated
| - NUM_THREADS=4 | ||
|
|
||
| cache: | ||
| timeout: 10080 # 1 week |
There was a problem hiding this comment.
according to https://docs.travis-ci.com/user/caching/ the timeout is expressed in seconds and 10080s=2.8h. Am I not looking at the right doc?
There was a problem hiding this comment.
Haha whoops, sloppy math. Thanks!
4e90f6d to
8b45244
Compare
|
How do we handle the case where one build is started just before the timeout? And the case when the cache is empty and two jobs are started within minutes of each other? Maybe we don't want to handle these cases. Just curious. |
From reading through the documentation, the cache is checked at the start of the build and uploaded at the end of the build (makes sense). So, if the cache is empty and two jobs start within a few minutes of each other, they'll both build and both upload a new cache (probably identical caches). It's a little wasteful, but I think it'll shake out in our favor overall. I'm merging this now because I want to see how it behaves for a while. Then I can update BVLC's travis setup based on what I learn: BVLC/caffe#4207 (comment) |
|
Woohoo it's working great! Build+test times are consistently about 12 minutes now. |
Cache Caffe and Torch builds in Travis for 1 week
By removing the build time entirely, this brings the total TravisCI build+test time down from ~20 minutes to ~12 minutes when a cached build is present.