-
Notifications
You must be signed in to change notification settings - Fork 192
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
xmlrpc y2038 problem #1764
Comments
I don't know what However I suspect the problem is some of the fixture data has a large id number, so I'll reduce that below If that fix still doesn't work, the output of the following would be helpful:
Really weird this test would only fail in this specific situation though. |
@bmwiedemann Could you take over the conversation here, please? |
The current #1765 does not help as it fixes nothing that would only break in 2038. Here is a full backtrace:
|
…retending to be ints
Sorry, it was not clear to me on reading your initial comment that you were running these tests in the YEAR 2038. The problem is this section of code uses a timestamp from Since the xmlrpc doesn't support 64 bit ints, I'm not really sure I want to force these into strings just to fix a problem that won't exist for another 16 years. Anyway I will fix the tests so they don't fail. |
btw: You can emulate it on any Linux with
|
https://stackoverflow.com/questions/107616/xml-rpc-best-way-to-handle-64-bit-values says many xml-rpc implementations support an "i8" data type for 64-bit integers (so if python's xmlrpc.py doesn't it could be time to add it there), but OTOH XML transmits everything as string anyway, so you might just as well convert on the client side. |
(originally filed in the openSUSE Bugzilla):
While working on reproducible builds for openSUSE, I found that our python-softlayer package failed tests in 2038 with
To Reproduce:
(basically run with the machine hardware clock set to post-2038)
Expected behavior
Test suite should pass.
Version
6.1.2 from tarball.
The text was updated successfully, but these errors were encountered: