STINNER Victor <vstin...@python.org> added the comment:
> I don't think that's a segfault. That seems that the process was killed no? > Also, the buildbot is green so this is not happening in the latest builds * (1) 0:01:12, test_compile child process was killed by signal -9 * (2) 0:08:48, test_multiprocessing_forkserver child process was killed by signal -9 * (3) 0:27:56, test_compile main process was killed (unknown signal... I bet on signal -9, SIGSEGV) Maybe it was a manual action, but it sounds like a strange coincidence that 3 processes were killed in the same build, and it wasn't at the same time. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44360> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
