[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl resolved as Fixed Jenkins / JENKINS-55226 Deadlock while running tests Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196305.1545056354000.8140.1565041560197%40Atlassian.JIRA.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests I ran the PCT against the latest token-macro version and it ran fine. Can you confirm if you are seeing this issue still? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196305.1545056354000.12377.1563291240193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests I did a bit of debug today and made some changes. I'll try and run the ATH on this. https://github.com/jenkinsci/token-macro-plugin/commit/2df76372834a50b35f7124293fb9a7c4e60f7ca9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests If I update the Jenkins version in the pom, I see a hang as well. I am not sure why it is happening as the plugin runs fine in running instances for me that are much newer. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests https://github.com/jenkins-infra/pipeline-library/blob/master/vars/buildPlugin.groovy#L204 java.level is used for source code compatibility and feature enablement, not the version of the JDK that is being used to build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests I didn't think so, most probably I'm wrong. I thought it was using the java.level from the pom.xml. In this case, it probably means it's a problem of Jenkins core version.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests Isn't the plugin already only building on JDK 8? The buildPlugin() function uses JDK8 as the default if none is specified. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests I don't think it's related to the build server, even if I didn't test that. The problem is that, in the Pipeline related tests, the build is never actually run. It is triggered, started, but nothing happen. I have this even just by upgrading the Java version (and so Jenkins core requirement). If you could update the Jenkinsfile to build the plugin on Java 8 (for now only), it would be great. I can open a PR with the new Jenkinsfile but it wouldn't be used. Only you (write permission on the repo) can open such PR (update parent-pom to latest version at the same time). This way we could validate that if it's a problem of test environment (my computer) or if it's something wrong in the test description. Also, the versions of the Pipeline plugins used for the tests are a bit old. This might be the problem. I tried to update them and it didn't solve the problem. But again, "doesn't work on my machine" it not what we want here, right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests Adrien Lecharpentier Do you mean that there is an issue in the test environment as specified in the plugin, or on the build server? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests Alex Earl I tried to work a bit on this. It's not a deadlock and it's not only related to java 11. It is a test environment issue. If you update jenkins.version to 2.60.1, the Pipeline related tests simply timeout. You could check that by updating Jenkinsfile with buildPlugin( configurations: [ [ platform: "linux" ], [ platform: "windows" ], [ platform: "linux", jdk: "8", jenkins: "2.60.1", javaLevel: "8" ], [ platform: "windows", jdk: "8", jenkins: "2.60.1", javaLevel: "8" ] ] ) (or similar, just test with a newer version of Jenkins core) The tests are supposed to trigger a job and see the result of run. The run is triggered but it doesn't go any further: nothing is truly executed and the tests timeout. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests Don't hesitate to ping me if you need more details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests Adrien Lecharpentier I think this should work, thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier commented on JENKINS-55226 Re: Deadlock while running tests Alex Earl You are correct. Sorry I didn't at first. Is this detailed enough? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title
Adrien Lecharpentier updated an issue
Jenkins / JENKINS-55226
Deadlock while running tests
Change By:
Adrien Lecharpentier
While I was running {{token-macro}} against PCT and Jenkins {{2.155}}, I noticed that deadlocks are happening during the plugin tests.{noformat}[INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest[INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest=== Starting testException(org.jenkinsci.plugins.tokenmacro.PipelineTest) 0.084 [id=175] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:35227/jenkins/ 0.236 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 0.279 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 0.704 [id=181] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 0.713 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 0.716 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 0.719 [id=186] INFO h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component org.jenkinsci.plugins.workflow.steps.scm.SubversionStep$DescriptorImpl; skipping 1.234 [id=184] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 1.268 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 180.000 [id=1] WARNING o.j.hudson.test.JenkinsRule$2#evaluate: Test timed out (after 180 seconds). 180.049 [id=175] INFO jenkins.model.Jenkins#cleanUp: Stopping Jenkins"Executing testException(org.jenkinsci.plugins.tokenmacro.PipelineTest)" Id=175 Group=FailOnTimeoutGroup RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:783) - locked org.eclipse.jetty.util.MultiException@15d42ccb at java.lang.Throwable.(Throwable.java:265) at java.lang.Exception.(Exception.java:66) at org.eclipse.jetty.util.MultiException.(MultiException.java:38) at org.eclipse.jetty.server.Server.doStop(Server.java:465) at org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89) - locked java.lang.Object@279dd959 at org.jvnet.hudson.test.JenkinsRule.after(JenkinsRule.java:480) at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:564) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)"Jenkins cron thread" Id=179 Group=FailOnTimeoutGroup WAITING on java.util.TaskQueue@541179e7 at java.lang.Object.wait(Native Method) - waiting on java.util.TaskQueue@541179e7 at java.lang.Object.wait(Object.java:502) at java.util.TimerThread.mainLoop(Timer.java:526) at java.util.TimerThread.run(Timer.java:505)"jenkins.util.Timer [#10]" Id=200 Group=FailOnTimeoutGroup WAITING on
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Alex Earl commented on JENKINS-55226 Re: Deadlock while running tests When filing these type of issues, it would be helpful to have a way of reproducing the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55226) Deadlock while running tests
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-55226 Deadlock while running tests Issue Type: Bug Assignee: Alex Earl Components: token-macro-plugin Created: 2018-12-17 14:19 Environment: Jenkins 2.155 PCT Java 1.8 && Java 11 Priority: Minor Reporter: Adrien Lecharpentier While I was running token-macro against PCT and Jenkins 2.155, I noticed that deadlocks are happening during the plugin tests. [INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest[INFO] Running org.jenkinsci.plugins.tokenmacro.PipelineTest=== Starting testException(org.jenkinsci.plugins.tokenmacro.PipelineTest) 0.084 [id=175] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:35227/jenkins/ 0.236 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 0.279 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 0.704 [id=181] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 0.713 [id=182] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 0.716 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 0.719 [id=186] INFO h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate optional component org.jenkinsci.plugins.workflow.steps.scm.SubversionStep$DescriptorImpl; skipping 1.234 [id=184] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 1.268 [id=186] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 180.000 [id=1] WARNING o.j.hudson.test.JenkinsRule$2#evaluate: Test timed out (after
