summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_timeout.py
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2003-02-21 16:45:41 (GMT)
committerTim Peters <tim.peters@gmail.com>2003-02-21 16:45:41 (GMT)
commit14821c59147228d45e3b6f828e7188a4075fa9cb (patch)
tree83c77b5e9209fcd41e99cbfd1d48f74136d88114 /Lib/test/test_timeout.py
parentd7c17237420e68e298aa549fb671ad17d6afebc1 (diff)
downloadcpython-14821c59147228d45e3b6f828e7188a4075fa9cb.zip
cpython-14821c59147228d45e3b6f828e7188a4075fa9cb.tar.gz
cpython-14821c59147228d45e3b6f828e7188a4075fa9cb.tar.bz2
Doubled TimeoutTestCase.fuzz, to slash the frequency of bogus failures
on the boxes I use.
Diffstat (limited to 'Lib/test/test_timeout.py')
-rw-r--r--Lib/test/test_timeout.py8
1 files changed, 7 insertions, 1 deletions
diff --git a/Lib/test/test_timeout.py b/Lib/test/test_timeout.py
index 6510ca9..5949e51 100644
--- a/Lib/test/test_timeout.py
+++ b/Lib/test/test_timeout.py
@@ -87,7 +87,13 @@ class CreationTestCase(unittest.TestCase):
class TimeoutTestCase(unittest.TestCase):
"""Test case for socket.socket() timeout functions"""
- fuzz = 1.0
+ # There are a number of tests here trying to make sure that an operation
+ # doesn't take too much longer than expected. But competing machine
+ # activity makes it inevitable that such tests will fail at times.
+ # When fuzz was at 1.0, I (tim) routinely saw bogus failures on Win2K
+ # and Win98SE. Boosting it to 2.0 helped a lot, but isn't a real
+ # solution.
+ fuzz = 2.0
def setUp(self):
self.sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)