Skip to content

Commit

Permalink
Keep sccache alive for 10 hours, not 3
Browse files Browse the repository at this point in the history
We're currently praying that sccache dying after 3 hrs somehow causes
the "exited with 259" errors on appveyor, but this is a complete shot in
the dark. In any case it should be harmless to keep sccache alive!

cc rust-lang#58160
  • Loading branch information
alexcrichton committed Mar 5, 2019
1 parent f22dca0 commit dec319a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/ci/run.sh
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ fi
# server (#48192) which causes Cargo to erroneously think that a build script
# hasn't finished yet. Try to solve that problem by starting a very long-lived
# sccache server at the start of the build, but no need to worry if this fails.
SCCACHE_IDLE_TIMEOUT=10800 sccache --start-server || true
SCCACHE_IDLE_TIMEOUT=36000 sccache --start-server || true

if [ "$RUN_CHECK_WITH_PARALLEL_QUERIES" != "" ]; then
$SRC/configure --enable-parallel-compiler
Expand Down

0 comments on commit dec319a

Please sign in to comment.