Skip to content
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

Intermittent "Connection to server timed out" while building gecko-media (sccache) #19495

Closed
jdm opened this issue Dec 5, 2017 · 4 comments
Closed

Comments

@jdm
Copy link
Member

@jdm jdm commented Dec 5, 2017

Example log: https://gist.github.com/jdm/14b33c3f609730891733d1a41e3f0af2

In particular:

running: "cmake" "--build" "." "--target" "install" "--config" "Release" "--"
Scanning dependencies of target ogg
[  0%] Building C object CMakeFiles/ogg.dir/gecko/src/media/libogg/src/ogg_alloc.c.o

--- stderr
error: Connection to server timed out
make[2]: *** [CMakeFiles/ogg.dir/gecko/src/media/libogg/src/ogg_alloc.c.o] Error 2
make[1]: *** [CMakeFiles/ogg.dir/all] Error 2
make: *** [all] Error 2
thread 'main' panicked at '
command did not execute successfully, got: exit code: 2

My guess is this is related to the jobserver integration. cc @aturon, since this is significantly affecting Servo's CI throughput.

@jdm
Copy link
Member Author

@jdm jdm commented Dec 5, 2017

jdm added a commit to servo/saltfs that referenced this issue Dec 14, 2017
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.
@mbrubeck mbrubeck mentioned this issue Dec 15, 2017
3 of 3 tasks complete
bors-servo added a commit to servo/saltfs that referenced this issue Dec 20, 2017
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
Copy link
Member Author

@jdm jdm commented Dec 21, 2017

This appears to still be happening.

@jdm jdm reopened this Dec 21, 2017
@jdm jdm changed the title Intermittent "Connection to server timed out" while building cmake-based crates Intermittent "Connection to server timed out" while building gecko-media Dec 21, 2017
@jdm jdm changed the title Intermittent "Connection to server timed out" while building gecko-media Intermittent "Connection to server timed out" while building gecko-media (sccache) Jan 4, 2018
@jdm
Copy link
Member Author

@jdm jdm commented Jan 4, 2018

Our builders have sccache 0.1.1-pre installed, but support for SCCACHE_IDLE_TIMEOUT was not introduced until 0.2.1-pre. This explains why we're still seeing the problem on our build machines. This makes servo/saltfs#755 much more urgent.

bors-servo added a commit to servo/saltfs that referenced this issue Jan 9, 2018
Upgrade sccache

This puts the binaries in a s3 bucket that we control and upgrades to the latest version. This should finally 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/774)
<!-- Reviewable:end -->
@jdm jdm mentioned this issue Jan 9, 2018
1 of 5 tasks complete
@jdm jdm reopened this Jan 9, 2018
@jdm
Copy link
Member Author

@jdm jdm commented Jan 10, 2018

This should now be fixed, since servo/saltfs#774 has been deployed.

@jdm jdm closed this Jan 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant
You can’t perform that action at this time.