Commit Graph

711 Commits

Author SHA1 Message Date
Jonathan Brouwer 730b6766c6 Rollup merge of #155769 - Enselic:ping-enselic, r=Urgau
triagebot.toml: Ping Enselic when tests/debuginfo/basic-stepping.rs changes

The test `tests/debuginfo/basic-stepping.rs` has a history of [regressing for subtle reasons](https://github.com/rust-lang/rust/issues/33013#issuecomment-3121579216) ([retroactively](https://github.com/rust-lang/rust/pull/144497)), and has [expected behavior](https://github.com/rust-lang/rust/pull/153941) that is [not obvious](https://github.com/rust-lang/rust/pull/155377). So I'd like to keep an extra eye one it.
2026-04-25 23:07:53 +02:00
Martin Nordholts ff73b8ac2b triagebot.toml: Ping Enselic when tests/debuginfo/basic-stepping.rs changes
The test `tests/debuginfo/basic-stepping.rs` has a history of regressing
for subtle reasons, and has non-obvious expectations. So I'd like to
keep an extra eye on it.
2026-04-25 10:11:10 +02:00
cyrgani 11ba127dfc move remaining files from deriving to derives 2026-04-22 20:26:08 +00:00
Jonathan Brouwer f86378ca17 Rollup merge of #155352 - Enselic:label-sync, r=Mark-Simulacrum
triagebot.toml: Sync `assign.owners` with `autolabel."T-compiler"`

In `autolabel."T-compiler"`, several `./tests/*` dirs are listed.

But many of them are missing from `assign.owners`. Add them all to `assign.owners` so reviewers are picked from the compiler group, and not from the small `assign.adhoc_groups.fallback` group.

Discovered in https://github.com/rust-lang/rust/pull/153941#issuecomment-4065145752.

CC fallback group @Mark-Simulacrum @jieyouxu who can maybe confirm that the old setup was not intentional? (Edit: I hope it was not intentional, because in that case I should have reached out to you personally beforehand.)
2026-04-19 16:04:30 +02:00
Stuart Cook 37344ab259 Rollup merge of #155384 - mejrs:pingme, r=jieyouxu
triagebot: notify on diagnostic attribute changes

Did I get this right? 😆
2026-04-17 16:17:58 +10:00
mejrs 4645f036d0 triagebot: notify on diagnostic attribute changes 2026-04-16 15:48:06 +02:00
Martin Nordholts f684713c43 triagebot.toml: Sync assign.owners with autolabel."T-compiler"
In `autolabel."T-compiler"`, several `./tests/*` dirs are listed.

But many of them are missing from `assign.owners`. Add them all to
`assign.owners` so reviewers are picked from the compiler group, and not
from the small `assign.adhoc_groups.fallback` group.
2026-04-15 20:33:24 +02:00
Waffle Lapkin 0a0dc9e13c remove ibraheemdev from review rotation 2026-04-14 20:03:24 +02:00
Jonathan Brouwer 1bc6b6a05e Rollup merge of #154767 - jieyouxu:lib-tests, r=Mark-Simulacrum
triagebot: roll library reviewers for `{coretests,alloctests}`

Noticed in https://github.com/rust-lang/rust/pull/154761 that we are currently rolling fallback reviewers for `library/{alloctests,coretests}`

r? libs
2026-04-04 20:20:00 +02:00
Jieyou Xu d5f67d8631 triagebot: roll library reviewers for {coretests,alloctests} 2026-04-04 01:18:55 +08:00
David Wood 4fbcb031de cg_llvm: sve_tuple_{create,get,set} intrinsics
Clang changed to representing tuples of scalable vectors as
structs rather than as wide vectors (that is, scalable vector types
where the `N` part of the `<vscale x N x ty>` type was multiplied by
the number of vectors). rustc mirrored this in the initial implementation
of scalable vectors.

Earlier versions of our patches used the wide vector representation and
our intrinsic patches used the legacy
`llvm.aarch64.sve.tuple.{create,get,set}{2,3,4}` intrinsics for creating
these tuples/getting/setting the vectors, which were only supported
due to LLVM's `AutoUpgrade` pass converting these intrinsics into
`llvm.vector.insert`. `AutoUpgrade` only supports these legacy intrinsics
with the wide vector representation.

With the current struct representation, Clang has special handling in
codegen for generating `insertvalue`/`extractvalue` instructions for
these operations, which must be replicated by rustc's codegen for our
intrinsics to use. This patch implements new intrinsics in
`core::intrinsics::scalable` (mirroring the structure of
`core::intrinsics::simd`) which rustc lowers to the appropriate
`insertvalue`/`extractvalue` instructions.
2026-04-03 10:27:30 +00:00
Guillaume Gomez 8c8e0c3074 Rollup merge of #154515 - sayantn:std-detect-notify, r=tgross35
Notify stdarch maintainers on changes in std_detect

cc @Amanieu @folkertdev @Kobzol

It would be nice to be notified when std_detect changes, as it is spiritually a part of stdarch.

Also assign @rust-lang/libs to std_detect
2026-03-29 00:06:53 +01:00
sayantn fbfecb8d78 Map std_detect to t-libs 2026-03-29 00:31:12 +05:30
sayantn 14e4991c03 Notify stdarch maintainers for std_detect 2026-03-29 00:25:43 +05:30
Jieyou Xu a53f0bc7ea triagebot: add reminder for bumping CI LLVM stamp 2026-03-28 12:14:27 +08:00
Jacob Pratt a16a4c3f86 Rollup merge of #154430 - apiraino:create-gpu-target-notif-group, r=jieyouxu
Create GPU target notification group

Creating the notification group for the newly created GPU target (see [mcp#960](https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Create.20a.20GPU.20notification.20group.20compiler-team.23960/near/568629680))

I'm following these [steps](https://github.com/rust-lang/rust/issues/133334).

(feel free to suggest a better wording)

r? @jieyouxu
2026-03-27 02:30:09 -04:00
apiraino 5efde4b728 Create GPU target notification group
* Create GPU target notification group
* Update triagebot.toml

Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com>
2026-03-26 16:32:50 +00:00
David Wood 1384f66c1c triagebot: remove myself from some mention groups
I haven't worked in these areas for a little while, but happy to still be
pinged if someone wanted.
2026-03-10 13:11:00 +00:00
Matthias Krüger 9b45a3c7a8 Rollup merge of #153624 - fmease:ping-me-on-parser-changes, r=fmease
Ping fmease on parser modifications

From time to time innocuous-seeming PRs get submitted and sometimes even approved that unbeknownst to their author and to reviewers change the grammar of (stable) Rust which would be a breaking change; often they only meant to tweak diagnostics.

I sometimes catch such PRs before they get merged but I want to make it a lot harder for them to slip through the cracks going forward.

I'm going to list recent examples to paint a picture (note: this is not about blame!):

1. https://github.com/rust-lang/rust/pull/149728#pullrequestreview-3916816500 (2026)
   * caught before merge but after approval
   * PR unapproved for now
2. https://github.com/rust-lang/rust/issues/152501 (2026)
   * caught after merge of rust-lang/rust#149489
   * fixed & backported
3. https://github.com/rust-lang/rust/issues/152499 (2026)
   * caught after merge of rust-lang/rust#149667
   * fixed & backported
4. https://github.com/rust-lang/rust/pull/151960#discussion_r2751649272 (2026)
   * caught right after submission
   * the approach was thus changed
5. rust-lang/rust#148238 (2025)
   * caught after merge of rust-lang/rust#118947
   * still unaddressed
6. https://github.com/rust-lang/rust/pull/144386#pullrequestreview-3052288562 (2025)
   * caught right after submission
   * crater & T-lang were activated by me
7. https://github.com/rust-lang/rust/pull/119042#discussion_r1429189817 (2023)
   * caught right after submission
   * the approach was thus changed
8. https://github.com/rust-lang/rust/issues/103534 (2022)
   * caught way later
   * partially addressed

Why not just post a note without pinging me? Well, due to them not failing CI and generally due to (friendly) botspam, such comments just get lost or sometimes even actively ignored.

Of course, I'm not able to catch everything. E.g., I didn't notice issue https://github.com/rust-lang/rust/issues/146417 before PR https://github.com/rust-lang/rust/pull/139858 was merged despite having skimmed its diff and more importantly, I as a reviewer missed the blatantly obvious https://github.com/rust-lang/rust/issues/144958 before merge.

Separately, off and on over the span of one year I've worked on a Rust parser that now has >99% accuracy/parity with rustc according to some metrics (this includes stable + unstable + internal syntax) and which I'm now using to detect such regressions and issues in general among other things (e.g., https://github.com/rust-lang/rust/issues/152499 and https://github.com/rust-lang/rust/issues/152820 were found this way, more to come). I'm pretty invested, let's say.

r? me
2026-03-09 23:47:04 +01:00
León Orell Valerian Liehr c5c8d6bac7 Ping fmease on parser modifications 2026-03-09 18:22:39 +01:00
Jonathan Brouwer 83e6dbf9e1 Rollup merge of #151900 - tgross35:num-internal-imp, r=Mark-Simulacrum
num: Separate public API from internal implementations

Currently we have a single `core::num` module that contains both thin wrapper API and higher-complexity numeric routines. Restructure this by moving implementation details to a new `imp` module.

This results in a more clean separation of what is actually user-facing compared to items that have a stability attribute because they are public for testing.

The first commit does the actual change then the second moves a portion back.
2026-03-08 22:51:52 +01:00
Jonathan Brouwer 06b411cede Rollup merge of #153230 - jieyouxu:rustfmt-reviewers-for-rustfmt, r=ytmimi
Roll rustfmt reviewers for in-tree rustfmt

Noticed in https://github.com/rust-lang/rust/pull/153229#issuecomment-3977482140, where because `src/tools/rustfmt` has no corresponding `[assign.owners]` entry, it rolls one of the `fallback` reviewers (Mark and me) which is needless indirection, since if it rolls to Mark, Mark will have to reroll again.

This _can_ also be

```toml
"/src/tools/rustfmt" = ["rustfmt", "rustfmt-contributors"]
```

which corresponds to https://github.com/orgs/rust-lang/teams/rustfmt and https://github.com/orgs/rust-lang/teams/rustfmt-contributors respectively. I will double-check with triagebot team if we can use review rotation toggles for `rust-lang/rust` in-tree `rustfmt` specifically.

Discussion: [#t-rustfmt > review queue tracking for rust-lang/rust in-tree rustfmt](https://rust-lang.zulipchat.com/#narrow/channel/357797-t-rustfmt/topic/review.20queue.20tracking.20for.20rust-lang.2Frust.20in-tree.20rustfmt/with/576498516)

### Unresolved question

- ~~Do we want to start everyone off as off-rotation? Or on-rotation? I plan to start conservatively by preserving existing effective status, which is everyone off-rotation.~~ We will match existing defaults, with everyone starting off as off-team-rotation.

r? @ytmimi
2026-03-06 18:49:50 +01:00
Jonathan Brouwer 53ef4d297e Rollup merge of #153414 - JonathanBrouwer:translate_cleanup, r=Kivooeo
Rename translation -> formatting

Because there is no translation happening anymore

r? @Kivooeo
2026-03-04 19:30:42 +01:00
Jonathan Brouwer d8092147fe Rename translation -> formatting 2026-03-04 17:47:24 +01:00
Jieyou Xu c9529f361c triagebot: remove a ping for jieyouxu 2026-03-04 22:09:02 +08:00
Jakub Beránek 778e602bb5 Do not ping kobzol on rustc-dev-guide changes 2026-03-02 19:27:28 +01:00
Jieyou Xu c9763e717d triagebot: roll rustfmt reviewers for in-tree rustfmt 2026-03-01 16:29:39 +08:00
Urgau 0512fb068c Enable "View all comments" link feature in triagebot.toml 2026-02-18 21:55:31 +01:00
Nicholas Nethercote e9288e7e90 Remove last remnants of rustc_query_system.
At this point module `ich` is the only thing left.
2026-02-16 22:56:47 +11:00
Nicholas Nethercote ed091aaf5d Move rustc_query_system::query::dep_graph to rustc_middle.
Most of the files within the `dep_graph` module can be moved wholesale
into `rustc_middle`. But two of them (`mod.rs` and `dep_node.rs`) have
the same name as existing files in `rustc_middle`, so for those I just
copied the contents into the existing files.

The commit also moves `QueryContext` and `incremental_verify_ich*`
because they are tightly intertwined with the dep graph code. And a
couple of error structs moved as well.
2026-02-14 18:46:05 +11:00
Asuna 4c10efb939 Replace "bug" with "issue" in triagebot ping messages 2026-02-13 07:55:58 +01:00
Trevor Gross 23e44f65aa num: Separate public API from internal implementations
Currently we have a single `core::num` module that contains both thin
wrapper API and higher-complexity numeric routines. Restructure this by
moving implementation details to a new `imp` module.

This results in a more clean separation of what is actually user-facing
compared to items that have a stability attribute because they are
public for testing.
2026-02-11 17:10:33 -06:00
Jonathan Brouwer 415780bb11 Rollup merge of #152326 - Kobzol:remove-compiler-adhoc-group, r=wesleywiser
Remove the compiler adhoc group

Since triagebot now allows configuring rotation mode through a specific team.

Original review rotation:

```toml
compiler = [
    "@BoxyUwU",
    "@chenyukang",
    "@davidtwco",
    "@eholk",
    "@fee1-dead",
    "@fmease",
    "@jackh726",
    "@jieyouxu",
    "@jdonszelmann",
    "@JonathanBrouwer",
    "@madsmtm",
    "@mati865",
    "@Nadrieril",
    "@nnethercote",
    "@oli-obk",
    "@petrochenkov",
    "@SparrowLii",
    "@TaKO8Ki",
    "@tiif",
    "@WaffleLapkin",
    "@wesleywiser",
]
```

I went through all the remaining members of t-compiler now and set their `compiler` team rotation to be off, to match the original state. You can check it with `team-stats compiler`.

r? @davidtwco
2026-02-09 23:37:49 +01:00
Jakub Beránek 5862618fab Remove the compiler adhoc group 2026-02-08 09:52:34 +01:00
Jakub Beránek f46032089a Remove project-exploit-mitigations adhoc group 2026-02-08 09:24:38 +01:00
Jakub Beránek 5e33ea7b92 Remove project-stable-mir adhoc group 2026-02-08 09:23:04 +01:00
Jakub Beránek c19c780d45 Remove project-const-traits adhoc group 2026-02-08 09:22:24 +01:00
Jakub Beránek 6b1ed212b7 Remove types adhoc group 2026-02-08 09:16:31 +01:00
Jakub Beránek d53133eec2 Remove rustdoc adhoc group 2026-02-07 22:03:40 +01:00
Jonathan Brouwer 4ae29f946a Rollup merge of #152222 - TaKO8Ki:add-tako8ki-to-triagebot, r=davidtwco
Re-add TaKO8Ki to triagebot review queue

I’m rejoining the compiler review rotation to help with ongoing review load.
2026-02-06 15:33:41 +01:00
Takayuki Maeda ee2c39a2b4 re-add TaKO8Ki to triagebot review queue 2026-02-06 22:24:36 +09:00
apiraino 623c9cd143 update compiler stable backport zulip msg 2026-02-05 18:24:30 +01:00
Jonathan Brouwer 6eb9c02a96 Subscribe myself to translation diagnostics 2026-01-28 22:40:28 +01:00
Jieyou Xu 1973d65ade misc: roll bootstrap reviewers for src/tools/build-manifest 2026-01-21 09:59:34 +08:00
Jieyou Xu 5e960ef418 triagebot: label src/tools/build-manifest with T-bootstrap 2026-01-21 09:58:33 +08:00
tiif 40691d0ca6 Add myself to the review rotation 2026-01-19 01:46:08 +00:00
lcnr db36c093ca remove lcnr from compiler review rotation 2026-01-16 10:21:06 +01:00
Guillaume Gomez bf31616b85 Rollup merge of #150587 - add-rustdoc-js-autolabel, r=fmease
triagebot: add A-rustdoc-js autolabel

Adds an autolabel rule for rustdoc JavaScript/TypeScript files so PRs touching
rustdoc frontend assets and related tests are automatically labeled `A-rustdoc-js`.

Fixes rust-lang/rust#137983
2026-01-13 23:39:07 +01:00
Jayan Sunil 2d49cfe6aa fix: added missing type in triagebot.toml 2026-01-13 03:17:32 +05:30
Matthias Krüger 7fd7eecf1f Rollup merge of #150922 - subscribe-attr-parsing, r=Urgau
Subscribe myself to attr parsing
2026-01-11 09:56:51 +01:00