-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
test_future_import asserts due to result_lines returning 2.3999999999999999 and not 2.4 #408
Comments
I cant reproduce , note python 3.12 below ]$ pytest test/test_template.py::FuturesTest::test_future_import
==================================================================================== test session starts =====================================================================================
platform linux -- Python 3.12.4, pytest-8.1.0, pluggy-1.4.0 -- /home/classic/.venv3/bin/python
cachedir: .pytest_cache
rootdir: /home/classic/dev/mako
configfile: setup.cfg
plugins: xdist-3.4.0, anyio-4.1.0, random-0.2, repeat-0.9.3
collected 1 item
test/test_template.py::FuturesTest::test_future_import PASSED [100%]
===================================================================================== 1 passed in 0.05s ======================================================================================
[classic@framework mako:review/michael_bayer/update_pyproject]$ |
Interesting, are you on aarch64? I'm doing this on NixOS on an aarch64 system (Apple Silicon M1 Pro). I've tried running this test multiple times and it consistently. I also am using an LLVM built environment so I wonder if some sort of optimization could have caused this. |
OK so this is some kind of CPU thing? im on x86_64. if this is doing a pure FP comparison then the test should be changed to use rounding or something, feel free to send a PR. |
Possibly, I am not 100% sure. I'm going to try an x86_64 machine as well. |
This happens to me on Apple Silicon also. Not in the default environment, and not in the LLVM one that @RossComputerGuy is using, but in a musl cross compliation environment. It does not happen in a musl native environment. |
Confirmed it happens on a non-Apple Silicon aarch64 machine too. |
Mike Bayer has proposed a fix for this issue in the main branch: update future import test https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5683 |
Proposed patch solves my problem. |
Discovered with Nix
The text was updated successfully, but these errors were encountered: