Skip to content

coverage: Tidy tests and add some new ones - #161397

Open
Zalathar wants to merge 3 commits into
rust-lang:mainfrom
Zalathar:tests-coverage
Open

coverage: Tidy tests and add some new ones#161397
Zalathar wants to merge 3 commits into
rust-lang:mainfrom
Zalathar:tests-coverage

Conversation

@Zalathar

Copy link
Copy Markdown
Member

While experimenting with some coverage changes, I noticed that some of our tests are not very useful for diagnosing problems, and that we lack good simple tests for some common Rust constructs.

@rustbot rustbot added 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. labels Aug 20, 2026
@rustbot

rustbot commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

r? @fee1-dead

rustbot has assigned @fee1-dead.
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 75 candidates
  • Random selection from 16 candidates

@rust-log-analyzer

This comment has been minimized.

@Zalathar

Copy link
Copy Markdown
Member Author

Looks like one of the new tests was affected by #151419, so I added a directive to skip it on older LLVM.

@Zalathar Zalathar added A-testsuite Area: The testsuite used to check the correctness of rustc A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) labels Aug 22, 2026
@rustbot

This comment has been minimized.

@rustbot

This comment has been minimized.

@rustbot

This comment has been minimized.

@fee1-dead

Copy link
Copy Markdown
Member

Not very familiar with coverage tests :)

@rustbot reroll

@rustbot

This comment has been minimized.

@rustbot

This comment has been minimized.

@rustbot

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Zalathar
Zalathar force-pushed the tests-coverage branch 2 times, most recently from e29b935 to 46a5610 Compare September 3, 2026 05:55
@rustbot

This comment has been minimized.

These tests are of limited value for investigating specific problems, but still
have some worth in detecting regressions by adding variety to the test corpus.

(The boundary is a bit fuzzy, but it's easy enough to move tests back out if
appropriate.)
@rustbot

rustbot commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

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.

@Zalathar

Zalathar commented Sep 5, 2026

Copy link
Copy Markdown
Member Author

Approved as part of #161517, but landing separately since this is just preliminary test changes.

r? davidtwco
@bors r=davidtwco rollup

@rust-bors

rust-bors Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 492fff7 has been approved by davidtwco

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-review Status: Awaiting review from the assignee but also interested parties. labels Sep 5, 2026
Zalathar added a commit to Zalathar/rust that referenced this pull request Sep 5, 2026
coverage: Tidy tests and add some new ones

While experimenting with some coverage changes, I noticed that some of our tests are not very useful for diagnosing problems, and that we lack good simple tests for some common Rust constructs.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Sep 5, 2026
coverage: Tidy tests and add some new ones

While experimenting with some coverage changes, I noticed that some of our tests are not very useful for diagnosing problems, and that we lack good simple tests for some common Rust constructs.
Zalathar added a commit to Zalathar/rust that referenced this pull request Sep 5, 2026
coverage: Tidy tests and add some new ones

While experimenting with some coverage changes, I noticed that some of our tests are not very useful for diagnosing problems, and that we lack good simple tests for some common Rust constructs.
rust-bors Bot pushed a commit that referenced this pull request Sep 5, 2026
Rollup of 14 pull requests

Successful merges:

 - #162324 (miri subtree update)
 - #162170 (bootstrap: use target's LLVM libdir when cross-compiling)
 - #158312 (Adds support for AArch64 SVE to inline assembly)
 - #159792 (A more readable debug map for IndexMaps)
 - #160745 (make closures act like MaybeDangling)
 - #161263 (break rustc_expand-rustc_middle dependency)
 - #161895 (std::sys::pal::sgx: fix mismatched alloc/free alignment)
 - #161940 (Promote `wasm32-wasip3` to a tier 2 target)
 - #161397 (coverage: Tidy tests and add some new ones)
 - #161616 (Report precondition violation for `<usize as SliceIndex>::get_unchecked` in const-eval)
 - #162248 (Add regression test for unsized const parameter default ICE)
 - #162250 (Fix hashing of span end columns in incremental compilation)
 - #162265 (cargotest: add lockfiles)
 - #162318 (bootstrap: Fix broken path for `./x doc compiler/rustc --open`)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. 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.

6 participants