CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linux #132396
+2 −2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
rustbot added A-testsuite 
| @bors try |
bors added a commit to rust-lang-ci/rust that referenced this pull request Oct 31, 2024
…6_64-gnu-tools-and-x86_64-rust-for-linux, r=<try> CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linux try-job: x86_64-gnu-tools try-job: x86_64-rust-for-linux
| ☀️ Try build successful - checks-actions |
| @Kobzol looks great 🥳 Imo we can merge this 👍 |
| I don't think there's any skipping in try builds here, definitely not in the RfL job, AFAIK. Anyway, it looks good, let's see what happens with CI times. @bors r+ |
bors added S-waiting-on-bors 
bors added a commit to rust-lang-ci/rust that referenced this pull request Oct 31, 2024
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#130693 (Add `minicore` test auxiliary and support `//@ add-core-stubs` directive in ui/assembly/codegen tests) - rust-lang#132316 (CI: use free runners for 3 fast windows jobs) - rust-lang#132354 (Add `lp64e` RISC-V ABI) - rust-lang#132395 (coverage: Avoid ICE when `coverage_cx` is unexpectedly unavailable) - rust-lang#132396 (CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linux) r? `@ghost` `@rustbot` modify labels: rollup
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request Oct 31, 2024
Rollup merge of rust-lang#132396 - MarcoIeni:ci-use-free-runners-for-x86_64-gnu-tools-and-x86_64-rust-for-linux, r=Kobzol CI: use free runners for x86_64-gnu-tools and x86_64-rust-for-linux try-job: x86_64-gnu-tools try-job: x86_64-rust-for-linux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Similar to #132316
I noticed that some jobs running on large runners are significantly faster than the rest of the auto build.
Here's some data based on the latest 97 auto builds:
x86_64-gnu-tools: 64 minutesx86_64-rust-for-linux: 33 minutesIn this PR I switch these jobs from large runners to free runners, to see if we can save some resources.
Imo if the try builds don't take longer than the average duration of the auto build we could merge this PR.
try-job: x86_64-gnu-tools
try-job: x86_64-rust-for-linux