You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_float_remainder_overflow fails on intel 32-bit because divmod(_, tiny) does not raise invalid value #18388
I assume 1.19 passes, and that this is inside a qemu? Could you show the first few lines of the test log where it reports what CPU features are in play?
Don't be mislead by the 'i586' name. Yes, that is the name for the openSUSE build service. RPM internally even calls it i386. Yet this is the same as any other 32-bit Linux.
I assume you have a pytest plugin generating the pytest header?. We do not build inline into the source tree. But let me check how to optimize the test rig setup.
Activity
mattip commentedon Feb 10, 2021
I assume 1.19 passes, and that this is inside a qemu? Could you show the first few lines of the test log where it reports what CPU features are in play?
charris commentedon Feb 10, 2021
i586 is really old, do things work for i686?
charris commentedon Feb 10, 2021
I think we reguire SSE2, which came in with i786 (2000).
mattip commentedon Feb 10, 2021
we should make that a hard requirement and not install on these machines
bnavigator commentedon Feb 10, 2021
Yes this is a qemu on the opensuse build sevice. AFAICT SSE2 is enabled. Yes 1.19.5 passes.
Here is the full buildlog:
numpy-1.20-i586_log.txt
bnavigator commentedon Feb 10, 2021
Don't be mislead by the 'i586' name. Yes, that is the name for the openSUSE build service. RPM internally even calls it i386. Yet this is the same as any other 32-bit Linux.
mattip commentedon Feb 10, 2021
The "NumPy CPU features" line I am looking for in the log does not appear. In our CI runs it is this:
bnavigator commentedon Feb 10, 2021
I assume you have a pytest plugin generating the pytest header?. We do not build inline into the source tree. But let me check how to optimize the test rig setup.
bnavigator commentedon Feb 10, 2021
I found the report line. It's not in conftest.py but you use a custom
_pytesttesternumpy-1.20-i586_numpy_info_log.txt
mattip commentedon Feb 10, 2021
Thanks. Our 32-bit run uses the same features
This is building and testing inside the manylinux2010 32 bit docker, and not qemu.
charris commentedon Mar 27, 2021
I cleared the milestone as this is likely an environment issue.