[
https://issues.apache.org/jira/browse/HUDI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961014#comment-16961014
]
leesf commented on HUDI-312:
----------------------------
For vm crashes, the following information is useful.
https://stackoverflow.com/questions/23260057/the-forked-vm-terminated-without-saying-properly-goodbye-vm-crash-or-system-exi.
I added <argLine>-Xmx1024m -XX:MaxPermSize=256m</argLine> to surefire plugin
configuration(https://github.com/leesf/incubator-hudi/commit/d2b26650fc921666761d816b721cea22307bf884)
and build it many times in travis
(https://travis-ci.org/leesf/incubator-hudi/builds/603810854), the vm did not
crash again. [~vinoth]
> Investigate recent flaky CI runs
> --------------------------------
>
> Key: HUDI-312
> URL: https://issues.apache.org/jira/browse/HUDI-312
> Project: Apache Hudi (incubating)
> Issue Type: New Feature
> Components: Testing
> Reporter: Vinoth Chandar
> Priority: Major
> Fix For: 0.5.1
>
> Attachments: Builds - apache_incubator-hudi - Travis CI.pdf
>
>
> master used to be solid green. noticing that nowadays PRs and even some
> master merges fail with
> - No output received for 10m
> - Exceeded runtime of 50m
> - VM exit crash
> We saw this earlier in the year as well. It was due to the apache org queue
> in travis being busy/stressed. I think we should shadow azure CI or circle CI
> parallely and weed out code vs environment issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
