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

Question

我的集成测试将启动多个进程。我可以在本地运行集成测试，但是当我将它移动到travis时，集成测试将失败。以下是我看到的错误消息。我没有找到任何有用的信息，它似乎不是由我的集成测试引起的，而是由外部世界引起的（也许是环境问题）。我也通过使用这里的指令在本地成功运行了travis。 https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image

错误我看到外面的世界（一个kill 9）杀死硬

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 

Answer 1

错误137的手段。通常这意味着内存不足。

除了修复memopry的情况，如果您的测试运行在sudo: false，您可以尝试sudo: required。你会为你的过程留下更多的记忆。