Closed mgorny closed 2 weeks ago
I see some of those tests are skipped on windows; possibly we should also check for whether the platform is 32 bit and skip on those?
Either that, or adjusting expected sizes depending on the platform.
These are looking at the reprs, so adjusting the expectations isn't easy.
We would def take a PR to skip them based on the platform though!
Does skipping based on the value of sys.maxsize
sound about right? I think that's the simplest way of determining whether we're dealing with a 64-bit platform.
That seems to be the recommended way
we can also try hard-coding the dtype for those variables. Since the difference is in the repr
, the default dtype of the platform is not actually important
Actually, fixing expectations doesn't seem that hard, so I'm going to try doing that first. If you don't like that, we can look into other solutions.
What happened?
When running the test suite on 32-bit platforms (e.g. x86), I'm getting the following test failures:
(log below)
I think the tests assume specific object sizes for 64-bit platforms.
This is Python 3.11.9 on 32-bit x86, retested on 380979fc213b3d1f53f097bab9b61851391be729.
What did you expect to happen?
Tests passing.
Minimal Complete Verifiable Example
MVCE confirmation
Relevant log output
Anything else we need to know?
No response
Environment