Stefan Krah added the comment: I'm convinced now that some systems just can't handle a low switch interval gracefully. Look at:
http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/5642/steps/test/logs/stdio ====================================================================== FAIL: test_pending_calls_race (test.test_concurrent_futures.ThreadPoolWaitTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_concurrent_futures.py", line 71, in tearDown self.assertLess(dt, 60, "synchronization issue: test lasted too long") AssertionError: 152.02985382080078 not less than 60 : synchronization issue: test lasted too long ---------------------------------------------------------------------- That test also uses sys.setswitchinterval(1e-6). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15599> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
