Maven test is being killed #2109

tnachen opened this Issue Mar 26, 2014 · 5 comments


None yet
3 participants

tnachen commented Mar 26, 2014

Our Travis CI setup in is failing everytime where one of the test ran through maven shows it being killed:

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.838 sec - in org.apache.drill.exec.physical.impl.TestDistributedFragmentRun
Running org.apache.drill.exec.physical.impl.TestHashToRandomExchange

We're guessing that there is some memory limit that it is hitting?

I wonder if this is seen anywhere else, or if it is memory problem any way to increase the ulimit for CI.


roidrage commented Mar 26, 2014

Memory limits are very likely in this case.

How much memory is consumed in this test suite when running locally?

tnachen commented Mar 26, 2014

Hi @BanzaiMan I'm referring to builds like this:

I think we need about 7-8GB of memory to run our tests, does Travis VM provide us knobs for that?


roidrage commented Mar 26, 2014

Sorry, 3GB is our limit currently.

tnachen commented Mar 26, 2014

Gotcha, we'll have to figure out something else then.


BanzaiMan closed this Mar 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment