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
There are some arch specific failures on Debian that seem related to libatlas. This affects test_polynomial_weighted_estimation for amd64 and test_ellipse_parameter_stability for ppc64el and loongarch64.
See also #7391 (comment) for possible dependencies that might have caused the test assertion failures:
The main difference seems to be that the failing build used libatlas 3.10.3 instead of blas 3.12.0 / libopenblas 0.3.26. All other differences seem minor:
Python distutils, lib2to3, tk from 3.12.2 to 3.12.3
pyproject-metadata only in the Debian release number,
liblua 5.46, gringo 5.6.2, clasp 3.3.5, aspcud 1.9.6 are only in the failed (experimental) build
Python defcon 0.10.3 is only in the failed (experimental) build
Python ufolib2 0.16.0 is only in the successfull (unstable) build
I must say that I don't know why in the experimental build libatlas was preferred over blas; it is a numpy dependency and libblas is there the preferred one. However, they should give the same results, shouldn't they?
From #7391 (comment):
Details
There are some arch specific failures on Debian that seem related to libatlas. This affects
test_polynomial_weighted_estimation
for amd64 andtest_ellipse_parameter_stability
for ppc64el and loongarch64.See also #7391 (comment) for possible dependencies that might have caused the test assertion failures:
cc @olebole
The text was updated successfully, but these errors were encountered: