summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_timeout.py
Commit message (Collapse)AuthorAgeFilesLines
* fix a poorly worded error messageAnthony Baxter2004-06-111-1/+1
|
* Combine the functionality of test_support.run_unittest()Walter Dörwald2003-05-011-4/+1
| | | | | | | | | | and test_support.run_classtests() into run_unittest() and use it wherever possible. Also don't use "from test.test_support import ...", but "from test import test_support" in a few spots. From SF patch #662807.
* Avoid creating one of the TestSuite objects.Fred Drake2003-04-111-2/+1
|
* Fix SF bugs #692951 and 692988, test_timeout.py needs 'network' resourceNeal Norwitz2003-02-281-0/+5
| | | | | require -u network to run test_timeout since it fails when not connected to a network.
* Doubled TimeoutTestCase.fuzz, to slash the frequency of bogus failuresTim Peters2003-02-211-1/+7
| | | | on the boxes I use.
* Actually run these tests from regrtest.py.Neal Norwitz2003-02-171-2/+2
| | | | | | There was no test_main() and the main body was protected by if __name__ == '__main__' so the test didn't happen on import either.
* testConnectTimeout(): set the timeout to a smaller value; 0.02Guido van Rossum2002-09-031-1/+1
| | | | sometimes wasn't short enough.
* Standardize behavior: no docstrings in test functions.Guido van Rossum2002-08-221-14/+14
|
* Get rid of relative imports in all unittests. Now anything thatBarry Warsaw2002-07-231-1/+1
| | | | | | | | | | | imports e.g. test_support must do so using an absolute package name such as "import test.test_support" or "from test import test_support". This also updates the README in Lib/test, and gets rid of the duplicate data dirctory in Lib/test/data (replaced by Lib/email/test/data). Now Tim and Jack can have at it. :)
* Temporarily disable the timeout and socket tests.Guido van Rossum2002-06-131-2/+2
| | | | | | They still run as standalone scripts, but when used as part of the regression test suite, they are effectively no-ops. (This is done by renaming test_main to main.)
* Major overhaul of timeout sockets:Guido van Rossum2002-06-131-3/+3
| | | | | | | | | | | | | | | | | | | | - setblocking(0) and settimeout(0) are now equivalent, and ditto for setblocking(1) and settimeout(None). - Don't raise an exception from internal_select(); let the final call report the error (this means you will get an EAGAIN error instead of an ETIMEDOUT error -- I don't care). - Move the select to inside the Py_{BEGIN,END}_ALLOW_THREADS brackets, so other theads can run (this was a bug in the original code). - Redid the retry logic in connect() and connect_ex() to avoid masking errors. This probably doesn't work for Windows yet; I'll fix that next. It may also fail on other platforms, depending on what retrying a connect does; I need help with this. - Get rid of the retry logic in accept(). I don't think it was needed at all. But I may be wrong.
* Docstring, layout and style tweaking. Increase fuzz to 1 second.Guido van Rossum2002-06-121-90/+87
|
* Add some more basic tests to validate the argument checking ofGuido van Rossum2002-06-121-1/+51
| | | | | settimeout(), test settimeout(None), and the interaction between settimeout() and setblocking().
* New test suite for the socket module by Michael Gilfix.Guido van Rossum2002-06-121-12/+14
| | | | Changed test_timeout.py to conform to the guidelines in Lib/test/README.
* SF patch 555085 (timeout socket implementation) by Michael Gilfix.Guido van Rossum2002-06-061-0/+136
I've made considerable changes to Michael's code, specifically to use the select() system call directly and to store the timeout as a C double instead of a Python object; internally, -1.0 (or anything negative) represents the None from the API. I'm not 100% sure that all corner cases are covered correctly, so please keep an eye on this. Next I'm going to try it Windows before Tim complains. No way is this a bugfix candidate. :-)
generated by cgit v0.12 at 2024-10-22 00:40:49 (GMT)