joohnnie commented on issue #546: [GRIFFIN-295]Limit the memory used by test case URL: https://github.com/apache/griffin/pull/546#issuecomment-548677470 HI @wankunde , First, you are right, there is a memory limit for the Travis container. As i mentioned in this PR https://github.com/apache/griffin/pull/543. I copied my testing result below I tried to build with the following Maven Options and they are running successfully. export MAVEN_OPTS="-Xms500m -Xmx1g -XX:MaxPermSize=512m https://travis-ci.org/joohnnie/griffin/builds/601486973 and export MAVEN_OPTS="-Xms256m -Xmx1g -XX:MaxPermSize=256m https://travis-ci.org/joohnnie/griffin/builds/601561953 Looks like there is memory limit for each travis CI JVM. This kind of constraint is related to the Travis CI container. IMO, I think it is a good practice to not put this kind of limitation to our code and POM configs if it can be solved by the travis config .travis.yml. To put it another way, if in the future we use other CI tools to replace Travis and there is no this kind of memory limitation, we need to change the config one more time to make it work on the new CI tools. Based on my experience, the Travis issues mainly related to the 2 constraints, - one is memory - the other one is No Log in 10 minutes/ or too much log to exceed the log size. That's why we need to carefully define the log level and memory. Thanks Johnnie
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
