[issue26583] test_timestamp_overflow fails

New submission from Peter Inglesby: I get the following test failure against changeset 100576 on OSX 10.9.5: $ ./python.exe -m test test_import [1/1] test_import test test_import failed -- Traceback (most recent call last): File "/Users/peteringlesby/src/cpython/Lib/test/test_import/__init__.p

[issue26583] test_timestamp_overflow fails

Changes by SilentGhost : -- components: +Macintosh, Tests nosy: +ned.deily, ronaldoussoren type: -> behavior ___ Python tracker ___ _

[issue26583] test_timestamp_overflow fails

Ned Deily added the comment: Sorry, I am unable to reproduce this on either 10.9.5 or current 10.11.3 OS X systems. Is there something unusual about the working directory you are running the tests from, like residing on an NFS or other networked file system? Any special ./configure options?

[issue26583] test_timestamp_overflow fails

Peter Inglesby added the comment: The problem is that I have PYTHONDONTWRITEBYTECODE set in my environment. Should the setUp and tearDown methods ensure that PYTHONDONTWRITEBYTECODE is cleared and reset? -- ___ Python tracker

[issue26583] test_timestamp_overflow fails

Peter Inglesby added the comment: I can reproduce it reliably. I ran ./configure with --with-pydebug. I'm not using NFS, and I'm not aware of anything else unusual about my filesystem. The fact that a timestamp overflows in the failing test is a red herring -- the following also fails, with