Keep balancing "split" AppVeyor jobs #48844
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
Comments
alexcrichton
added
T-bootstrap
|
cc @rust-lang/infra |
kennytm
added
the
C-enhancement
5 tasks
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Mar 24, 2018
We've made headway towards splitting the test suite across two appveyor builders and this moves one more tests suite between builders. The last [failed build][fail] had its longest running test suite and I've moved that to the secondary builder. cc rust-lang#48844 [fail]: https://ci.appveyor.com/project/rust-lang/rust/build/1.0.6782
bors
added a commit
that referenced
this issue
Mar 26, 2018
appveyor: Move run-pass-fulldeps to extra builders We've made headway towards splitting the test suite across two appveyor builders and this moves one more tests suite between builders. The last [failed build][fail] had its longest running test suite and I've moved that to the secondary builder. cc #48844 [fail]: https://ci.appveyor.com/project/rust-lang/rust/build/1.0.6782
|
Is this still relevant? |
|
I don't think we need an issue for continuing to balance things, but we do still have some split builders (typically ending in -1, -2). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@kennytm has done some amazing analysis and it looks like our "split" appveyor jobs for 32-bit tests currently isn't very split but rather still somewhat imbalanced. We should shuffle around some more test suites to balance the load a bit more!
The text was updated successfully, but these errors were encountered: