Rollup of 17 pull requests - #161196
Conversation
getsockname(2) and friends do not count the trailing NUL in the length they report on freebsd, netbsd and qnx, and a caller may bind(2) without one anywhere, so shortening the path by one byte dropped its last character. scan for the NUL within the reported length instead, which is the rule unix(7) gives and subsumes the qnx case the old cfg handled. Fixes rust-lang#118925
genmc: rename 'invalid' to 'moot'
This updates the rust-version file to 7dfb9d0.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@7dfb9d0 Filtered ref: rust-lang/miri@5cd9353 Upstream diff: rust-lang/rust@f73951d...7dfb9d0 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
This updates the rust-version file to 4667d75.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@4667d75 Filtered ref: rust-lang/miri@b4685b1 Upstream diff: rust-lang/rust@7dfb9d0...4667d75 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
When `for<'a>` appears on a closure without `closure_lifetime_binder`, suggest rewriting a simple let-bound closure to a stable `for<'a> fn(...)` binding type annotation when that rewrite is safe.
Cover MachineApplicable rewrites, MaybeIncorrect capture cases, and macro-expanded binders where structured suggestions must be suppressed.
…erver [Priroda] Add TCP DAP mode for VS Code attach
…he `retain` attribute
|
@bors r+ p=5 |
This comment has been minimized.
This comment has been minimized.
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 34baba5 (parent) -> 2c39ff4 (this PR) Test differencesShow 50 test diffsStage 0
Stage 1
Stage 2
Additionally, 28 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 2c39ff499469be916d4e45506d1afed69bbaddb7 --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 (2c39ff4): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 4.3%, secondary 1.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -9.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 455.832s -> 457.537s (0.37%) |
|
📌 Perf builds for each rolled up PR:
parent commit: 34baba5394 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Successful merges:
binutilsbefore buildinggcc#161006 ([CI] Build newerbinutilsbefore buildinggcc)Once#161185 (std: guard against unwinds in queue-basedOnce)iter().last()anditer().next()#161103 (cleanup: rip out unnecessaryiter().last()anditer().next())tests/rustdoc-gui/headers-color.goml#161181 (Add back flaky gui rustdoc testtests/rustdoc-gui/headers-color.goml)r? @ghost
Create a similar rollup