Repository navigation
sccache: the client waits for the server through sccache's own setting - #82
Merged
Merged
Conversation
The server checks its storage before it answers and the client waited sccache's default ten seconds; several jobs' servers checking one WebDAV backend at once made an ERiC job fail with "the server did not start" and nothing else. The wait is sccache's server_startup_timeout_ms, so the action writes it into a configuration file and exports SCCACHE_CONF for every client in the job, unless the job brings its own; the input server-startup-timeout-ms defaults to 30 s. The client's message reaches the log when the start fails.
gronke
force-pushed
the
sccache-late-server
branch
from
September 17, 2026 08:45
8223e77 to
1371dda
Compare
gronke
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The server checks its storage before it answers and the client waited sccache's default ten seconds; several jobs' servers checking one WebDAV backend at once made an ERiC job fail with "the server did not start" and nothing else.
The wait is sccache's server_startup_timeout_ms, so the action writes it into a configuration file and exports SCCACHE_CONF for every client in the job, unless the job brings its own; the input server-startup-timeout-ms defaults to 30 s. The client's message reaches the log when the start fails.