Re: Build failure on 0.13.SNAPSHOT

Oh, it seems like apache mailing server ate the attached image as Gian said; here is the table: total usedfree shared buff/cacheavailable Mem: 7704 6147 122 161 1435 1123 Swap: 4095 16672428 Frankly, this result is not accurate; since I

Re: Build failure on 0.13.SNAPSHOT

@Dongjin, thank you for looking into this. I got some follow-up questions. > Druid uses above 8gb of memory for testing. How did you get this result? Did you use some tools to get the memory usage of only the maven process for Druid tests? When I checked last time using JMC, I could see that

Re: Build failure on 0.13.SNAPSHOT

OOME seems to be showing up in some of the Travis testing as well for group by related stuff. Unsure what's going on there. On Tue, Jul 24, 2018 at 9:46 PM Dongjin Lee wrote: > After some experiments, I figured out the following: > > 1. Druid uses above 8gb of memory for testing.

Re: Build failure on 0.13.SNAPSHOT

Hi Dongjin, Thanks for doing this research. I don't see building-druid.png attached to your mail -- maybe the ASF mailing list ate it? Please do send in a pull request to update the documentation. Fwiw I think 8GB should be enough memory with the right settings, since our Travis CI build

Re: Build failure on 0.13.SNAPSHOT

After some experiments, I figured out the following: 1. Druid uses above 8gb of memory for testing. (building-druid.png) 2. With 8gb(physical)+4gb(swap) of memory, the test succeeds regardless of maven version (3.3.9, 3.5.2, 3.5.4) or MAVEN_OPTS. However, with 8gb(physical)+2gb(swap) of

Re: Build failure on 0.13.SNAPSHOT

I'm also using Maven 3.5.2 and not using any special configurations for Maven, but I have never seen that error too. Most of our Travis jobs have been working with only 512 MB of direct memory. Only the 'strict compilation' Travis job requires 3 GB of memory. I think it's worthwhile to look into

Re: Build failure on 0.13.SNAPSHOT

Interesting. Fwiw, I am using Maven 3.5.2 for building Druid and it has been working for for me. I don't think I"m using any special Maven overrides (at least, I don't see anything interesting in my ~/.m2 directory or in my environment variables). It might have to do with how much memory our

Re: Build failure on 0.13.SNAPSHOT

Finally, it seems like I found the reason. It was a composition of several problems: - Druid should not be built with maven 3.5.x. With 3.5.2, Test suites like `GroupByQueryRunnerFailureTest` fails. After I switched into 3.3.9 which is built in the latest version of IntelliJ, those errors

Re: Build failure on 0.13.SNAPSHOT

Hi Dongjin, that is weird. It looks like the vm crashed because of out of memory while testing. It might be a real issue or not. Have you set any memory configuration for your maven? Jihoon On Thu, Jul 19, 2018 at 7:09 PM Dongjin Lee wrote: > Hi Jihoon, > > I ran `mvn clean package` following

Re: Build failure on 0.13.SNAPSHOT

Hi Jihoon, I ran `mvn clean package` following development/build . Dongjin On Fri, Jul 20, 2018 at 12:30 AM Jihoon Son wrote: > Hi Dongjin, > > what maven command did you run? > > Jihoon > > On Wed, Jul

Re: Build failure on 0.13.SNAPSHOT

Hi Dongjin, what maven command did you run? Jihoon On Wed, Jul 18, 2018 at 10:38 PM Dongjin Lee wrote: > Hello. I am trying to build druid, but it fails. My environment is like the > following: > > - CPU: Intel(R) Core(TM) i7-7560U CPU @ 2.40GHz > - RAM: 7704 MB > - OS: ubuntu 18.04 > - JDK:

Build failure on 0.13.SNAPSHOT

Hello. I am trying to build druid, but it fails. My environment is like the following: - CPU: Intel(R) Core(TM) i7-7560U CPU @ 2.40GHz - RAM: 7704 MB - OS: ubuntu 18.04 - JDK: openjdk version "1.8.0_171" (default configuration, with MaxHeapSize = 1928 MB) - Branch: master (commit: cd8ea3d) The