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 neologix
Recipients Arfrever, lemburg, neologix, python-dev, vstinner
Date 2012-04-29.09:02:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335690171.59.0.34599291923.issue14428@psf.upfronthosting.co.za>
In-reply-to
Content
test_process_time_threads is failing on one of the buildbots:
"""
======================================================================
FAIL: test_process_time_threads (test.test_time.TimeTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/buildbot/buildarea/3.x.warsaw-ubuntu-arm/build/Lib/test/test_time.py", line 408, in test_process_time_threads
    self.assertGreater(t2 - t1, 0.1)
AssertionError: 0.08041412500006118 not greater than 0.1
"""

The test is a bit too optimistic: a thread is looping for 0.2s, and the test checks that the process time (user + system) increased of at least 0.1s. If the thread is preempted, there's a high chance you won't get even as low as 0.1s.
I see two options: either increase the total running time, to make it really likely you'll get a chance to run (or decrase the lower threshold), or use times(2), and check the result against that (does Windows have such a syscall?).
History
Date User Action Args
2012-04-29 09:02:51neologixsetrecipients: + neologix, lemburg, vstinner, Arfrever, python-dev
2012-04-29 09:02:51neologixsetmessageid: <1335690171.59.0.34599291923.issue14428@psf.upfronthosting.co.za>
2012-04-29 09:02:51neologixlinkissue14428 messages
2012-04-29 09:02:50neologixcreate