[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

STINNER Victor added the comment: > This is resolved with gh-12159, no? I was waiting to see if buildbot workers feel better. It's the case, so I close the issue. -- priority: release blocker -> normal resolution: -> fixed stage: -> resolved status: open -> closed

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Eric Snow added the comment: This is resolved with gh-12159, no? -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

STINNER Victor added the comment: test_mymanager and test_mymanager_context of test_multiprocessing_spawn.WithManagerTestMyManager failed in this build: > https://buildbot.python.org/all/#/builders/58/builds/1983/steps/3/logs/stdio ERROR: test_multiprocessing (test.test_venv.BasicTest)

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

STINNER Victor added the comment: > It's also possible that the child process is causing the segfault because of > misconfiguration (e.g. broken environment variables). Maybe, but the test also produces core dump on FreeBSD: bpo-36114. It looks more like a real bug. I set the priority

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Pablo Galindo Salgado added the comment: See also https://bugs.python.org/issue36114 -- ___ Python tracker ___ ___

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

STINNER Victor added the comment: https://buildbot.python.org/all/#/builders/32/builds/2219 FAIL: test_mymanager_context_prestarted (test.test_multiprocessing_spawn.WithManagerTestMyManager) Re-running failed tests in verbose mode Re-running test 'test_multiprocessing_spawn' in verbose mode

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Eryk Sun added the comment: > And depending on the OS, abort() calls (via Py_FatalError) sometimes > appear to be segfaults, so it could be any number of issues. > (Aside - I'd love to replace the abort() calls with specific exit > codes for configuration errors - they really mess up the

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Steve Dower added the comment: It's also possible that the child process is causing the segfault because of misconfiguration (e.g. broken environment variables). And depending on the OS, abort() calls (via Py_FatalError) sometimes appear to be segfaults, so it could be any number of issues.

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Pablo Galindo Salgado added the comment: Adding Łukasz, as I think this is a release blocker (the Windows 8 and 7 multiprocessing module may be causing segfaults). -- nosy: +lukasz.langa priority: normal -> high ___ Python tracker

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Pablo Galindo Salgado added the comment: It seems that return code 3221225477 in Windows is: #define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC005L) so this is a segfault in the manager. -- nosy: +pitrou ___ Python tracker

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

Pablo Galindo Salgado added the comment: It also fails on Windows 7: https://buildbot.python.org/all/#/builders/58/builds/1983/steps/3/logs/stdio -- ___ Python tracker ___

[issue36116] test_multiprocessing_spawn fails on AMD64 Windows8 3.x

New submission from Pablo Galindo Salgado : test test_multiprocessing_spawn failed test_import (test.test_multiprocessing_spawn._TestImportStar) ... ok == FAIL: test_mymanager_context