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_time errors on AIX #78554
Comments
32-bit: ====================================================================== Traceback (most recent call last):
File "/data/prj/python/src/python3-3.7.0/Lib/test/test_time.py", line 446, in test_mktime
self.assertEqual(time.mktime(tt), t)
OverflowError: mktime argument out of range ====================================================================== Traceback (most recent call last):
File "/data/prj/python/src/python3-3.7.0/Lib/test/test_time.py", line 129, in test_pthread_getcpuclockid
self.assertNotEqual(clk_id, time.CLOCK_THREAD_CPUTIME_ID)
AssertionError: 12 == 12 64-bit: Traceback (most recent call last):
File "/opt/lib/python3.7/test/test_time.py", line 446, in test_mktime
self.assertEqual(time.mktime(tt), t)
OverflowError: mktime argument out of range ====================================================================== Traceback (most recent call last):
File "/opt/lib/python3.7/test/test_time.py", line 130, in test_pthread_getcpuclockid
t1 = time.clock_gettime(clk_id)
OverflowError: signed integer is greater than maximum The test_mktime failed because The patch in the file Modules/timemodule.c fixes this. The test_pthread_getcpuclockid is a bit more complex as the result is different In 32-bit mode AIX always responds with the constant CLOCK_THREAD_CPUTIME_ID. In AIX clockid_t is actually long long. However, changing the type to parse to "L" See additional change in Modules/timemodule.c Finally, |
Would be very nice to get this to clear on the build bots! |
Could this alos be backported to Version 3.7 and 3.6 - thx! |
On 10/03/2019 19:43, Michael Felt wrote:
|
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: