testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed FAILED/PASSEDSegmentation fault

testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed から始め、リンクされた Debian レポートとビルドログをコンテキストとして使用して、失敗を繰り返し再現します。完了の条件は、remote-killed のケースが一貫して動作し、セグメンテーションフォルトを起こさずに waitclose から EOFError を、channel.send から IOError を発生させることです。

• Bitbucket: https://bitbucket.org/hpk42/execnet/issue/53
• Originally reported by: @danstender
• Originally created at: 2017-03-19T18:17:04.424

We've got this test failure here on the Debian package. It appears randomly (however, oftenly), so it's hard to tell what triggers this, nor how to successfully reproduce it.

=================================== FAILURES ===================================
_______________ TestPopenGateway.test_waitclose_on_remote_killed _______________

self = <test_gateway.TestPopenGateway object at 0x7fbe7777a518>
makegateway = <bound method Group.makegateway of <Group ['gw0']>>

    def test_waitclose_on_remote_killed(self, makegateway):
        gw = makegateway('popen')
        channel = gw.remote_exec("""
                import os
                import time
                channel.send(os.getpid())
                time.sleep(100)
            """)
        remotepid = channel.receive()
        py.process.kill(remotepid)
        py.test.raises(EOFError, "channel.waitclose(TESTTIMEOUT)")
>       py.test.raises(IOError, channel.send, None)
E       Failed: DID NOT RAISE <class 'OSError'>

testing/test_gateway.py:251: Failed

Anyway, any hint on this or a fix would be very welcome.
The corresponding bug report is https://bugs.debian.org/854494, please see there for moreinfo and buildlogs.
DS