Skip to content

Conversation

jieyouxu
Copy link
Member

@jieyouxu jieyouxu commented Oct 2, 2025

Current auto compiler stable-regression backport nominations seem to be too aggressive, and seems to unfortunately lower signal-to-noise ratio of the compiler backport channel. So this PR disables the triagebot compiler auto stable-regression backport nominations pending a redesign. Beta-regression auto backport nominations are not modified, we might want to gather some more experience with it.

No prejudice against re-enabling them if the nominations include a bit more context on why it's automatically nominated and which regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate comment.

cf. #t-compiler/backports > #146919: stable-nominated @ 💬

I like the idea of rustbot just posting a message that suggests adding the label. That seems like a good compromise between avoiding forgotten nominations and avoiding spurious nominations.

In any case, this was very much worth experimenting!

r? @apiraino (or triagebot)

@rustbot
Copy link
Collaborator

rustbot commented Oct 2, 2025

triagebot.toml has been modified, there may have been changes to the review queue.

cc @davidtwco, @wesleywiser

@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 2, 2025
Copy link
Contributor

@apiraino apiraino left a comment

Choose a reason for hiding this comment

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

I'm ok with disabling both stable and beta auto-nominations but I understood from that thread that stable auto-nominations were too eager

View changes since this review

No prejudice against re-enabling them if the nominations include a bit
more context on _why_ it's automatically nominated and _which_
regression(s) are being addressed. Or as proposed, it could also simply
become a reminder-to-nominate _comment_.
@jieyouxu jieyouxu force-pushed the disable-auto-backport-nominations branch from f7f9846 to 16cfde9 Compare October 2, 2025 09:22
@jieyouxu jieyouxu changed the title Disable triagebot auto compiler backport nominations pending redesign Disable triagebot auto stable-regression compiler backport nominations pending redesign Oct 2, 2025
@jieyouxu
Copy link
Member Author

jieyouxu commented Oct 2, 2025

Modified to only disable the stable auto backport nominations, since stable backports have a substantially higher bar, which makes those very prone to false positives.

@jieyouxu
Copy link
Member Author

jieyouxu commented Oct 2, 2025

(Also this is r-l/r so you'll need to bors 😁)

@Urgau
Copy link
Member

Urgau commented Oct 2, 2025

@bors r=apiraino,Urgau

@bors
Copy link
Collaborator

bors commented Oct 2, 2025

📌 Commit 16cfde9 has been approved by apiraino,Urgau

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 Oct 2, 2025
@Urgau
Copy link
Member

Urgau commented Oct 2, 2025

@bors rollup

bors added a commit that referenced this pull request Oct 3, 2025
Rollup of 6 pull requests

Successful merges:

 - #141839 (make rust-analyzer use a dedicated build directory)
 - #146166 (Implement range support in `//@ edition`)
 - #147259 (cg_llvm: Use helper methods for all calls to `LLVMMDNodeInContext2`)
 - #147263 (Disable triagebot auto stable-regression compiler backport nominations pending redesign)
 - #147268 (add arm-maintainers to various targets)
 - #147270 (Move doc_cfg-specific code into `cfg.rs`)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 179d182 into rust-lang:master Oct 3, 2025
10 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 3, 2025
rust-timer added a commit that referenced this pull request Oct 3, 2025
Rollup merge of #147263 - jieyouxu:disable-auto-backport-nominations, r=apiraino,Urgau

Disable triagebot auto stable-regression compiler backport nominations pending redesign

Current auto compiler stable-regression backport nominations seem to be too aggressive, and seems to unfortunately lower signal-to-noise ratio of the compiler backport channel. So this PR disables the triagebot compiler auto stable-regression backport nominations pending a redesign. Beta-regression auto backport nominations are not modified, we might want to gather some more experience with it.

No prejudice against re-enabling them if the nominations include a bit more context on _why_ it's automatically nominated and _which_ regression(s) are being addressed. Or as proposed, it could also simply become a reminder-to-nominate _comment_.

cf. [#t-compiler/backports > #146919: stable-nominated @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/474880-t-compiler.2Fbackports/topic/.23146919.3A.20stable-nominated/near/540979327)

> I like the idea of rustbot just posting a message that suggests adding the label. That seems like a good compromise between avoiding forgotten nominations and avoiding spurious nominations.

In any case, this was very much worth experimenting!

r? `@apiraino` (or triagebot)
@jieyouxu jieyouxu deleted the disable-auto-backport-nominations branch October 3, 2025 04:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: Issues & PRs about the rust-lang/rust repository itself S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants