-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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_decimal
failed in pgo
#91821
Comments
When I revert #32242, everything was fine. |
On my own computer I can reproduce this without configuring with sam@samtop ~/Documents/git/cpython (git)-[main] % ./python -m test test_decimal
0:00:00 load avg: 2.15 Run tests sequentially
0:00:00 load avg: 2.15 [1/1] test_decimal
test test_decimal failed -- Traceback (most recent call last):
File "/home/sam/Documents/git/cpython/Lib/test/test_decimal.py", line 5538, in test_from_tuple
self.assertEqual(str(c.create_decimal(x)), '-0E-1000007')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: '-0E-1000026' != '-0E-1000007'
- -0E-1000026
? ^^
+ -0E-1000007
? ^^
test_decimal failed (1 failure)
== Tests result: FAILURE ==
1 test failed:
test_decimal
Total duration: 1.8 sec
Tests result: FAILURE
2 sam@samtop ~/Documents/git/cpython (git)-[main] % |
I also get the same error on Windows (no PGO, debug build) when running test_decimal. I'm curious as to why our CI is still passing. |
I can reproduce the test failure on MacOS, even in debug mode, and even with #32242 reverted. However, it reproduces only with |
The test relies on precision being set to 9, but some ways of invoking this test leave it set to 28 instead. I don't know exactly how it happens, but setting the precision directly should make the behavior consistent.
#77931 (PR #7355) fixed a previous similar problem with this test; cc @serhiy-storchaka. |
Fails also on FreeBSD (no PGO) |
The test relies on precision being set to 9, but some ways of invoking this test leave it set to 28 instead. I don't know exactly how it happens, but setting the precision directly should make the behavior consistent.
I merged #91825 which should make this test pass consistently. As a more general solution, I think we should check the decimal global context in |
Bug report
configure with
--enable-optimizations
and thenmake run_profile_task
, fail occurred.After then I tried to reproduce the error.
I found
make buildbottest TESTOPTS="-j4 -uall,-cpu test_decimal"
success! The specific commands it executes are:Because
pgo
mode does not have the-w
parameter, it will not re-run after fail.Finally, I reset commit and locate that gh-91291 causing the problem.
The text was updated successfully, but these errors were encountered: