Repository navigation
DirEntry::metadata: use dirfd on more targets - #163552
Conversation
|
Any special-casing of Miri in the standard library requires review. cc @rust-lang/miri |
|
r? @JohnTitor rustbot has assigned @JohnTitor. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@bors try |
This comment has been minimized.
This comment has been minimized.
DirEntry::metadata: use dirfd everywhere that we support Dir try-job: *bsd* try-job: *various*
9f3dc8b to
90ee551
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
90ee551 to
a6b3a69
Compare
|
@bors try |
This comment has been minimized.
This comment has been minimized.
DirEntry::metadata: use dirfd on more targets try-job: *bsd* try-job: *various*
This comment has been minimized.
This comment has been minimized.
a6b3a69 to
c97c7de
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
c97c7de to
6a7b5dd
Compare
| target_os = "nto", | ||
| target_os = "qnx", | ||
| target_os = "vita", | ||
| target_os = "hurd", |
There was a problem hiding this comment.
hurd has dirfd according to libc, and we've been using it for DirEntry::metadata, so it should be fine to use here as well.
6a7b5dd to
3b1fc44
Compare
3b1fc44 to
46b2135
Compare
|
It's been more than two weeks without any feedback from the reviewer. I guess I should reroll. |
|
Also Cc @the8472 as it's related to directory handles (but this is about functions that are already stable) |
|
@bors r+ rollup=iffy |
This comment has been minimized.
This comment has been minimized.
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 12433c3 (parent) -> dc44e7f (this PR) Test differencesShow 2 test diffs2 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard dc44e7f2c436b6041742e138b9c2176f093196d5 --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 (dc44e7f): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 0.2%, secondary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.2%, secondary -0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.652s -> 487.351s (-0.27%) |
View all comments
Most of the BSDs support
dirfdandfstatatjust fine but for some reason we've not been using it forDirEntry::metadata. This syncs thecfgfor usingdirfdwith the one that we use inDir::closefor the FD sanity check. Those target evidently all havedirfdas we're using it there, and that's a strict subset of the targets that haveDirhandles, so they should supportfstatatas well.try-job: bsd
try-job: various