[JIRA] (JENKINS-60618) Jenkins test harness InjectedTest hangs on machine with many cores since parent 3.55 upgrade

0 views
Skip to first unread message

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 1, 2020, 9:08:02 AM1/1/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Jenkins / Bug JENKINS-60618
Jenkins test harness InjectedTest hangs on machine with many cores since parent 3.55 upgrade
Change By: Mark Waite
Summary: Jenkins test harness InjectedTest hangs on machine with many cores since parent 3. 54 55 upgrade
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 1, 2020, 9:09:04 AM1/1/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
After upgrading to parent pom 3. 54 (and still with parent pom 3. 55 ) on a Ubuntu 16.04 server with 72 cores, the test suite in two three different plugins (platformlabeler-plugin , git-plugin, and git- client- plugin) hangs and never returns.  The last message reported from the CI job using an agent on that computer is "InjectedTest".  The same last message is visible when the tests are run with {{mvn clean verify}}.

The messages from platformlabeler-plugin look like this at the hang:

{noformat}
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskLsbReleaseTest
[INFO] Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.292 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskLsbReleaseTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskReleaseTest
[INFO] Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.097 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskReleaseTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskStaticStringTest
[INFO] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskStaticStringTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskTest
[INFO] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.893 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskTest
[INFO] Running InjectedTest
{noformat}

The same problem does not occur on an  8 core FreeBSD 11 machine or on 4 core or fewer machines running Ubuntu 16.04, Ubuntu 18.04, CentOS 7, CentOS 8, Debian 9, Debian 10, or Windows.

Setting the {{forkCount}} in pom.xml does not seem to change the behavior, since git-plugin has {{forkCount}} set to 1 (one test thread) and platformlabeler-plugin has {{forkCount}} set to 1C (one test thread per core on the machine).

The only workaround I've found has been to disable that agent during tests of those plugins.  That is unfortunate, since it is one of the fastest agents available to me.

The Jenkins test harness versions reported by {{mvn dependency:list}} are:

{noformat}
[INFO]    org.jenkins-ci.main:jenkins-test-harness:jar:2.57:test
[INFO]    org.jenkins-ci.main:jenkins-test-harness-htmlunit:jar:2.31-2:test
{noformat}

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 1, 2020, 9:10:02 AM1/1/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
After upgrading to parent pom 3.55 on a Ubuntu 16.04 server with 72 cores, the test suite in three different plugins (platformlabeler-plugin, git-plugin, and git-client-plugin) hangs and never returns.  The last message reported from the CI job using an agent on that computer is "InjectedTest".  The same last message is visible when the tests are run with {{mvn clean verify}}.


The messages from platformlabeler-plugin look like this at the hang:

{noformat}
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskLsbReleaseTest
[INFO] Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.292 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskLsbReleaseTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskReleaseTest
[INFO] Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.097 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskReleaseTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskStaticStringTest
[INFO] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskStaticStringTest
[INFO] Running org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskTest
[INFO] Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.893 s - in org.jvnet.hudson.plugins.platformlabeler.PlatformDetailsTaskTest
[INFO] Running InjectedTest
{noformat}

The same problem does not occur on an  8 core FreeBSD 11 machine or on 4 core or fewer machines running Ubuntu 16.04, Ubuntu 18.04, CentOS 7, CentOS 8, Debian 9, Debian 10, or Windows.

Setting the {{forkCount}} in pom.xml does not seem to change the behavior, since git-plugin has {{forkCount}} set to 1 (one test thread) and platformlabeler-plugin has {{forkCount}} set to 1C (one test thread per core on the machine).

The only workaround I've found has been to disable that agent during tests of those plugins.  That is unfortunate, since it is one of the fastest agents available to me.

The Jenkins test harness versions reported by {{mvn dependency:list}} are:

{noformat}
[INFO]    org.jenkins-ci.main:jenkins-test-harness:jar:2.57:test
[INFO]    org.jenkins-ci.main:jenkins-test-harness-htmlunit:jar:2.31-2:test
{noformat}


Issue was not seen in git client plugin with parent pom 3.54, only with 3.55.

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 1, 2020, 9:12:02 AM1/1/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
After upgrading to parent pom 3.55 on a Ubuntu 16.04 server with 72 cores, the test suite in three different plugins ( [ platformlabeler-plugin |https://github.com/jenkinsci/platformlabeler-plugin] , [ git-plugin |https://github.com/jenkinsci/git-plugin] , and [ git-client-plugin |https://github.com/jenkinsci/git-client-plugin] ) hangs and never returns.   

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 1, 2020, 9:13:02 AM1/1/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
Change By: Mark Waite
Environment: Ubuntu 16.04 computer with 72 cores ,
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09),
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 19, 2020, 9:59:02 PM1/19/20
to jenkinsc...@googlegroups.com

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 19, 2020, 9:59:03 PM1/19/20
to jenkinsc...@googlegroups.com
Mark Waite resolved as Duplicate
Change By: Mark Waite
Status: Open Resolved
Resolution: Duplicate
Released As: jenkins-test-harness 2.60
Reply all
Reply to author
Forward
0 new messages