summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_fork1.py
Commit message (Collapse)AuthorAgeFilesLines
* Restore rev 47014:Neal Norwitz2006-07-071-1/+9
| | | | | | | | | | | | | | | | The hppa ubuntu box sometimes hangs forever in these tests. My guess is that the wait is failing for some reason. Use WNOHANG, so we won't wait until the buildbot kills the test suite. I haven't been able to reproduce the failure, so I'm not sure if this will help or not. Hopefully, this change will cause the test to fail, rather than hang. That will be better since we will get the rest of the test results. It may also help us debug the real problem. *** The reason this originally failed was because there were many zombie children outstanding before rev 47158 cleaned them up. There are still hangs in test_subprocess that need to be addressed, but that will take more work. This should close some holes.
* Add new utility function, reap_children(), to test_support. This shouldNeal Norwitz2006-06-291-1/+2
| | | | | | | | | | be called at the end of each test that spawns children (perhaps it should be called from regrtest instead?). This will hopefully prevent some of the unexplained failures in the buildbots (hppa and alpha) during tests that spawn children. The problems were not reproducible. There were many zombies that remained at the end of several tests. In the worst case, this shouldn't cause any more problems, though it may not help either. Time will tell.
* Revert 47014 until it is more robustNeal Norwitz2006-06-181-9/+1
|
* The hppa ubuntu box sometimes hangs forever in these tests. My guessNeal Norwitz2006-06-181-1/+9
| | | | | | | | | | is that the wait is failing for some reason. Use WNOHANG, so we won't wait until the buildbot kills the test suite. I haven't been able to reproduce the failure, so I'm not sure if this will help or not. Hopefully, this change will cause the test to fail, rather than hang. That will be better since we will get the rest of the test results. It may also help us debug the real problem.
* Patch #1309579: wait3 and wait4 were added to the posix module by Chad J. ↵Neal Norwitz2006-03-201-64/+12
| | | | | | | | Schroeder. This was a fair amount of rework of the patch. Refactored test_fork1 so it could be reused by the new tests for wait3/4. Also made them into new style unittests (derive from unittest.TestCase).
* Oops, missed an import of test_support.Barry Warsaw2002-07-231-1/+1
|
* Unixware 7 support by Billy G. Allie (SF patch 413011)Guido van Rossum2001-04-111-1/+4
|
* Checking in patch #103478 -- makes popen2 and fork1 tested on BeOS.Moshe Zadka2001-01-301-9/+2
| | | | Tested for not breaking builds on Linux.
* This patch removes all uses of "assert" in the regression test suiteMarc-André Lemburg2001-01-171-4/+5
| | | | | | | and replaces them with a new API verify(). As a result the regression suite will also perform its tests in optimization mode. Written by Marc-Andre Lemburg. Copyright assigned to Guido van Rossum.
* Chris Herborth <chrish@pobox.com>:Fred Drake2000-08-151-0/+9
| | | | | | | | | Minor updates for BeOS R5. Use of OSError in test.test_fork1 changed to TestSkipped, with corresponding change in BeOS/README (by Fred). This closes SourceForge patch #100978.
* Raise 'TestSkipped' (from the test_support) module rather than 'ImportError'Thomas Wouters2000-08-041-1/+2
| | | | | to signify a test that should be marked as 'skipped' rather than 'failed'. Also 'document' it, in README.
* Raise ImportError when os.fork does not exist.Guido van Rossum2000-05-041-0/+5
|
* Added a provision to stop all threads before exiting from the test:Guido van Rossum2000-04-241-1/+7
| | | | | | the change to regrtest.py to unload all newly imported modules did something bad to the threads -- and I realized that they would never stop!
* Use a constant to specify the number of child threads to create.Fred Drake2000-04-101-4/+7
| | | | | | | | | | | Instead of assuming that the number process ids of the threads is the same as the process id of the controlling process, use a copy of the dictionary and check for changes in the process ids of the threads from the thread's process ids in the parent process. This makes the test make more sense on systems which assign a new pid to each thread (i.e., Linux). This doesn't fix the other problems evident with this test on Linux.
* Test case for fork1() behavior.Guido van Rossum2000-02-251-0/+54
Only the main thread should survive in the child after a fork().
generated by cgit v0.12 at 2024-11-24 20:27:06 (GMT)