-
Notifications
You must be signed in to change notification settings - Fork 693
Address multiple CI failures #2642
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
9a5f408
to
ea9eef8
Compare
@psumbera Could you please take a look at the Solaris CI? |
POSIX 1003.1-2024 Issue 8 changed the error code for this operation, and recent ZFS versions have followed suit. So the test should accept either the old error code (EINVAL) or the new one (ENOTSUP). https://pubs.opengroup.org/onlinepubs/9799919799/functions/posix_fallocate.html
Because it never worked reliably anyway. See https://doc.rust-lang.org/nightly/core/ptr/fn.fn_addr_eq.html for more info. Alternatively, we could only remove `Eq` and leave `PartialEq`. We would be able to guarantee equality or inequality in most cases, but would be unable to prove that different handler functions are actually different. I think users would find that confusing. Reported by: Clippy (unpredictable_function_pointer_comparisons)
Fix the lint in one file, but suppress it in src/sys/aio.rs, where the docstrings are nicely formated for reading in either plain text or html.
6cbccfb
to
16df853
Compare
A recent change in the libc crate broke the Then it fails our CI Update: the issue will be fixed by rust-lang/libc#4497 |
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.
Thanks
test_fcntl::test_posix_fallocate::success
test with recent ZFSPartialEq
andEq
implementations fromSigHandler
See individual commit messages for details
Checklist:
CONTRIBUTING.md