Open bmwiedemann opened 1 month ago
For python 3.13, I found 2037-10-28 as the date when tests start to fail (test.test_asyncio.test_events test_imaplib test_poplib test_ssl
)
For 2038, isn't it related to Unix max timestamp value? (which is January 19, 2038, at 03:14:07). As for 2037-10-28, could it be because we use some offset in the tests (like a fake delta time)?
There are various test certs set to expire in 2037, e.g.:
openssl x509 -text < Python-3.13.0rc2/Lib/test/certdata/pycacert.pem | grep After
Not After : Oct 28 14:23:16 2037 GMT
The previous compileall 2038 bug from 2018 was https://bugs.python.org/issue34990
Bug report
Bug description:
While working on reproducible builds for openSUSE (sponsored by the NLnet NGI0 fund), I found that our
python312
package fails to build when the build runs in a VM withqemu-kvm -rtc base=2038-01-20T00:00:00
3.13 seems to not be affected by the issue in
test_compileall
.The full log is at https://rb.zq1.de/other/python312-ftbfs2038.log.txt (there are also some expiring SSL certs)
CPython versions tested on:
3.12
Operating systems tested on:
Linux