如何摆脱“以退出代码139完成的过程(被信号11中断:SIGSEGV)".在Pychar + Django中 [英] How To Get Rid Of "Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)" in Pychar+Django

查看:123
本文介绍了如何摆脱“以退出代码139完成的过程(被信号11中断:SIGSEGV)".在Pychar + Django中的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我在本地计算机上使用pycharm为django应用运行测试套件时,在某些测试下,我得到了:

When I run my test suite using pycharm for a django app in my local machine, at certain test I got:

进程结束,退出代码为139(信号11:SIGSEGV中断)

如果我使用pycharm单独运行该测试,那么它将成功,这意味着该应用程序或测试中没有问题.如果我禁用了该特定测试,那么在另一项测试中,我会得到相同的错误,这是一个虚拟测试!这似乎表明pycharm本身存在问题.完整的测试套件可在CI环境中成功.

If I run that test in isolation using pycharm, it succeeds, which means there's not a problem in the app or test. If I disable that particular test, down the line I get the same error, in a different test, this one a dummy test! This seems to indicate that it's a problem with pycharm itself. The full test suite succeeds in the CI environment.

我尝试了其他其他stackoverflow问题的建议,但并没有解决问题:

I tried some suggestion from other stackoverflow questions, which didn't solve the issue:

  • Unticking the Qt box in PyCharm Settings (Build, Ex... -> Python Debugger)
  • Uninstalling python3-pyqt5 (same link as above): Pyqt is not installed in my local machine.
  • Ticking gevent compatible in Pycharm Settings

我的环境:python 3.7.3,djando 2.2.8,Pycharm 2019.2.4(专业版)

My Environment: python 3.7.3, djando 2.2.8, Pycharm 2019.2.4 (professional edition)

推荐答案

最后,我解决了.此条目为我提供了线索.这不是pycharm问题,而是python本身的错误.我发现运行flake8本身失败时.

Finally, I solve it. This entry gave me the clue. It wasn't a pycharm issue, but a bug in python itself. I discovered when running flake8 itself failed.

我在ubuntu中使用python 3.7.3,似乎有SIGSEGV错误(地址边界错误).升级到python 3.7.5之后,此问题已解决.

I was using python 3.7.3 in ubuntu, which seems to have have SIGSEGV Error (Address boundary error). After upgrading to python 3.7.5, the issue was fixed.

这篇关于如何摆脱“以退出代码139完成的过程(被信号11中断:SIGSEGV)".在Pychar + Django中的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆