| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
test_support.is_resource_enabled.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
specified. Fixes #1124637
|
|
|
|
| |
stdin/stdout/stderr redirected.
|
| |
|
|
|
|
| |
slightly modified.
|
|
|
|
| |
In test_args_string, remove the tempfile before assertEqual.
|
|
|
|
| |
TEMP dirs with {memb} strings. Fixes #1063571.
|
|
|
|
|
| |
know that the newly-started Python process only has 3 filedescriptors
open. Fixes bug 1048808.
|
|
|
|
|
| |
this test failed under the combination of passing -O to a debug-build
Python. Now all 4 of those pass ({debug, release} x {-O, no -O}).
|
|
|
|
| |
it's rather expensive to create new processes.
|
|
|
|
| |
"Khalid A. B." on python-dev)
|
|
|
|
|
| |
debug build on Windows now. More applications of the helper may be needed
on non-Windows platforms.
|
|
|
|
|
|
|
|
|
|
|
| |
Turns out the mysterious "expected output" file contained exactly N dots,
because test_poll() has a loop that *usually* went around N times,
printing one dot on each loop trip. But there's no guarantee of that,
because the exact value of N depended on the vagaries of scheduling
time.sleep()s across two different processes. So stopped printing dots,
and got rid of the expected output file. Add a loop counter instead,
and verify that the loop goes around at least a couple of times. Also
cut the minimum time needed for this test from 4 seconds to 1.
|
|
|
|
|
| |
of the test. It's testing stdout in a different process, so it has to
print something, but I didn't find "banana" to be self-explanatory.
|
|
|
|
|
|
| |
tester that a DOS box is expected to flash. Slash the sleep from 2
seconds to a quarter second (why would we want to wait 2 seconds just
to stare at a DOS box?).
|
|
|
|
|
|
| |
what this is trying to do. If it's necessary for it to create > 1000
processes, it should be controlled by a new resource and not run by
default on Windows.
|
|
|
|
|
|
| |
display a test's docstring as "the name" of the test. So changed most
test docstrings to comments, and removed the clearly useless ones. Now
unittest reports the actual names of the test methods.
|
| |
|
| |
|
|
|