Skip to content

Tidy: show todo reason when lint fails (and fix the lint's tidy allow statement which was weird and broken...) - #161736

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
jdonszelmann:show-todo-reason
Aug 26, 2026
Merged

Tidy: show todo reason when lint fails (and fix the lint's tidy allow statement which was weird and broken...)#161736
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
jdonszelmann:show-todo-reason

Conversation

@jdonszelmann

Copy link
Copy Markdown
Contributor

r? @WaffleLapkin

Note

I've not used an LLM for any part of this PR, or any other PR I make. This includes any related work like research.

@rustbot rustbot added A-tidy Area: The tidy tool 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 Aug 25, 2026
@rustbot

rustbot commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

WaffleLapkin is currently at their maximum review capacity.
They may take a while to respond.

Comment thread src/tools/tidy/Readme.md
fn z() {}
// tidy-alphabetical-end
```
<!--ignore-tidy-todo-->While not exactly a tidy directive, // TODO will fail tidy and make sure you can't merge a PR with unfinished work.

@jdonszelmann jdonszelmann Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

the tidy TODO lint previously implemented ignoring themselves, rather stupidly. And it worked different than all other tidy ignores, and had to be on the same line, instead of a previous line. With this lint using the standard ignore system now, the ignore comment needs to go the the previous line.

View changes since the review

@rust-log-analyzer

This comment has been minimized.

@jdonszelmann jdonszelmann changed the title Tidy: show todo reason when lint fails (and fix the lint tidy allow clause...) Tidy: show todo reason when lint fails (and fix the lint's tidy allow statement which was weird and broken...) Aug 25, 2026

@WaffleLapkin WaffleLapkin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

r=me with nits (I don't think having TODO: <no message> is useful, just omit this part if there is no message)

View changes since this review

Comment thread src/tools/tidy/src/style.rs
Comment thread src/tools/tidy/src/style.rs Outdated
@WaffleLapkin WaffleLapkin 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-review Status: Awaiting review from the assignee but also interested parties. labels Aug 26, 2026
@jdonszelmann

Copy link
Copy Markdown
Contributor Author

@bors r=wafflelapkin

@rust-bors

rust-bors Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 5d9f9e7 has been approved by wafflelapkin

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 Aug 26, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Aug 26, 2026
…afflelapkin

Tidy: show todo reason when lint fails (and fix the lint's tidy allow statement which was weird and broken...)

r? @WaffleLapkin

> [!NOTE]
> I've not used an LLM for any part of this PR, or any other PR I make. This includes any related work like research.
rust-bors Bot pushed a commit that referenced this pull request Aug 26, 2026
…uwer

Rollup of 4 pull requests

Successful merges:

 - #160651 (mir: validate `Move` call arguments are locals or box derefs)
 - #161736 (Tidy: show todo reason when lint fails (and fix the lint's tidy allow statement which was weird and broken...))
 - #161052 (Add regression test for generic inference)
 - #161818 (Fix long type on diagnostics for conditionally implemented traits)
@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 26, 2026
@rust-bors

rust-bors Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: wafflelapkin
Duration: 2h 53m 41s
Pushing bff8e12 to main...

@rust-bors
rust-bors Bot merged commit bff8e12 into rust-lang:main Aug 26, 2026
14 checks passed
@rustbot rustbot added this to the 1.100.0 milestone Aug 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 3b8ee6c (parent) -> bff8e12 (this PR)

Test differences

Show 3 test diffs

3 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard bff8e12ff5e6bcd53dfb1dbccdcec80a60a856ed --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-gnu-llvm-22-1: 49m 24s -> 1h 14m (+50.4%)
  2. x86_64-rust-for-linux: 38m 5s -> 53m 44s (+41.1%)
  3. x86_64-gnu-gcc-core-tests: 7m 57s -> 10m 47s (+35.6%)
  4. x86_64-gnu-nopt: 1h 51m -> 2h 30m (+35.1%)
  5. dist-arm-linux-gnueabi: 1h 31m -> 59m 41s (-35.1%)
  6. x86_64-gnu-llvm-21-1: 57m 45s -> 38m 9s (-33.9%)
  7. dist-i686-msvc: 2h 8m -> 1h 25m (-33.5%)
  8. arm-android: 1h 15m -> 1h 39m (+32.8%)
  9. test-various: 1h 33m -> 2h 4m (+32.3%)
  10. x86_64-gnu-stable: 1h 54m -> 2h 30m (+31.7%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (bff8e12): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.3% [0.2%, 0.4%] 8
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 9.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Cycles

Results (secondary -2.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

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

Binary size

Results (primary -0.0%, secondary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.0% [-0.0%, -0.0%] 4
Improvements ✅
(secondary)
-0.0% [-0.0%, -0.0%] 4
All ❌✅ (primary) -0.0% [-0.0%, -0.0%] 4

Bootstrap: 473.778s -> 474.868s (0.23%)
Artifact size: 402.59 MiB -> 402.61 MiB (0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-tidy Area: The tidy tool merged-by-bors This PR was explicitly merged by bors. 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.

5 participants