Re-establish no nailguns under TravisCI.
Review Request #2065 - Created April 11, 2015 and submitted
|benjyw, dturner-tw, stuhood|
We used to have a switch for this in the ci.sh script that .travis.yml passed but that went away here: https://rbcommons.com/s/twitter/r/1852/ This just adds a config override file dedicated to TravisCI runs. .travis.yml | 1 + pants.travis-ci.ini | 5 +++++ 2 files changed, 6 insertions(+)
CI went green here: https://travis-ci.org/pantsbuild/pants/builds/58106974
Doing this in the course of tracking down shading errors (return code -9 which should mean the jvm was killed with SIGKILL IIUC) under TravisCI. Benjy, David and I have seen these on branch PRs and they occur intermittently both in the course of shading junit-runner and in the BootstrapJvmToolsTest. It seems to me having nailguns off under CI on these containers is the right thing to do regardless of the shading issue being related or not.
I have been seeing orphaned processes left running at 100% cpu after tests exited abnormally this weekend. I know there was a recent change that went in that affected shutdown https://rbcommons.com/s/twitter/r/2024/ but I didn't want to pin it on that without more proof.