-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Rollup of 11 pull requests #144109
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 11 pull requests #144109
Conversation
external-repos.md: small fixes
Partially reverts commit 40311c4.
See RUST-141600: this test is broken in two ways: 1. This test triggers `-Wincompatible-pointer-types` on GCC 14. 2. This test requires ARMv8.5+ w/ MTE extensions enabled, but GHA CI runner hardware do not have this enabled.
./x is recommended over running ./x.py directly, and is the more commonly-used invocation of bootstrap in the guide
use a consistent (and recommended) invocation
- --depth=1 is more useful for once-off uses, like on ci - .git postfix on github repo url is not needed
That is, calling it an example is misleading
Nowhere else is this called "Dist check"
add missing word
do not invent a name
distcheck has only one possible invocation
…-false, r=clubby789 Boostrap: add warning on `optimize = false` I recently came across a bug that can be traced back to the use of `optimize = false` in `bootstrap.toml` in combination with other settings. Following [this](https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/Missing.20box-related.20symbols.20with.20panic.20.3D.20'abort'/with/528992909) conversation, this PR adds a warning from `bootstrap` when `optimize = false` is used. I notice that in the same file I edited there are two different styles for warnings (`WARN`, `Warning`). I used `WARNING` because, by happenstance, when testing I got a `WARNING` that I didn't set a change id: let me know if I can unify the styles in the file I edited.
rustc-dev-guide subtree update r? ghost
Copy GCC sources into the build directory even outside CI It takes ~3.5s on my Linux notebook to perform the copy, but it should only be executed when we actually go build GCC, and that will almost certainly take much longer :) So I think it should be fine. At least we won't be polluting the source directory for local builds. Fixes: rust-lang#143986 r? `````@nikic`````
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 1aa5b22465 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 1aa5b22 (parent) -> 6c0a912 (this PR) Test differencesShow 229 test diffsStage 1
Stage 2
Additionally, 202 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 6c0a912e5a45904cf537f34876b16ae71d899f86 --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 (6c0a912): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -3.6%, secondary -2.9%)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 sizeResults (primary 0.0%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 464.583s -> 465.309s (0.16%) |
Successful merges:
tests/run-make/mte-ffi
because no CI runners have MTE extensions enabled #142300 (Disabletests/run-make/mte-ffi
because no CI runners have MTE extensions enabled)-Zsanitizer=kcfi
on#[naked]
functions #143293 (fix-Zsanitizer=kcfi
on#[naked]
functions)-o
and arg #143719 (Emit warning when there is no space between-o
and arg)#[coverage]
to the new attribute system #143891 (Port#[coverage]
to the new attribute system)Option
methods #143967 (constifyOption
methods)optimize = false
#144010 (Boostrap: add warning onoptimize = false
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup