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 expand-yaml-anchors in x test tidy #107704

Merged
merged 1 commit into from
Feb 7, 2023
Merged

Conversation

jyn514
Copy link
Member

@jyn514 jyn514 commented Feb 5, 2023

Previously, the pre-commit hook which runs x test tidy could pass only to have CI fail within the first 30 seconds. This adds about 30 seconds to test tidy (for an initial run, much less after the tool is built the first time) in exchange for catching errors in .github/workflows/ci.yml before they're pushed.

Previously, the pre-commit hook which runs `x test tidy` could pass only to have CI fail within the first 30 seconds.
This adds about 30 seconds to `test tidy` (for an initial run, much less after the tool is built the first time)
in exchange for catching errors in `.github/workflows/ci.yml` before they're pushed.
@rustbot
Copy link
Collaborator

rustbot commented Feb 5, 2023

r? @Mark-Simulacrum

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

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Feb 5, 2023
@@ -1134,6 +1131,11 @@ help: to skip test's attempt to check tidiness, pass `--exclude src/tools/tidy`
}
crate::format::format(&builder, !builder.config.cmd.bless(), &[]);
}

builder.info("tidy check");
try_run(builder, &mut cmd);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change isn't strictly necessary, but I personally find that I have broken formatting way more commonly than any other issue, so it seems nice to run that check first.

@Mark-Simulacrum
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Feb 6, 2023

📌 Commit 13588cc 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 Feb 6, 2023
@bors
Copy link
Contributor

bors commented Feb 7, 2023

⌛ Testing commit 13588cc with merge e4dd9ed...

@bors
Copy link
Contributor

bors commented Feb 7, 2023

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

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Feb 7, 2023
@bors bors merged commit e4dd9ed into rust-lang:master Feb 7, 2023
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (e4dd9ed): comparison URL.

Overall result: ❌ regressions - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

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)
1.0% [0.4%, 1.5%] 3
Regressions ❌
(secondary)
3.7% [3.4%, 4.3%] 6
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 1.0% [0.4%, 1.5%] 3

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)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-4.2% [-4.2%, -4.2%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -4.2% [-4.2%, -4.2%] 1

Cycles

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)
3.6% [1.1%, 5.7%] 8
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 3.6% [1.1%, 5.7%] 8

@rustbot rustbot added the perf-regression Performance regression. label Feb 7, 2023
@jyn514 jyn514 deleted the tidy-ci branch February 7, 2023 16:08
@jyn514
Copy link
Member Author

jyn514 commented Feb 7, 2023

This has to be noise, I didn't touch anything except CI code.

@pnkfelix
Copy link
Member

pnkfelix commented Feb 7, 2023

the performance graph for cranelift check does indicate some up-and-down swings that seem to have only started recently, possibly correlated with #107627 though I don't know how that would introduce noise.

the graph for keccak check also has recent injection of up-and-down swings that also correlated with #107627. I see that @nnethercote actually asked about recent noise on zulip, so I'll ping them and see what they think root cause might be.

@rustbot label: +perf-regression-triaged

@rustbot rustbot added the perf-regression-triaged The performance regression has been triaged. label Feb 7, 2023
@ehuss ehuss added this to the 1.69.0 milestone May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. perf-regression-triaged The performance regression has been triaged. 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)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants