-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xlapack.solveCholesky test precision too high for 32 bit machines #211
Comments
Thanks for the report. We would be interested in a fix, but presumably it would be interesting to include an i386 test in the CI if we want to catch these. |
A pragmatic workaround could be to increase the test tolerance e.g. from 1e-18 to 1e-16 (as an example. I'm not certain what the effective tolerance here is). That could be done here using EXPECT_NEAR in place of EXPECT_DOUBLE_EQ. |
Thanks! |
I can do it. I'll need to investigate what tolerance i386 needs. |
The xlapack.solveCholesky test in test_lapack.cpp fails on 32-bit architectures (i386/i686): [ RUN ] xlapack.solveCholesky /tmp/autopkgtest-lxc.gg3nslld/downtmp/autopkgtest_tmp/test_lapack.cpp:166: Failure Expected equality of these values: x_expected[i] Which is: 0.13757507429403265 x[i] Which is: 0.13757507429403248 [ FAILED ] xlapack.solveCholesky (0 ms) This patch relaxes test tolerance by using EXPECT_NEAR with abstol=2e-16 instead of EXPECT_DOUBLE_EQ. Fixes Issue xtensor-stack#211.
Also affects armhf, confirming it's a 32-bit issue. |
armhf is a little coarser, |
Looks like 5e-16 is enough. i386 and armhf are both passing now with PR #212, Eventually test logs will appear at https://ci.debian.net/packages/x/xtensor-blas/ |
The xlapack.solveCholesky test in
xtensor-blas/test/test_lapack.cpp
Line 150 in 0aee299
uses an expected x value
0.13757507429403265
This tests fails on 32-bit architectures (or at least i386/i686),
Full log at https://ci.debian.net/data/autopkgtest/testing/i386/x/xtensor-blas/15978147/log.gz
The text was updated successfully, but these errors were encountered: