Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake sccache never time out #763
Conversation
|
Are there docs for this somewhere? Please add a link to the commit message and also maybe a description of the problem (where is sccache timing out currently?) and/or link to a Buildbot log in this PR. |
Per https://github.com/mozilla/sccache/blob/a310f6a62eb34281bda083f88dc96c736a3eeb74/src/server.rs#L69-L76 this variable controls how long the server waits before shutting down. For long compiles that exceed this timeout, this can cause compilation to fail like servo/servo#19495. https://github.com/mozilla/sccache/blob/629813f2d2f0b3ac8102696df69d57200688d320/docs/Jenkins.md#L11 describes the effect of making this timeout zero for CI infrastructure - the server process becomes long-lived and never shuts down.
|
Commit message updated. |
|
Thanks for the links. Two questions I have:
|
|
The first time a build is run with a timeout of 0, it will automatically start the long-lived server in the background. As part of upgrading, we should run |
|
I'm going to go ahead and merge this change because servo/servo#19495 is really frustrating and I want to have enough time to be able to look into anything that might go wrong. @bors-servo: r+ |
|
|
Make sccache never time out This should fix servo/servo#19495. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/763) <!-- Reviewable:end -->
|
|
jdm commentedDec 14, 2017
•
edited by larsbergstrom
This should fix servo/servo#19495.
This change is