[
https://issues.apache.org/jira/browse/BUILDS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283721#comment-14283721
]
Robert Munteanu commented on BUILDS-49:
---------------------------------------
We see this as well from time to time in the Apache Sling builds. Here's a
sample:
* job: https://builds.apache.org/job/sling-trunk-1.8/637
* build slave: H10
* JVM: /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.8.0
* console output: https://builds.apache.org/job/sling-trunk-1.8/637/console
* log snippet:
{noformat}Running
org.apache.sling.launchpad.webapp.integrationtest.JsonRenderingTest
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.441 sec - in
org.apache.sling.launchpad.webapp.integrationtest.JsonRenderingTest
Running org.apache.sling.launchpad.webapp.integrationtest.SlingWebDavServletTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.293 sec - in
org.apache.sling.launchpad.webapp.integrationtest.SlingWebDavServletTest
Running org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.579 sec - in
org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest
Running org.apache.sling.launchpad.webapp.integrationtest.StreamServletTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.288 sec - in
org.apache.sling.launchpad.webapp.integrationtest.StreamServletTest
Running
org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
Killed
Results :
Tests run: 26, Failures: 0, Errors: 0, Skipped: 0{noformat}
Note the 'Killed' snippet, which indicates (to my knowledge) that the process
was killed externally. Given that we don't see this randomly for many projects,
I would say that it's not a rogue 'killall java', but something more targeted
like the OOM killer. Is there a way to check that? For us, it seems the build
was killed sometime after 20-01-2015 23:11:49 .
> 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)
