We made several updates to fdtables in past ~1yr, but the test suite was not updated accordingly. As a result, running cargo test within the fdtables library now produces multiple failures.
We should review the updated logic and bring the test suite back in sync with the current behavior. This most likely requires updating the affected tests to match the new semantics (i.e.: arguments changes / etc.).