-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Rollup of 10 pull requests #138693
Rollup of 10 pull requests #138693
Conversation
Fix MCP links
…pter-cleaning "Running tests" chapter cleaning
expand ${workspaceFolder} in sample vim config
It is only used by a single test, yet would take up unnecessary space once stdlib deps get vendored.
Co-authored-by: Ibraheem Ahmed <ibraheem@ibraheem.ca>
Given that we now only enlarge empty spans to "{" or "}", there shouldn't be any danger of enlarging beyond a function body.
clarify BufRead::{fill_buf, consume} docs Fixes rust-lang#85394
@bors r+ rollup=never p=4 |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors treeclosed- |
☀️ 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 c4b38a5 (parent) -> a7fc463 (this PR) Test differencesShow 431 test diffs
Additionally, 404 doctest diffs were found. These are ignored, as they are noisy. Job group index
|
📌 Perf builds for each rolled up PR:
previous master: c4b38a5967 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (a7fc463): comparison URL. Overall result: ❌ regressions - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 3.5%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary 3.2%, secondary 1.9%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResults (primary 8.3%, secondary 8.8%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 776.901s -> 773.717s (-0.41%) |
what. @rust-timer build 836e0e2 |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (836e0e2): comparison URL. Overall result: ❌ regressions - please read the text belowInstruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.1%, secondary -2.2%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary 5.5%, secondary 1.0%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeResults (primary 8.4%, secondary 11.1%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 776.901s -> 775.979s (-0.12%) |
Huh. That PR was not supposed to change anything |
Successful merges:
FunctionCoverageInfo
#138659 (coverage: Don't store a body span inFunctionCoverageInfo
)fuse
to enhance readability #138684 (use then in docs forfuse
to enhance readability)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup