hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18712) Specify MaxPermSize for surefire tests
Date Tue, 29 Aug 2017 04:32:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144726#comment-16144726

stack commented on HBASE-18712:

bq. https://builds.apache.org/job/PreCommit-HBASE-Build/833/artifact/patchprocess/patch-unit-hbase-server-jdk1.7.0_79.txt

The build is gone. Was it precommit for master branch?

bq. For JDK 1.8, -XX:-UseLoopPredicate should be used, as indicated by the post in description.

>From bug db, "Bug 406419 - Don't use -XX:-UseLoopPredicate"; says not needed since the
original prob was fixed.

> Specify MaxPermSize for surefire tests
> --------------------------------------
>                 Key: HBASE-18712
>                 URL: https://issues.apache.org/jira/browse/HBASE-18712
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 18712.v1.txt, 18712.v2.txt
> Currently hbase-surefire.argLine doesn't specify MaxPermSize for the test run(s).
> This sometimes resulted in mvn build prematurely exiting, leaving some large tests behind.
> The tests would be deemed timed out.
> As indicated by the following post:
> https://stackoverflow.com/questions/23260057/the-forked-vm-terminated-without-saying-properly-goodbye-vm-crash-or-system-exi
> We should specify large enough MaxPermSize so that mvn build doesn't end prematurely.

This message was sent by Atlassian JIRA

View raw message