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
Don’t install rust-docs, rust-src, or clippy on CI #24511
Conversation
@bors-servo try |
Don’t install rust-docs, rust-src, or clippy on CI See https://blog.rust-lang.org/2019/10/15/Rustup-1.20.0.html#profiles
Alright, managed to observe the desired behavior on Windows, macOS, and Linux. This PR should be good now. In my first attempt nothing happened on macOS because the worker already had that version of Rust Nightly installed, so I wanted to have a look at what’s on each server:
I expected each worker to have my key configured through salt. @jdm, are workers to 3 to 7 configured differently? |
Looks like those workers had never been salted since the ssh key changes. I've deployed to all of them now. |
Does this have any impact on our code that tries to merge the standard library docs with our project docs? |
Oh that’s a good point. That task likely needs |
https://tools.taskcluster.net/groups/fRGfWK7SQze62WwLbxe1PA/tasks/T6SB8V5eS3u0ZwfpH08wZw/runs/0/logs/public%2Flogs%2Flive.log#L2530 ran without error, I wonder if it copied an empty directory. |
Ah, foiled again by
My key hasn’t changed in a couple years, though? Trying again now, I can access all macOS workers except # 2 and 9. |
There is no worker 9. I missed 2; I have now deployed the keys to that worker. |
Our Macstadium account shows 9 machines, and This PR is ready for review. |
@bors-servo r+ |
📌 Commit 6913ad0 has been approved by |
Don’t install rust-docs, rust-src, or clippy on CI See https://blog.rust-lang.org/2019/10/15/Rustup-1.20.0.html#profiles
☀️ Test successful - linux-rel-css, linux-rel-wpt, status-taskcluster |
See https://blog.rust-lang.org/2019/10/15/Rustup-1.20.0.html#profiles