diff options
| author | bors <bors@rust-lang.org> | 2017-02-25 03:10:23 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-02-25 03:10:23 +0000 |
| commit | 19e5a82f8950ae15fb2a082791cb82c048e58006 (patch) | |
| tree | 1373ae8478f00f13fd52e9b8d868f72644a275d3 /src/test/run-pass/thinlto | |
| parent | 7932349e95ebd9de314e5c5fce155c33940a148b (diff) | |
| parent | 255a87499dece27cd400f387506336360a3d07fd (diff) | |
| download | rust-19e5a82f8950ae15fb2a082791cb82c048e58006.tar.gz rust-19e5a82f8950ae15fb2a082791cb82c048e58006.zip | |
Auto merge of #40084 - alexcrichton:update-sccache, r=aturon
Update sccache binaries on CI Currently CI builds can fail spuriously during the LLVM build (#39003). I believe this is due to sccache, and I believe that in turn was due to the fact that the sccache server used to just be a raw mio server. Historically raw mio servers are quite complicated to get right, but this is why we built Tokio! The sccache server has been migrated to Tokio which I suspect would fix any latent issues. I have no confirmation of this (never been able to reproduce the deadlock locally), but my hunch is that updating sccache to the master branch will fix the timeouts during the LLVM build. The binaries previously came from Gecko's infrastructure, but I've built new ones by hand for Win/Mac/Linux and uploaded them to our CI bucket.
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions