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
redis make test fails on bash on windows #4537
Comments
Can confirm. I get the exact same issue when running make test. |
I'm having the same issues! I tried OpenSUSE with the exact same error |
18 months later, same issue here. |
The same here |
1 similar comment
The same here |
it seems some compilers on Windows consider long double as a synonym for double.
|
@oranagra I noticed that as well on WSL which is not really distinguishable from any other Linux/x86_64 environment. I think we may need to relax this test or come up with some way to indicate 80-bit floats are not supported. |
So it seems like WSL sets the FPU control register's PC bits to It might make more sense to just relax the tests. @oranagra what do you think? |
i'm ok with relaxing that test a little bit (but still making sure it hits it's purpose). on the other hand, i'm also ok to add an info field that exposes the precision to clients (maybe it'll be useful for others too). maybe @guybe7 has some feedback about this (i remember he messed with some other long-double related issues with tests). |
Environment: Windows 10 Pro 64-bit running Ubuntu subsystem (Ubuntu 16.04.2 LTS)
make install failed with
!!! WARNING The following tests failed:
*** [err]: Test HINCRBYFLOAT for correct float representation (issue #2846) in tests/unit/type/hash.tcl
Expected condition '[r hincrbyfloat myhash float 1.23] eq {1.23}' to be true ([r hincrbyfloat myhash float 1.23] eq {1.23})
Cleanup: may take some time... OK
Makefile:242: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/home/sami/redis/redis-4.0.6/src'
Makefile:6: recipe for target 'test' failed
make: *** [test] Error 2
The text was updated successfully, but these errors were encountered: