strophy

@jneem I'm out of my depth already, feel free to comment over at https://github.com/pubgrub-rs/pubgrub/issues/373 I am skipping the test for now in 32-bit Alpine packages of nickel.

I wonder if it could be related to gcc 15 and/or several OpenBLAS changes that were recently patched into Alpine: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/93836 Upstream refs: https://github.com/OpenMathLib/OpenBLAS/pull/5448 https://github.com/OpenMathLib/OpenBLAS/pull/5463 https://github.com/OpenMathLib/OpenBLAS/pull/5472 This issue specifically mentions...

Thanks so much @mmuetzel for helping narrow this down, I really appreciate it! Do you think I should open an issue with OpenBLAS, given they pushed a number of changes...

Thanks both for your helpful comments. https://github.com/OpenMathLib/OpenBLAS/issues/5372 mentions differences between gcc versions, so I'll try to see if I can pin it down to different combinations of OpenBLAS 0.3.29, 0.3.30...

@mpizenberg as a packager this issue isn't a showstopper because it doesn't actually affect usability, my solution is to simply disable the test. I'll leave it to @jneem to possibly...

I work in the embedded space and we certainly do provision Alpine on bare metal Raspberry Pi and Pi Zero devices - it was during deploy of a k3s cluster...

Potential patch to fix the issue by reducing the precision of the comparison to match the other test assertions: ``` diff --git a/src/python/PyImathTest/pyImathTest.py b/src/python/PyImathTest/pyImathTest.py index 6b8c4ac..6c98626 100644 --- a/src/python/PyImathTest/pyImathTest.py +++...

I'd love to see this merged - @Ahuge could you rebase it and maybe ping a maintainer to try again for a review?

Hi @seruman just checking on progress and if there is anything I can do to help move this issue along? Having this feature would allow us to switch back to...