homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients pablogsal, vstinner, xtreak
Date 2019年02月12日.19:39:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550000391.12.0.00100926773753.issue35978@roundup.psfhosted.org>
In-reply-to
Content
That looks like a similar example of the problem that bpo35378 solves. But the PR is merged and the test keeps failing:
test test_venv failed -- Traceback (most recent call last):
 File "/home/travis/build/python/cpython/Lib/test/test_venv.py", line 309, in test_multiprocessing
 out, err = check_output([envpy, '-c',
 File "/home/travis/build/python/cpython/Lib/test/test_venv.py", line 37, in check_output
 raise subprocess.CalledProcessError(
subprocess.CalledProcessError: Command '['/tmp/tmplplx90pf/bin/python', '-c', 'from multiprocessing import Pool; print(Pool(1).apply_async("Python".lower).get(3))']' died with <Signals.SIGABRT: 6>.
https://travis-ci.org/python/cpython/jobs/492305033
Running that command locally on master does not die with SIGABRT:
❯ ./python -c 'from multiprocessing import Pool; print(Pool(1).apply_async("Python".lower).get(3))'; echo $?
python
/home/pablogsal/github/cpython/Lib/multiprocessing/pool.py:234: ResourceWarning: unclosed running multiprocessing pool <multiprocessing.pool.Pool state=RUN pool_size=1>
 _warn(f"unclosed running multiprocessing pool {self!r}",
ResourceWarning: Enable tracemalloc to get the object allocation traceback
0
History
Date User Action Args
2019年02月12日 19:39:51pablogsalsetrecipients: + pablogsal, vstinner, xtreak
2019年02月12日 19:39:51pablogsalsetmessageid: <1550000391.12.0.00100926773753.issue35978@roundup.psfhosted.org>
2019年02月12日 19:39:51pablogsallinkissue35978 messages
2019年02月12日 19:39:51pablogsalcreate

AltStyle によって変換されたページ (->オリジナル) /