[issue12625] sporadic test_unittest failure

STINNER Victor added the comment: > Is this test still failing? Or can this be closed? The OpenIndiana buildbot is gone for many years. See also bpo-42173. -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python

[issue12625] sporadic test_unittest failure

Irit Katriel added the comment: Is this test still failing? Or can this be closed? -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___

[issue12625] sporadic test_unittest failure

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12625] sporadic test_unittest failure

Mark Lawrence added the comment: Can this be closed as out of date? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12625 ___

[issue12625] sporadic test_unittest failure

STINNER Victor victor.stin...@haypocalc.com added the comment: getpid() is called after each kill(getpid(), signum), to force the signal delivery Please write a function (in test.support?) with a comment explaining why you are doing that. You may also only do this workaround on specific

[issue12625] sporadic test_unittest failure

Charles-François Natali neolo...@free.fr added the comment: Please write a function (in test.support?) with a comment explaining why you are doing that. You may also only do this workaround on specific platforms. For example, only on FreeBSD and OpenIndiana (the test would be in the

[issue12625] sporadic test_unittest failure

Charles-François Natali neolo...@free.fr added the comment: No, it's a feature of the new GIL. When I look at 2.7's code, I see something different - _Py_Ticker is reset in Py_AddPendingCall(): int Py_AddPendingCall(int (*func)(void *), void *arg) { [...] /* signal main loop */

[issue12625] sporadic test_unittest failure

New submission from Antoine Pitrou pit...@free.fr: Seen on an OpenIndiana buildbot: == FAIL: testInstallHandler (unittest.test.test_break.TestBreak) --

[issue12625] sporadic test_unittest failure

Charles-François Natali neolo...@free.fr added the comment: Looks similar to issue #8263, which is in turn similar to #12469 (see http://bugs.python.org/issue12469#msg139620 and http://bugs.python.org/issue12469#msg139626 for original explanations): normally, pending signals are checked when

[issue12625] sporadic test_unittest failure

Charles-François Natali neolo...@free.fr added the comment: So I'd say the easier solution is to skip this test on OpenSolaris, like it's done on FreeBSD6 since issue #8263. Another option could be to add a dummy syscall, like os.getpid(), before checking that the handler got called - this

[issue12625] sporadic test_unittest failure

Antoine Pitrou pit...@free.fr added the comment: Note that this kind of test assumes that the Python signal handler is called right after the signal is delivered, i.e. every time from the main eval loop (I think that's true with recent Python versions, is that true with 2.7?). No, it's a