-
Notifications
You must be signed in to change notification settings - Fork 167
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
Split rust CI into more jobs #2786
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ea251d7
to
8eb09ba
Compare
3ffafd9
to
1f6268a
Compare
ee6d349
to
59cb85b
Compare
1f6268a
to
63f038c
Compare
59cb85b
to
bf5ab5c
Compare
63f038c
to
f0f704d
Compare
bf5ab5c
to
631364e
Compare
f0f704d
to
0f57c58
Compare
631364e
to
83c1944
Compare
0f57c58
to
4824098
Compare
83c1944
to
facd157
Compare
4824098
to
c68473d
Compare
facd157
to
99b8f1f
Compare
c68473d
to
3e17207
Compare
99b8f1f
to
e1af55b
Compare
3e17207
to
b3f5cf8
Compare
d30332c
to
8ed386a
Compare
b3f5cf8
to
2010c9e
Compare
8ed386a
to
0a8ccc4
Compare
2010c9e
to
f9fa551
Compare
6ff1a0f
to
47e4443
Compare
f9fa551
to
d4706f4
Compare
f862c21
to
dfa4908
Compare
d4706f4
to
83d1692
Compare
dfa4908
to
5450a3b
Compare
.github/workflows/rust.yml
Outdated
sudo rm -rf /usr/share/dotnet | ||
sudo rm -rf /opt/ghc | ||
sudo rm -rf "/usr/local/share/boost" | ||
sudo rm -rf "$AGENT_TOOLSDIRECTORY" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This runs in parallel to the remote-net-tests
and also has the "Clear up some space"
step. Are you sure these parallel jobs, trying to access the same directories, won't conflict with each other? Do they run on separate machines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They all run in their own isolated VMs: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#overview-of-github-hosted-runners
I also think these steps might be unnecessary now 🤔 Let me try removing them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great.
Now, we just need to move a couple of "lint jobs" to `github merge queue" and we cut down the CI running time by another 5 minutes and save on CI costs.
83d1692
to
792bc4c
Compare
5450a3b
to
f288c9f
Compare
792bc4c
to
a5479f7
Compare
f288c9f
to
f1966ea
Compare
f1966ea
to
b34213b
Compare
## Motivation CI takes a long time ## Proposal Split into more jobs, which will make us do roughly the same amount of work, but more parallelized. So hopefully this reduces CI time without increasing github costs much. ## Test Plan CI With this and the PR before this one (#2785), we went from having the `test` job sometimes take up to an hour, to now, running many jobs in parallel, the test that takes the longest is `check-all-features`, which takes around 30 minutes. ## Release Plan - Nothing to do / These changes follow the usual release cycle.
Motivation
CI takes a long time
Proposal
Split into more jobs, which will make us do roughly the same amount of work, but more parallelized. So hopefully this reduces CI time without increasing github costs much.
Test Plan
CI
With this and the PR before this one (#2785), we went from having the
test
job sometimes take up to an hour, to now, running many jobs in parallel, the test that takes the longest ischeck-all-features
, which takes around 30 minutes.Release Plan