预期集成测试在traivs CI中失败,但在本地成功运行

时间:2016-12-07 08:19:01

标签: travis-ci

我的集成测试会启动多个流程。我可以在本地运行集成测试,但是当我将它移动到travis时,集成测试将失败。以下是我看到的错误消息。我没有找到任何有用的信息,它似乎不是由我的集成测试引起的,而是由外部世界引起的(可能是环境问题)。我还使用此处的说明在本地成功运行了travis。 https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image

我看到错误

 INFO [2016-12-06 14:36:02,147] ({main} LivyInterpreterIT.java[onUpdate]:303) - onUpdate:
DEBUG [2016-12-06 14:36:02,148] ({main} LivyHelper.java[executeHTTP]:346) - Call rest api in http://testing-docker-ca2e7f34-da95-4627-bc72-7e92273f5758:8998/sessions/0/statements, method: POST, jsonData: {"code": "sqlContext.sql(\"show tables\").show(100)"}
DEBUG [2016-12-06 14:36:03,274] ({main} LivyHelper.java[executeHTTP]:346) - Call rest api in http://testing-docker-ca2e7f34-da95-4627-bc72-7e92273f5758:8998/sessions/0/statements/4, method: GET, jsonData: null
DEBUG [2016-12-06 14:36:03,392] ({main} LivyHelper.java[getStatusById]:323) - statement 4 response: {"id":4,"state":"running","output":null}
DEBUG [2016-12-06 14:36:04,392] ({main} LivyHelper.java[executeHTTP]:346) - Call rest api in http://testing-docker-ca2e7f34-da95-4627-bc72-7e92273f5758:8998/sessions/0/statements/4, method: GET, jsonData: null
DEBUG [2016-12-06 14:36:04,528] ({main} LivyHelper.java[getStatusById]:323) - statement 4 response: {"id":4,"state":"running","output":null}
DEBUG [2016-12-06 14:36:05,529] ({main} LivyHelper.java[executeHTTP]:346) - Call rest api in http://testing-docker-ca2e7f34-da95-4627-bc72-7e92273f5758:8998/sessions/0/statements/4, method: GET, jsonData: null
/home/travis/build.sh: line 57:  6800 Killed                  mvn $TEST_FLAG $PROFILE -B $TEST_PROJECTS


The command "mvn $TEST_FLAG $PROFILE -B $TEST_PROJECTS" exited with 137.
store build cache

change detected (content changed, file is created, or file is deleted):
/home/travis/.m2/repository/org/jsoup/jsoup/1.9.3-SNAPSHOT/resolver-status.properties
/home/travis/.m2/repository/org/jsoup/jsoup/resolver-status.properties


changes detected, packing new archive

1 个答案:

答案 0 :(得分:1)

错误137表示外界难以杀死(kill 9)。通常这意味着内存不足。

除了修复memopry情况之外,如果您的测试使用sudo: false,则可以尝试sudo: required。你的过程会有更多的记忆。