[
https://issues.apache.org/jira/browse/BUILDS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284174#comment-14284174
]
Andrew Bayer commented on BUILDS-49:
------------------------------------
Duh - my brain had not started yet. =) So my guess here is just that having two
different large-scale Java builds running on the host at the same time is just
chewing up a lot of RAM. Annoying, but not sure we can do much.
> Surefire runner JVMs are being killed for HBase 0.98 Jenkins jobs
> -----------------------------------------------------------------
>
> Key: BUILDS-49
> URL: https://issues.apache.org/jira/browse/BUILDS-49
> Project: Infra Build Platform
> Issue Type: Bug
> Components: Jenkins
> Reporter: Andrew Purtell
> Assignee: Andrew Bayer
>
> Occasionally the JVMs executing forked runners from Surefire are being
> killed, failing HBase-0.98 Jenkins jobs.
> For example, see https://builds.apache.org/job/HBase-0.98/794:
> {noformat}
> Running org.apache.hadoop.hbase.security.access.TestCellACLs
> Running org.apache.hadoop.hbase.security.access.TestAccessController
> Killed
> Killed
> {noformat}
> or https://builds.apache.org/job/HBase-0.98/797/
> {noformat}
> Running org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient
> Running org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient
> Killed
> Killed
> {noformat}
> Is there something we can do to avoid this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
