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
While building for conda-forge, I noticed that the first run had some failures on linux that appeared only in one out of three runs (py38/py39/py310).
From previous experience that such failures occasionally can depend on absence/presence of CPU features (and the fact that the azure agents are randomly assigned but have different capabilities), I checked whether that was the case, and indeed, the failures occurred only for non-AVX512 machines.
I went to some length to validate this by forcing runs to explicitly have both either AVX512 or not (by failing and restarting if otherwise), and indeed, the following two tests then fail consistently in the non-AVX512 case:
=========================== short test summary info ============================
FAILED core/tests/test_umath.py::TestSpecialFloats::test_exp2 - AssertionErro...
FAILED core/tests/test_umath_accuracy.py::TestAccuracy::test_validate_transcendentals
= 2 failed, 17280 passed, 848 skipped, 1293 deselected, 20 xfailed, 5 xpassed in 212.59s (0:03:32) =
Finally, given previous issues with #15179 / #19192, I then checked if things fail with a "newer" glibc (2.17 in CentOS 7), and then, the failures are gone, see this run.
From the discussions in those previous glibc-related issues, I take that the appetite to spend time on these things is low, but I'd hope that skipping those tests (based on the glibc version check introduced in #19209) would be acceptable?
From the discussions in those previous glibc-related issues, I take that the appetite to spend time on these things is low, but I'd hope that skipping those tests (based on the glibc version check introduced in #19209) would be acceptable?
Sounds good to me. I will have a patch to fix this.
While building for conda-forge, I noticed that the first run had some failures on linux that appeared only in one out of three runs (py38/py39/py310).
From previous experience that such failures occasionally can depend on absence/presence of CPU features (and the fact that the azure agents are randomly assigned but have different capabilities), I checked whether that was the case, and indeed, the failures occurred only for non-AVX512 machines.
I went to some length to validate this by forcing runs to explicitly have both either AVX512 or not (by failing and restarting if otherwise), and indeed, the following two tests then fail consistently in the non-AVX512 case:
Here's a link to the CI run for that.
Finally, given previous issues with #15179 / #19192, I then checked if things fail with a "newer" glibc (2.17 in CentOS 7), and then, the failures are gone, see this run.
From the discussions in those previous glibc-related issues, I take that the appetite to spend time on these things is low, but I'd hope that skipping those tests (based on the glibc version check introduced in #19209) would be acceptable?
The text was updated successfully, but these errors were encountered: