You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/06/14 19:53:01 UTC
[jira] [Commented] (BUILDS-49) Surefire runner JVMs are being
killed for HBase 0.98 Jenkins jobs
[ https://issues.apache.org/jira/browse/BUILDS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585156#comment-14585156 ]
Sean Busbey commented on BUILDS-49:
-----------------------------------
if these builds were happening in parallel, could it be the post-build zombie finder matching processes from other jobs?
> 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)