➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients brett.cannon, pitrou, skrah, vstinner
Date 2012-09-02.18:02:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346608968.18.0.068431661924.issue15599@psf.upfronthosting.co.za>
In-reply-to
Content 
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).
History
Date User Action Args
2012-09-02 18:02:48skrahsetrecipients: + skrah, brett.cannon, pitrou, vstinner
2012-09-02 18:02:48skrahsetmessageid: <1346608968.18.0.068431661924.issue15599@psf.upfronthosting.co.za>
2012-09-02 18:02:47skrahlinkissue15599 messages
2012-09-02 18:02:47skrahcreate