-
Notifications
You must be signed in to change notification settings - Fork 13.9k
tests: activate misspelled gdb-check in function-arg-initialization.rs
#147728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
rustbot has assigned @Mark-Simulacrum. Use |
This comment has been minimized.
This comment has been minimized.
ca052c1 to
b8c1b25
Compare
This comment has been minimized.
This comment has been minimized.
133bfad to
f88ff0b
Compare
9cfef2e to
b2af5c5
Compare
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 ```
…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.
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
|
Failed in rollup in @bors r- |
|
@rustbot ready |
|
r? Zalathar (since you already looked at this) |
|
@bors r+ rollup=iffy |
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
|
💔 Test failed - checks-actions |
|
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 |
This comment has been minimized.
This comment has been minimized.
tests: activate misspelled `gdb-check` in `function-arg-initialization.rs` try-job: x86_64-gnu
|
Previous failure seems like flakiness. @bors retry |
|
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. |
|
☀️ Test successful - checks-actions |
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 differencesShow 4 test diffs4 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 35ebdf9ba1414456dfe1cb6a6b13ebae80e99734 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (35ebdf9): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 475.169s -> 474.155s (-0.21%) |
In 9253e12 a bunch of
gdbr-check(forrust-gdb) directives andgdbg-check(for plaingdb) directives were added. But in two places the author accidentally wrotegdbt-checkinstead (tis next toron the keyboard). This commit fixes that typo.#129218 later renamed
gdbr-checkto justgdb-checkwhich is why we rename togdb-checkdirectly.The test still passes locally for me after the change, but fails if I change the
gdb-checkchecks 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 avoidprints on at least
aarch64-gnu-llvm-20-1.After this there are no more instances of the string
gdbtin the code base:$ git grep gdbttry-job: dist-i586-gnu-i586-i686-musl