-
Notifications
You must be signed in to change notification settings - Fork 14k
Rollup of 4 pull requests #149059
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 4 pull requests #149059
Conversation
- Implement std::fs::metadata function. - Tested on qemu ovmf Signed-off-by: Ayush Singh <ayush@beagleboard.org>
std: sys: fs: uefi: Implement stat - Implement std::fs::metadata function. - Tested on qemu ovmf
flush_delayed: add note about stashed diagnostics r? `@nnethercote` Is `emit_stashed_diagnostics` the right advice to give? The other option seems to be to call `finish_diagnostics`. That's what I ended up doing (for now) in rust-lang/miri#4702 because it best matches what happens during normal compilation.
…-variant, r=lolbinarycat Add test for href of reexported enum variant Working on rust-lang#148648 and realized that we actually didn't test for enum variants reexports, so here we are. I also think I'll do rust-lang#148648 at the same time as rust-lang#148547. r? `@lolbinarycat`
compiletest: Use JSON "binary-format" to decide `//@ only-elf` and `//@ ignore-elf` Some tests only apply to ELF targets, or want to enable different test revisions for ELF and non-ELF targets. So compiletest supports the `//@ only-elf` and `//@ ignore-elf` directives to make that possible. Historically, deciding whether the current target is an ELF target relied on a handful of ad-hoc string comparisons against the target tuple. However, nowadays compiletest has access to the output of `--print=all-target-specs-json`, and that JSON output specifies the binary format of each target, making it much easier to determine whether a target is ELF or not.
|
@bors r+ p=5 rollup=never |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: f9e7961506 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 f9e7961 (parent) -> 3d461af (this PR) Test differencesShow 7 test diffsStage 0
Stage 1
Stage 2
Job group index Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3d461af2a23456a2676aadb13b4253c87bdfe28d --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 (3d461af): comparison URL. Overall result: ✅ improvements - no action needed@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)This benchmark run did not return any relevant results for this metric. CyclesResults (primary -2.4%, secondary 0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 471.624s -> 473.417s (0.38%) |
Successful merges:
//@ only-elfand//@ ignore-elf#149049 (compiletest: Use JSON "binary-format" to decide//@ only-elfand//@ ignore-elf)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup