A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-March/138952.html below:

[Python-Dev] Sporadic failures of test_subprocess and test_multiprocessing_spawn

[Python-Dev] Sporadic failures of test_subprocess and test_multiprocessing_spawn [Python-Dev] Sporadic failures of test_subprocess and test_multiprocessing_spawnVictor Stinner victor.stinner at gmail.com
Mon Mar 30 02:31:45 CEST 2015
Hi Serhiy,

2015-03-28 17:40 GMT+01:00 Serhiy Storchaka <storchaka at gmail.com>:
> Just run tests with low memory limit.
>
> (ulimit -v 60000; ./python -m test.regrtest -uall -v
> test_multiprocessing_spawn;)
>
> test_io also hangs.

I confirm that some tests using threads hang under very low memory
condition. At bootstrap, Python doesn't handle correctly all
exceptions when starting a new thread. The "parent thread" waits until
the "child thread" completes, which never occurs because the thread
already completed.

I don't think that it was my regression, it probably exists since
Python 2 and maybe before. I'm not interested to touch this fragile
part of Python. It's maybe easy to fix the issue, I don't know.

Victor
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4