Make borrow-state tests portable to 32-bit targets
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 141
- Avg merge
- 16m
- Merged PRs (30d)
- 3
Description
The borrow-state tests assert exact values of the process-global borrow-flag count. On Debian i386, the no-feature test suite can observe an additional registered flag and fails with an assertion such as left: 2, right: 1, while the array-count and safety checks remain valid.
The exact n_flags assertions should either be made architecture-independent or limited to targets where the underlying registry behavior is deterministic. This was found while packaging rust-numpy 0.28.0 for Debian unstable.
A Debian-side patch currently gates the exact n_flags assertions to 64-bit targets while preserving the other borrow-state checks. The corresponding i386 build passes with that patch.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the borrow-state tests and locate the assertions on the process-global n_flags count. Run the no-feature test suite on a 32-bit target and compare it with a 64-bit target, keeping the array-count and safety checks intact. Done means the exact count checks no longer fail because of architecture-specific registry behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100