You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Valentyn Tymofieiev (JIRA)" <ji...@apache.org> on 2018/10/04 22:56:00 UTC
[jira] [Comment Edited] (BEAM-5243)
beam_Release_Gradle_NightlySnapshot InvocationError py27-cython/bin/python
setup.py nosetests
[ https://issues.apache.org/jira/browse/BEAM-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638998#comment-16638998 ]
Valentyn Tymofieiev edited comment on BEAM-5243 at 10/4/18 10:55 PM:
---------------------------------------------------------------------
[~swegner]
It seems that we are hit by this flake ~once per month, most recently in https://builds.apache.org/job/beam_Release_Gradle_NightlySnapshot/197/
The symptoms are that a test suite started by `python setup.py nosetests` is passing but then returns a non-zero exit code "-11", which we interpret as failure:
========================
Ran 1726 tests in 261.611s
OK (SKIP=324)
ERROR: InvocationError for command '/home/jenkins/jenkins-slave/workspace/beam_Release_Gradle_NightlySnapshot/src/sdks/python/target/.tox/py27/bin/python setup.py nosetests' (exited with code -11)
========================
Exit code -11 may in some cases be a segmentation fault as per Stackoverflow Search.
This may be an issue with "nose" package, or some side-effects of some of our tests.
I suggest following further investigations avenues:
- Try to reproduce this locally, in a virtual environment, that has nose package and Beam SDK installed via something like `for i in `seq 100`; do python setup.py nosetests || echo "Last exit code was $?"; done`.
- See if the tests that we are running make a difference whether the error appears.
- See if versions of nose makes a difference.
- Reach out to nose maintainers.
was (Author: tvalentyn):
[~swegner]
It seems that we are hit by this flake ~once per month, most recently in https://builds.apache.org/job/beam_Release_Gradle_NightlySnapshot/197/
The symptoms are that a test suite started by `python setup.py nosetests` is passing but then returns a non-zero exit code "-11", which we interpret as failure:
========================
Ran 1726 tests in 261.611s
OK (SKIP=324)
ERROR: InvocationError for command '/home/jenkins/jenkins-slave/workspace/beam_Release_Gradle_NightlySnapshot/src/sdks/python/target/.tox/py27/bin/python setup.py nosetests' (exited with code -11)
========================
Exit code -11 may in some cases be a segmentation fault as per Stackoverflow Search.
This may be an issue with "nose" package, or some side-effects of some of our tests.
I suggest following further investigations avenues:
- Try to reproduce this locally via something like `for i in `seq 100`; do python setup.py nosetests || echo "Last exit code was $?"; done`.
- See if the tests that we are running make a difference whether the error appears.
- See if versions of nose makes a difference.
- Reach out to nose maintainers.
> beam_Release_Gradle_NightlySnapshot InvocationError py27-cython/bin/python setup.py nosetests
> ---------------------------------------------------------------------------------------------
>
> Key: BEAM-5243
> URL: https://issues.apache.org/jira/browse/BEAM-5243
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Andrew Pilloud
> Assignee: Ahmet Altay
> Priority: Major
>
> It isn't clear to me what exactly failed, logs are full of stack traces.
> [https://builds.apache.org/job/beam_Release_Gradle_NightlySnapshot/151/]
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/5844/]
>
> *01:00:38* ERROR: InvocationError for command '/home/jenkins/jenkins-slave/workspace/beam_Release_Gradle_NightlySnapshot/src/sdks/python/target/.tox/py27-cython/bin/python setup.py nosetests' (exited with code -11)*01:00:38* ___________________________________ summary ____________________________________*01:00:38* ERROR: py27-cython: commands failed*01:00:38*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)