-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Run x test tidy
sooner in mingw-check
#105714
Conversation
It takes less time to run than the other tests and is more likely to fail. `expand-yaml-anchors` is still run first to make sure the CI files are internally consistent.
(rustbot has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
This didn't exactly work as expected. |
@bors r- as discussed with Joshua |
Note that we run the script here twice, once with parallel and once without. Please check you're not looking at the second run. It should still fail fast. |
In #105058 it didn't fast-fail when I applied the same change |
amazing pointer, thank you ❤️ turns out we were running the parallel script first, which seems like the wrong thing - pushed a commit switching the order. |
@bors r+ I'm not convinced this is meaningful (i.e., the order doesn't seem like it would matter to me, especially for tidy). But 🤷 |
Run `x test tidy` sooner in mingw-check It takes less time to run than the other tests and is more likely to fail. `expand-yaml-anchors` is still run first to make sure the CI files are internally consistent. Note that changing to `--stage 0` doesn't actually do anything since bootstrap tools are always built with the bootstrap compiler, this just makes it less confusing. cc rust-lang@83bab41
Run `x test tidy` sooner in mingw-check It takes less time to run than the other tests and is more likely to fail. `expand-yaml-anchors` is still run first to make sure the CI files are internally consistent. Note that changing to `--stage 0` doesn't actually do anything since bootstrap tools are always built with the bootstrap compiler, this just makes it less confusing. cc rust-lang@83bab41
got a weird |
Oh, that's probably from reordering the parallel compiler build. I'll look into it. @bors r- |
This takes a long time and rarely fails. It also interferes with `retry make prepare`, the retry is unhelpful since `make prepare` turns into a no-op
@bors r=Mark-Simulacrum |
⌛ Testing commit b8a84c2 with merge b64fc3f69ca2c43d72984847cb383da0fb0a7892... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (37efc81): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
…dead Cleanup `mingw-tidy` docker job Fixes a couple small regressions from rust-lang#106048 and rust-lang#105714. - Avoid `/checkout/src/ci/run.sh: line 187: [: =: unary operator expected`: https://github.com/rust-lang/rust/actions/runs/3809902408/jobs/6481611301#step:26:1701 - Avoid running `x check` in the tidy test, to get faster feedback. It's already run on the normal `mingw-check` job. r? `@fee1-dead`
…dead Cleanup `mingw-tidy` docker job Fixes a couple small regressions from rust-lang#106048 and rust-lang#105714. - Avoid `/checkout/src/ci/run.sh: line 187: [: =: unary operator expected`: https://github.com/rust-lang/rust/actions/runs/3809902408/jobs/6481611301#step:26:1701 - Avoid running `x check` in the tidy test, to get faster feedback. It's already run on the normal `mingw-check` job. r? `@fee1-dead`
Run `x test tidy` sooner in mingw-check It takes less time to run than the other tests and is more likely to fail. `expand-yaml-anchors` is still run first to make sure the CI files are internally consistent. Note that changing to `--stage 0` doesn't actually do anything since bootstrap tools are always built with the bootstrap compiler, this just makes it less confusing. cc rust-lang@83bab41
It takes less time to run than the other tests and is more likely to fail.
expand-yaml-anchors
is still run first to make sure the CI files are internally consistent.Note that changing to
--stage 0
doesn't actually do anything since bootstrap tools are always built with the bootstrap compiler, this just makes it less confusing.cc 83bab41