Skip to content
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

Merged
merged 2 commits into from
Dec 18, 2022
Merged

Run x test tidy sooner in mingw-check #105714

merged 2 commits into from
Dec 18, 2022

Conversation

jyn514
Copy link
Member

@jyn514 jyn514 commented Dec 14, 2022

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

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
Copy link
Collaborator

rustbot commented Dec 14, 2022

r? @pietroalbini

(rustbot has picked a reviewer for you, use r? to override)

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Dec 14, 2022
@Mark-Simulacrum
Copy link
Member

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Dec 14, 2022

📌 Commit c99f1b7 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 14, 2022
@Noratrieb
Copy link
Member

This didn't exactly work as expected.
Tidy only started here, with an entire x check still running before.
https://github.com/rust-lang/rust/actions/runs/3697810827/jobs/6263246796#step:26:2872

@Noratrieb
Copy link
Member

@bors r- as discussed with Joshua

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Dec 14, 2022
@Mark-Simulacrum
Copy link
Member

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.

@Noratrieb
Copy link
Member

In #105058 it didn't fast-fail when I applied the same change

@jyn514
Copy link
Member Author

jyn514 commented Dec 14, 2022

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.

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.

@Mark-Simulacrum
Copy link
Member

@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 🤷

@bors
Copy link
Contributor

bors commented Dec 14, 2022

📌 Commit fc6d59d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Dec 14, 2022
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Dec 14, 2022
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
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Dec 14, 2022
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
@matthiaskrgr
Copy link
Member

got a weird cp: cannot stat 'obj/build/metrics.json': No such file or directory in ci for mingw-check, no idea if thats spurious or not
@bors rollup=iffy

@jyn514
Copy link
Member Author

jyn514 commented Dec 15, 2022

Oh, that's probably from reordering the parallel compiler build. I'll look into it.

@bors r-

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Dec 15, 2022
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
@rustbot rustbot added the T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) label Dec 17, 2022
@jyn514
Copy link
Member Author

jyn514 commented Dec 17, 2022

@bors r=Mark-Simulacrum

@bors
Copy link
Contributor

bors commented Dec 17, 2022

📌 Commit b8a84c2 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Dec 17, 2022
@bors
Copy link
Contributor

bors commented Dec 18, 2022

⌛ Testing commit b8a84c2 with merge b64fc3f69ca2c43d72984847cb383da0fb0a7892...

@bors
Copy link
Contributor

bors commented Dec 18, 2022

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Dec 18, 2022
@rust-log-analyzer
Copy link
Collaborator

The job x86_64-gnu-tools failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
.......... (90/93)
...        (93/93)


/checkout/src/test/rustdoc-gui/scrape-examples-button-focus.goml scrape-examples-button-focus... FAILED
[ERROR] (line 12) Error: Evaluation failed: The following errors happened (for selector `.scraped-example-list > .scraped-example pre`): [Expected `248` for property `scrollTop`, found `249`]: for command `assert-property: (".scraped-example-list > .scraped-example pre", {
 "scrollTop": |initialScrollTop|

Build completed unsuccessfully in 0:02:32

@jyn514
Copy link
Member Author

jyn514 commented Dec 18, 2022

@bors retry

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Dec 18, 2022
@bors
Copy link
Contributor

bors commented Dec 18, 2022

⌛ Testing commit b8a84c2 with merge 37efc81...

@bors
Copy link
Contributor

bors commented Dec 18, 2022

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 37efc81 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Dec 18, 2022
@bors bors merged commit 37efc81 into rust-lang:master Dec 18, 2022
@rustbot rustbot added this to the 1.68.0 milestone Dec 18, 2022
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (37efc81): comparison URL.

Overall result: ❌✅ regressions and improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
1.1% [1.1%, 1.1%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.4% [-1.4%, -1.4%] 1
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results

This 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.

mean range count
Regressions ❌
(primary)
1.1% [0.9%, 1.3%] 2
Regressions ❌
(secondary)
1.2% [1.0%, 1.3%] 2
Improvements ✅
(primary)
-1.8% [-2.1%, -1.4%] 2
Improvements ✅
(secondary)
-1.6% [-2.2%, -1.4%] 3
All ❌✅ (primary) -0.3% [-2.1%, 1.3%] 4

Cycles

This benchmark run did not return any relevant results for this metric.

@jyn514 jyn514 deleted the tidy-first branch December 18, 2022 20:11
Noratrieb added a commit to Noratrieb/rust that referenced this pull request Dec 31, 2022
…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`
compiler-errors added a commit to compiler-errors/rust that referenced this pull request Jan 2, 2023
…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`
Aaron1011 pushed a commit to Aaron1011/rust that referenced this pull request Jan 6, 2023
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants