-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Ubuntu 16.04 computer with 72 cores,
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09),
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
-
-
jenkins-test-harness 2.60
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:
[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
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:
[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
Issue was not seen in git client plugin with parent pom 3.54, only with 3.55.
- duplicates
-
-
- Closed
-
[JENKINS-60618] Jenkins test harness InjectedTest hangs on machine with many cores since parent 3.55 upgrade
| Description |
Original:
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 different plugins (platformlabeler-plugin and git-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 18.04, CentOS 7, CentOS 8, Debian 9, Debian 10, and 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 1T (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} |
New:
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 different plugins (platformlabeler-plugin and git-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 1T (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} |
| Assignee | Original: Oliver Gondža [ olivergondza ] | New: Mark Waite [ markewaite ] |
| Assignee | Original: Mark Waite [ markewaite ] | New: Oliver Gondža [ olivergondza ] |
| Description |
Original:
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 different plugins (platformlabeler-plugin and git-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 1T (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} |
New:
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 different plugins (platformlabeler-plugin and git-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} |
| Summary | Original: Jenkins test harness InjectedTest hangs on machine with many cores since parent 3.54 upgrade | New: Jenkins test harness InjectedTest hangs on machine with many cores since parent 3.55 upgrade |
| Description |
Original:
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 different plugins (platformlabeler-plugin and git-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} |
New:
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} |
| Description |
Original:
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} |
New:
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. |
| Description |
Original:
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. |
New:
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. 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. |
| Environment | Original: Ubuntu 16.04 computer with 72 cores |
New:
Ubuntu 16.04 computer with 72 cores, OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09), Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) |