-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 7 pull requests #141011
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 7 pull requests #141011
Conversation
It was showing compare mode instead of test name.
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
They will be used in Clippy to detect runtime parsing of known-valid IP addresses.
…e, r=oli-obk Do not ICE when reassigning in GatherLocalsVisitor on the bad path Fixes rust-lang#140785 Fixes rust-lang#140730 See comment in code. r? oli-obk
…Mark-Simulacrum Add an issue template for future-incompatible lints This adds a GitHub issue template for future-incompatible lints. Most of the existing tracking issues have been using different formats with different information, and I think it would be helpful to make them a little more consistent and to ensure that sufficient information is provided. Some comments on my choices: * Added a dedicated section to describe *why* the change is being made. Many existing issues already have this, so let's standardize on it. * Have a section with a very clear example. Almost all of the existing issues have this in one form or another. * Added a "Recommendations" section, since this is something I see missing in several of the existing issues, and this is really important information IMHO. * I reworded the "When" section. The existing template mentioned that these get reviewed every 6 weeks which my understanding is not true. That's also not very helpful information to the user, since it doesn't really answer the question. I'm not sure this section will actually be useful since I suspect most of the time we don't know when it will change (there have been a few exceptions). * Clearly show the expected progression steps. Several issues already have this. * Added implementation history, which is useful for linking PRs. (IDK, this could get merged with "Steps".)
…compiler-errors Fix a compiletest blessing message It was showing compare mode instead of test name. Fixes rust-lang#140945. Noticed in rust-lang#140622 (comment).
…=jieyouxu Update rustix to 1.0.7 for bootstrap Another bump for bootstrap. Finally it compiles on Cygwin:) Hooray! r? ``@jieyouxu``
…Urgau Add `Ipv4Addr` and `Ipv6Addr` diagnostic items They will be used in Clippy to detect runtime parsing of known-valid IP addresses.
…, r=tgross35 MaybeUninit::write: fix doc # Fix doc for `MaybeUninit::write` The documentation refers to the way `MaybeUninit` stores data internally. The property of not dropping content on context exit is the responsibility of `ManuallyDrop`.
…errors Suggest replace f with f: Box<f> when expr field is short hand Fixes rust-lang#139631 r? compiler
@bors r+ rollup=never p=5 |
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#140827 (Do not ICE when reassigning in GatherLocalsVisitor on the bad path) - rust-lang#140904 (Add an issue template for future-incompatible lints) - rust-lang#140953 (Fix a compiletest blessing message) - rust-lang#140973 (Update rustix to 1.0.7 for bootstrap) - rust-lang#140976 (Add `Ipv4Addr` and `Ipv6Addr` diagnostic items) - rust-lang#140988 (MaybeUninit::write: fix doc) - rust-lang#140989 (Suggest replace f with f: Box<f> when expr field is short hand) r? `@ghost` `@rustbot` modify labels: rollup
💔 Test failed - checks-actions |
💔 Test failed - checks-actions |
@bors p=5 |
@bors retry |
How about using |
UPD: CI failure tracking issue is #141022. |
Thanks for that suggestion, trying this in #141023. |
We're now using a workaround to temporarily fallback to Windows Server 2022 images for EDIT(jieyouxu): manually editing out the treeclosed comment to avoid this being picked up in a future sync. |
⌛ Testing commit e39ab25 with merge d163a28381c297a56417d4a5dfe88c6c65429265... |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 2a5da7acd4 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 2a5da7a (parent) -> d163a28 (this PR) Test differencesShow 300 test diffsStage 1
Stage 2
Additionally, 296 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 d163a28381c297a56417d4a5dfe88c6c65429265 --output-dir test-dashboard And 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 (d163a28): comparison URL. Overall result: ✅ improvements - no action needed@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 -0.5%, secondary -2.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.
CyclesResults (primary 1.5%, secondary 7.4%)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 sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 773.204s -> 772.725s (-0.06%) |
Successful merges:
Ipv4Addr
andIpv6Addr
diagnostic items #140976 (AddIpv4Addr
andIpv6Addr
diagnostic items)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup