Conversation
At least on OVMF, some files copied over from linux file system seem to have invalid time (year = 1980 and everything else 0). Since Rust allows time to be optional and we can return error, that seems to be the way to go for now. Signed-off-by: Ayush Singh <[email protected]>
Slice iter cleanup
array_chunks: slightly improve docs
…5, r=Kivooeo Merge E0412 into E0425 This PR merge E0412 into E0425 as both mean the same thing to users. This fixes rust-lang#148558.
also introduce Peekable::next_if_map_mut next to next_if_map As requested in rust-lang#148941 (comment) by ``@joshtriplett``
std: sys: fs: uefi: Make time in FileAttr optional At least on OVMF, some files copied over from linux file system seem to have invalid time (year = 1980 and everything else 0). Since Rust allows time to be optional, and we can return error, that seems to be the way to go for now. `@rustbot` label +O-UEFI
|
@bors r+ rollup=never p=5 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 646a3f8c15 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 646a3f8 (parent) -> a4cfac7 (this PR) Test differencesShow 60 test diffsStage 1
Stage 2
Additionally, 58 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 a4cfac7093a1c1c7fbdb6bc75d6b6dc4d385fc69 --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 (a4cfac7): 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 1.1%, secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 6.6%, secondary 3.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.6%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 468.916s -> 467.504s (-0.30%) |
|
perf triage I supect the doc regression is mostly noise. Either way, I don't think it's worth more investigation, it's just a doc and it's small. @rustbot label: +perf-regression-triaged |
Successful merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup