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

Update sccache binaries on CI #40084

Merged
merged 1 commit into from Feb 25, 2017

Conversation

Projects
None yet
5 participants
@alexcrichton
Copy link
Member

alexcrichton commented Feb 24, 2017

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.

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.
@rust-highfive

This comment has been minimized.

Copy link
Collaborator

rust-highfive commented Feb 24, 2017

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@aturon

This comment has been minimized.

Copy link
Member

aturon commented Feb 24, 2017

@bors r+ p=1

@bors

This comment has been minimized.

Copy link
Contributor

bors commented Feb 24, 2017

📌 Commit 255a874 has been approved by aturon

@aturon

This comment has been minimized.

Copy link
Member

aturon commented Feb 24, 2017

@bors force

@frewsxcv

This comment has been minimized.

Copy link
Member

frewsxcv commented Feb 24, 2017

@bors p=30

@bors

This comment has been minimized.

Copy link
Contributor

bors commented Feb 24, 2017

⌛️ Testing commit 255a874 with merge 94b7683...

bors added a commit that referenced this pull request Feb 24, 2017

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.
@bors

This comment has been minimized.

Copy link
Contributor

bors commented Feb 25, 2017

💔 Test failed - status-travis

@frewsxcv

This comment has been minimized.

Copy link
Member

frewsxcv commented Feb 25, 2017

@bors retry

@frewsxcv

This comment has been minimized.

Copy link
Member

frewsxcv commented Feb 25, 2017

Actually, looks like it exceeded the maximum run time on Travis. Not sure if retrying is going to help...

@bors

This comment has been minimized.

Copy link
Contributor

bors commented Feb 25, 2017

⌛️ Testing commit 255a874 with merge 19e5a82...

bors added a commit that referenced this pull request Feb 25, 2017

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.
@bors

This comment has been minimized.

Copy link
Contributor

bors commented Feb 25, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: aturon
Pushing 19e5a82 to master...

@bors bors merged commit 255a874 into rust-lang:master Feb 25, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
homu Test successful
Details

@alexcrichton alexcrichton deleted the alexcrichton:update-sccache branch Mar 8, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.