pytest-dev / pytest-dev/execnet
testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed FAILED/PASSEDSegmentation fault
未关闭
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 102
- 派生
- 47
- PR 合并指标
- 30 天内没有已合并 PR
描述
- 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
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 testing/test_gateway.py::TestPopenGateway::test_waitclose_on_remote_killed 开始,使用链接的 Debian 报告和构建日志作为背景,反复重现该故障。完成的标准是 remote-killed 情况表现一致,从 waitclose 引发 EOFError,并从 channel.send 引发 IOError,且不会发生 segmentation fault。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- distributed-systems, testing
- Issue 类型
- 缺陷
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100