[issue38842] test_multiprocessing_spawn altered the execution environment in AMD64 FreeBSD Non-Debug 3.x

[STINNER Victor]

STINNER Victor <vstinner at python.org> added the comment:

AMD64 RHEL7 3.8 was marked as failed because of:
https://buildbot.python.org/all/#/builders/279/builds/136

test_max_workers_too_large (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... skipped 'Windows-only process limit'
test_no_stale_references (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.57s ok
test_ressources_gced_in_workers (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 1.78s ok
test_shutdown_race_issue12456 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.42s
Warning -- reap_children() reaped child process 11860
ok

The test_concurrent_futures reap_children() issue is tracked as bpo-38546.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38842>
_______________________________________