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
#2435 (PR #2436) fixed some instances of EXPECT_EQ being used for floating point comparison instead of EXPECT_DOUBLE_EQ.
gcc-13 appears to have uncovered a few more, causing test failure on i386 and s390x. Tests were previously passing with gcc-12 and are still passing with clang.
l.33 in test_xinfo.cpp is also expected to be a problem with llvm-16. But this is a string comparison not a floating point comparison, so can't be fixed the same way. Why would llvm-16 be returning "le" instead of "double"? Is it a bug in llvm-16?
#2435 (PR #2436) fixed some instances of EXPECT_EQ being used for floating point comparison instead of EXPECT_DOUBLE_EQ.
gcc-13 appears to have uncovered a few more, causing test failure on i386 and s390x. Tests were previously passing with gcc-12 and are still passing with clang.
Test logs are available for i386 (xtensor 0.24.6)
The error is
As far as I can tell it's just further instances where EXPECT_DOUBLE_EQ is required instead of EXPECT_EQ, or similar, following the example of #2436
The gcc-13 trigger might be excess precision changes, https://gcc.gnu.org/gcc-13/porting_to.html
The text was updated successfully, but these errors were encountered: