Skip to content

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

Merged
merged 10 commits into from
Jun 17, 2025
Merged

Conversation

asomers
Copy link
Member

@asomers asomers commented Jun 14, 2025

  • Fix the test_fcntl::test_posix_fallocate::success test with recent ZFS
  • Remove the PartialEq and Eq implementations from SigHandler
  • Clippy cleanup: mismatched_lifetime_syntaxes
  • Fix a rustdoc warning on the latest nightly
  • Suppress Clippy::doc_overindented_list_items

See individual commit messages for details

Checklist:

  • I have read CONTRIBUTING.md
  • I have written necessary tests and rustdoc comments
  • A change log has been added if this PR modifies nix's API

@asomers asomers force-pushed the zfs-posix-fallocate branch from 9a5f408 to ea9eef8 Compare June 14, 2025 18:40
@asomers asomers changed the title Fix the test_fcntl::test_posix_fallocate::success test with recent ZFS Address multiple CI failures Jun 14, 2025
@asomers asomers requested a review from SteveLauC June 14, 2025 20:04
@SteveLauC
Copy link
Member

@psumbera Could you please take a look at the Solaris CI?

asomers added 8 commits June 17, 2025 09:16
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.
@SteveLauC SteveLauC force-pushed the zfs-posix-fallocate branch from 6cbccfb to 16df853 Compare June 17, 2025 01:17
@SteveLauC SteveLauC mentioned this pull request Jun 17, 2025
3 tasks
@SteveLauC
Copy link
Member

SteveLauC commented Jun 17, 2025

A recent change in the libc crate broke the timespec type (the tv_nsec field got removed) on x86_64-unknown-linux-gnux32, which breaks the parking_lot_core crate:

https://github.com/Amanieu/parking_lot/blob/ed4ea475002e82ea0f15bcd1d984d7a0fde83fac/core/src/thread_parker/linux.rs#L83-L86

Then it fails our CI

Update: the issue will be fixed by rust-lang/libc#4497

Copy link
Member

@SteveLauC SteveLauC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@SteveLauC SteveLauC added this pull request to the merge queue Jun 17, 2025
Merged via the queue into nix-rust:master with commit a72936d Jun 17, 2025
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants