Hyukjin Kwon created SPARK-21189:
------------------------------------
Summary: Handle unknown error codes in Jenkins rather then leaving
incomplete comment in PRs
Key: SPARK-21189
URL: https://issues.apache.org/jira/browse/SPARK-21189
Project: Spark
Issue Type: Improvement
Components: Project Infra
Affects Versions: 2.2.0
Reporter: Hyukjin Kwon
Recently, Jenkins tests were unstable due to unknown reasons as below:
{code}
/home/jenkins/workspace/SparkPullRequestBuilder/dev/lint-r ; process was
terminated by signal 9
test_result_code, test_result_note = run_tests(tests_timeout)
File "./dev/run-tests-jenkins.py", line 140, in run_tests
test_result_note = ' * This patch **fails %s**.' %
failure_note_by_errcode[test_result_code]
KeyError: -9
{code}
{code}
Traceback (most recent call last):
File "./dev/run-tests-jenkins.py", line 226, in <module>
main()
File "./dev/run-tests-jenkins.py", line 213, in main
test_result_code, test_result_note = run_tests(tests_timeout)
File "./dev/run-tests-jenkins.py", line 140, in run_tests
test_result_note = ' * This patch **fails %s**.' %
failure_note_by_errcode[test_result_code]
KeyError: -10
{code}
This exception looks causing failing to update the comments in the PR. For
example:
{code}
Test build #78508 has started for PR 18320 at commit 53e00d7.
{code}
comment just remains.
This always requires, for both reviewers and the author, a overhead to click
and check the logs, which I believe are not really useful.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
