-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
df: detect over-mounted device #4316
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
Conversation
what are the two binaries? (they are quite big btw) Would it be possible to write a test for this? |
f18724f
to
093eb76
Compare
Yup, shouldn't have pushed those blobs. RE: tests - Isn't it sufficient that a GNU test covers this? |
nope, the GNU testsuite takes an hour to run in the CI. |
GNU testsuite comparison:
|
GNU testsuite comparison:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but under the Run GNU root tests
job, we still have a FAIL: tests/df/over-mount-device.sh
. Any idea why that might be? Were you able to run that test on a local machine or virtual machine?
2b38fce
to
65fe643
Compare
There are quotes missing around the path :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool:
PASS: tests/df/over-mount-device.sh
Looks like there are some CI failures though
This should fix the spell checks, I believe that's all that's left to do? |
not yet, needs some love on Windows:
|
@ctsk ping? |
Hey, got caught up with other matters. Might get to it later this week. It seems like over-mounting is not a thing on windows, hopefully all that's needed is a platform check, |
Co-authored-by: jfinkels <jfinkels@users.noreply.github.com>
482c251
to
83a032f
Compare
83a032f
to
c221f4c
Compare
Addresses #3970 - Still needs some cleanup around the error handling. Feedback appreciated!
I added Filesystem::from_mount to ensure only valid (i.e. non-overmounted) Filesystem structs are created. I guess the next step for that would be making
Filesystem::new
unavailable outside offilesystem.rs