[issue37516] buid error - test_asyncio fails during make

STINNER Victor added the comment: The issue title says "test_asyncio fails", but "Unknown child process pid 30234, will report returncode 255" looks more like a warning. Does test_asyncio fail or not? Please run test_asyncio in verbose mode to identify which test emits the warning.

[issue37516] buid error - test_asyncio fails during make

Change by Karthikeyan Singaravelan : -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tracker ___ ___

[issue37516] buid error - test_asyncio fails during make

Gordon R. Burgess added the comment: I got excited prematurely - this is farther down in the log on the second build: ... 0:16:09 load avg: 0.84 [341/423] test_sys_settrace unhandled exception during asyncio.run() shutdown task: ()> exception=RuntimeError("can't send non-None value to a

[issue37516] buid error - test_asyncio fails during make

Gordon R. Burgess added the comment: Ran this on a different laptop (Debian 9.9, Lenovo w540) and it passed, so (as I'd expect) this is an intermittent issue. (The ticket was opened with an error on a Lenovo w510) Both systems have been reimaged in the last 6-8 months. 0:00:34 load avg:

[issue37516] buid error - test_asyncio fails during make

New submission from Gordon R. Burgess : 0:02:03 load avg: 3.08 [ 26/423] test_asyncio Unknown child process pid 30234, will report returncode 255 Child watcher got an unexpected pid: 30234 Traceback (most recent call last): File