Skip to content

test(chore): audit //@ run-pass in ui tests#154254

Open
Embers-of-the-Fire wants to merge 1 commit into
rust-lang:mainfrom
Embers-of-the-Fire:chore/clean-test-run-pass
Open

test(chore): audit //@ run-pass in ui tests#154254
Embers-of-the-Fire wants to merge 1 commit into
rust-lang:mainfrom
Embers-of-the-Fire:chore/clean-test-run-pass

Conversation

@Embers-of-the-Fire
Copy link
Copy Markdown
Contributor

@Embers-of-the-Fire Embers-of-the-Fire commented Mar 23, 2026

Part of work for #154158.

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Mar 23, 2026
@Embers-of-the-Fire Embers-of-the-Fire changed the title text(chore): audit //@ run-pass in ui tests test(chore): audit //@ run-pass in ui tests Mar 23, 2026
@Embers-of-the-Fire Embers-of-the-Fire marked this pull request as ready for review March 23, 2026 16:23
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 23, 2026
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Mar 23, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Mar 23, 2026

r? @JonathanBrouwer

rustbot has assigned @JonathanBrouwer.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: compiler
  • compiler expanded to 69 candidates
  • Random selection from 14 candidates

@JonathanBrouwer
Copy link
Copy Markdown
Contributor

JonathanBrouwer commented Mar 23, 2026

@rustbot reroll
I'm very busy in my personal life this week and probably the next one as well so will leave review duty for a bit (just changed my triagebot config)

@rustbot rustbot assigned TaKO8Ki and unassigned JonathanBrouwer Mar 23, 2026
@TaKO8Ki
Copy link
Copy Markdown
Member

TaKO8Ki commented Mar 24, 2026

Thank you. Could you let me know when you're ready with @rustbot review and rebase all commits into a single commit at the end? @Embers-of-the-Fire

@rustbot author

@rustbot rustbot 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 Mar 24, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Mar 24, 2026

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@rust-bors

This comment has been minimized.

@rustbot

This comment has been minimized.

@rustbot rustbot added the has-merge-commits PR has merge commits, merge with caution. label May 9, 2026
@Embers-of-the-Fire Embers-of-the-Fire force-pushed the chore/clean-test-run-pass branch from d865e9d to a85f929 Compare May 9, 2026 10:22
@rustbot

This comment has been minimized.

@rustbot rustbot removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. has-merge-commits PR has merge commits, merge with caution. labels May 9, 2026
@Embers-of-the-Fire Embers-of-the-Fire force-pushed the chore/clean-test-run-pass branch from a85f929 to 296a847 Compare May 9, 2026 12:29
@rustbot

This comment has been minimized.

@Embers-of-the-Fire
Copy link
Copy Markdown
Contributor Author

@rustbot review

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label May 9, 2026
@rust-log-analyzer

This comment has been minimized.

@TaKO8Ki
Copy link
Copy Markdown
Member

TaKO8Ki commented May 11, 2026

@Embers-of-the-Fire Could you fix CI failures?

@Embers-of-the-Fire
Copy link
Copy Markdown
Contributor Author

@TaKO8Ki Most of the errors (at least those I could observe) originate from linter warnings, and I'm not sure if you want me to fix them by 1) switching back to build-pass or run-pass or 2) modify the stderr file?

@TaKO8Ki
Copy link
Copy Markdown
Member

TaKO8Ki commented May 12, 2026

@Embers-of-the-Fire These look like stale stderr expectations after the mode change. The actual output is empty, I guess. You can keep check-pass and remove/bless the stale .stderr files with --bless as an example.

@rust-bors

This comment has been minimized.

@Embers-of-the-Fire Embers-of-the-Fire force-pushed the chore/clean-test-run-pass branch from 296a847 to b23ccf3 Compare May 14, 2026 14:20
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented May 14, 2026

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@rust-log-analyzer

This comment has been minimized.

Assisted-by: OpenAI:gpt-5.5
Co-authored-by: Ayuse <ayodeleoluwasina@gmail.com>
Signed-off-by: Embers-of-the-Fire <stellarishs@163.com>
@Embers-of-the-Fire Embers-of-the-Fire force-pushed the chore/clean-test-run-pass branch from b23ccf3 to c2455c7 Compare May 14, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

F-explicit_tail_calls `#![feature(explicit_tail_calls)]` S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants