Skip to content

Conversation

@Enselic
Copy link
Member

@Enselic Enselic commented Oct 15, 2025

In 9253e12 a bunch of gdbr-check (for rust-gdb) directives and gdbg-check (for plain gdb) directives were added. But in two places the author accidentally wrote gdbt-check instead (t is next to r on the keyboard). This commit fixes that typo.

#129218 later renamed gdbr-check to just gdb-check which is why we rename to gdb-check directly.

The test still passes locally for me after the change, but fails if I change the gdb-check checks to check for some other string, so the check seems to still perform its intended function.

Note that we need to add a std::hint::black_box() to avoid

$4 = <optimized out>

prints on at least aarch64-gnu-llvm-20-1.

After this there are no more instances of the string gdbt in the code base:

$ git grep gdbt

try-job: dist-i586-gnu-i586-i686-musl

@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 Oct 15, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 15, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
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

@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@Enselic Enselic 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 Oct 17, 2025
@Enselic Enselic force-pushed the gdbt-check-typo branch 3 times, most recently from 9cfef2e to b2af5c5 Compare October 17, 2025 16:58
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Oct 17, 2025
@Zalathar
Copy link
Member

Looks good; might as well just try to merge this and #148097.

@bors r+ rollup

@bors
Copy link
Collaborator

bors commented Oct 26, 2025

📌 Commit b2af5c5 has been approved by Zalathar

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 26, 2025
Zalathar added a commit to Zalathar/rust that referenced this pull request Oct 26, 2025
tests: activate misspelled `gdb-check` in `function-arg-initialization.rs`

In 9253e12 a bunch of `gdbr-check` (for `rust-gdb`) directives and `gdbg-check` (for plain `gdb`) directives were added. But in two places the author accidentally wrote `gdbt-check` instead (`t` is next to `r` on the keyboard). This commit fixes that typo.

rust-lang#129218 later renamed `gdbr-check` to just `gdb-check` which is why we rename to `gdb-check` directly.

The test still passes locally for me after the change, but fails if I change the `gdb-check` checks to check for some other string, so the check seems to still perform its intended function.

Note that we need to add a `std::hint::black_box()` to avoid

    $4 = <optimized out>

prints on at least `aarch64-gnu-llvm-20-1`.

After this there are no more instances of the string `gdbt` in the code base:
```console
$ git grep gdbt
```
Zalathar added a commit to Zalathar/rust that referenced this pull request Oct 26, 2025
…lathar

tests/debuginfo/closures.rs: Activate misspelled `cdb-check`

Split out from rust-lang#147799 because these seemingly simple corrections can turn out to be non-trivial. See rust-lang#147728 for example.
bors added a commit that referenced this pull request Oct 26, 2025
Rollup of 4 pull requests

Successful merges:

 - #145665 (Don't require `T: RefUnwindSafe` for `vec::IntoIter<T>: UnwindSafe`)
 - #147728 (tests: activate misspelled `gdb-check` in `function-arg-initialization.rs`)
 - #148097 (tests/debuginfo/closures.rs: Activate misspelled `cdb-check`)
 - #148118 (Improve the ICE message for invalid nullary intrinsic calls)

r? `@ghost`
`@rustbot` modify labels: rollup
@Zalathar
Copy link
Member

Failed in rollup in dist-i586-gnu-i586-i686-musl: #148123 (comment)

@bors r-

@bors bors removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Oct 26, 2025
@Enselic
Copy link
Member Author

Enselic commented Nov 1, 2025

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Nov 1, 2025
@jieyouxu
Copy link
Member

jieyouxu commented Nov 1, 2025

r? Zalathar (since you already looked at this)

@rustbot rustbot assigned Zalathar and unassigned Mark-Simulacrum Nov 1, 2025
@Zalathar
Copy link
Member

Zalathar commented Nov 2, 2025

@bors r+ rollup=iffy

@bors
Copy link
Collaborator

bors commented Nov 2, 2025

📌 Commit 192f862 has been approved by Zalathar

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 Nov 2, 2025
bors added a commit that referenced this pull request Nov 2, 2025
tests: activate misspelled `gdb-check` in `function-arg-initialization.rs`

In 9253e12 a bunch of `gdbr-check` (for `rust-gdb`) directives and `gdbg-check` (for plain `gdb`) directives were added. But in two places the author accidentally wrote `gdbt-check` instead (`t` is next to `r` on the keyboard). This commit fixes that typo.

#129218 later renamed `gdbr-check` to just `gdb-check` which is why we rename to `gdb-check` directly.

The test still passes locally for me after the change, but fails if I change the `gdb-check` checks to check for some other string, so the check seems to still perform its intended function.

Note that we need to add a `std::hint::black_box()` to avoid

    $4 = <optimized out>

prints on at least `aarch64-gnu-llvm-20-1`.

After this there are no more instances of the string `gdbt` in the code base:
```console
$ git grep gdbt
```

try-job: dist-i586-gnu-i586-i686-musl
@bors
Copy link
Collaborator

bors commented Nov 2, 2025

⌛ Testing commit 192f862 with merge a56143f...

@bors
Copy link
Collaborator

bors commented Nov 2, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 2, 2025
@Enselic
Copy link
Member Author

Enselic commented Nov 3, 2025

GitHub gives me errors when trying to look at the test log, so I'll re-run the failed job manually:

@bors try jobs=x86_64-gnu

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Nov 3, 2025
tests: activate misspelled `gdb-check` in `function-arg-initialization.rs`

try-job: x86_64-gnu
@rust-bors
Copy link

rust-bors bot commented Nov 3, 2025

☀️ Try build successful (CI)
Build commit: fce8500 (fce85000520569138267188d347c6864883692c4, parent: c5dabe8cf798123087d094f06417f5a767ca73e8)

@Enselic
Copy link
Member Author

Enselic commented Nov 3, 2025

Previous failure seems like flakiness.

@bors retry

@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 Nov 3, 2025
@Zalathar
Copy link
Member

Zalathar commented Nov 3, 2025

My rule of thumb is that if GitHub refuses to show a raw log, then it's probably the case that a GitHub runner flaked out.

@bors
Copy link
Collaborator

bors commented Nov 3, 2025

⌛ Testing commit 192f862 with merge 35ebdf9...

@bors
Copy link
Collaborator

bors commented Nov 3, 2025

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 35ebdf9 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 3, 2025
@bors bors merged commit 35ebdf9 into rust-lang:master Nov 3, 2025
13 checks passed
@rustbot rustbot added this to the 1.93.0 milestone Nov 3, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

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 f2bae99 (parent) -> 35ebdf9 (this PR)

Test differences

Show 4 test diffs

4 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 35ebdf9ba1414456dfe1cb6a6b13ebae80e99734 --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. dist-various-2: 2060.4s -> 2294.8s (+11.4%)
  2. x86_64-gnu-aux: 12107.6s -> 10859.2s (-10.3%)
  3. x86_64-mingw-1: 9346.7s -> 10291.8s (+10.1%)
  4. x86_64-gnu-stable: 6354.0s -> 6991.0s (+10.0%)
  5. aarch64-apple: 7754.0s -> 8509.9s (+9.7%)
  6. aarch64-msvc-2: 4863.6s -> 5307.6s (+9.1%)
  7. dist-loongarch64-linux: 5514.9s -> 5014.4s (-9.1%)
  8. dist-x86_64-apple: 8021.1s -> 7351.9s (-8.3%)
  9. dist-aarch64-apple: 7820.8s -> 7218.1s (-7.7%)
  10. dist-ohos-armv7: 4229.4s -> 3933.3s (-7.0%)
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
Collaborator

Finished benchmarking commit (35ebdf9): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (secondary -2.3%)

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.3% [-2.3%, -2.3%] 1
All ❌✅ (primary) - - 0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 475.169s -> 474.155s (-0.21%)
Artifact size: 390.81 MiB -> 390.84 MiB (0.01%)

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

Labels

merged-by-bors This PR was explicitly merged by bors. 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.

8 participants