-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Rust/Cargo CI perf improvements #6119
Labels
Comments
We already throttle Lines 220 to 224 in cafd732
easy to extend to Linux if needed (but realistically, that shard runs pretty fast) |
Hitting the 1st bullet in #6208 |
jsirois
added a commit
to jsirois/pants
that referenced
this issue
Aug 6, 2018
Picks the lowest hanging fruit from pantsbuild#6119.
Merged
jsirois
added a commit
to jsirois/pants
that referenced
this issue
Aug 6, 2018
Picks the lowest hanging fruit from pantsbuild#6119.
jsirois
added a commit
that referenced
this issue
Aug 7, 2018
Picks the lowest hanging fruit from #6119.
Alright, #6309 cuts ~4 minutes per shard. I'm going to stop progress here and close. |
CMLivingston
pushed a commit
to CMLivingston/pants
that referenced
this issue
Aug 27, 2018
Picks the lowest hanging fruit from pantsbuild#6119.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A few ideas stumbled upon while trying to speed up CI burns on #6104:
The official rust language support in Travis caches
~/.cargo
andtarget/
, so this is kosher from their point of view and blessed by Chrichton. I tried this already and the upshot is all 3rdparty crate compilations are cached when they have not changed versions - easy win.cargo build
as we do for zinc in pants.travis-ci.iniThis can be done via
CARGO_BUILD_JOBS=N
in .travis.yml and might give us better throughput with less thrash. Measurements needed.cargo test
similar to above.Not sure how to best do this. There is rumor
RUST_TEST_THREADS=N
works, though it looks discouraged. I've had great luck withcargo make ...
which allows setting up arbitrary commands in aMakefile.toml
on a side project. Might be a way to go for these bottom two bullets. Likely very little bang for the buck here though, tests are still pretty fast.The text was updated successfully, but these errors were encountered: