[issue29589] test_asyncio & test_multiprocessing_forkserver failed

STINNER Victor added the comment: For the test_asyncio.test_stdin_broken_pipe() failure: see bpo-33531. For the test_multiprocessing_forkserver.test_ignore() failure: see bpo-33532. -- nosy: +vstinner ___ Python tracker

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

Xiang Zhang added the comment: Hmm, it seems not Python's fault. I can't reproduce the failure either. So I am going to close this issue. -- resolution: -> works for me stage: test needed -> resolved status: open -> closed ___ Python tracker

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

Louie Lu added the comment: Both test_asyncio & test_multiprocessing_forkserver passed on latest 3.6 and 4.8.3-1-ARCH. -- nosy: +louielu ___ Python tracker

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

Marcel Widjaja added the comment: Both test_asyncio & test_multiprocessing_forkserver work for me. I'm on the latest 3.6 and Mac OS 10.11.6 -- nosy: +mawidjaj ___ Python tracker

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

Dima Zhukov added the comment: Just tried with 3.4.6 version. Same test failed -- ___ Python tracker ___ ___

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

Xiang Zhang added the comment: Hi Dima, can you stably reproduce the failures? Or try with the latest 3.6 code? -- nosy: +xiang.zhang stage: -> test needed ___ Python tracker

[issue29589] test_asyncio & test_multiprocessing_forkserver failed

New submission from Dima Zhukov: Hi, i'm new to Python. Just have downloded source code and tried to install it, but "make test" failed 2 test: test_asyncio and test_multiprocessing_forkserver. How bad is it and what should i do? Logs attached -- components: Build files: