Turns out this timeout is configurable via a system property but not if it is a unit test, unfortunately. I looked at https://github.com/jenkinsci/workflow-durable-task-step-plugin/blame/master/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/ExecutorPickle.java and on line 71 there is public static long TIMEOUT_WAITING_FOR_NODE_MILLIS = Main.isUnitTest ? /* fail faster */ TimeUnit.SECONDS.toMillis(15) : Long.getLong( *ExecutorPickle.class.getName()+".timeoutForNodeMillis"*, TimeUnit.MINUTES. toMillis(5));
On Fri, Jun 4, 2021 at 12:22 PM Jonathan Mackenzie < [email protected]> wrote: > NVM, found the log > <https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadobe-cloud-manager-plugin/detail/PR-4/12/tests>. > Saw that you increased the test timeout, but this was still the same error > as before: > > hudson.model.Queue$WaitingItem:ExecutorStepExecution.PlaceholderTask{runId=test#1,label=,context=CpsStepContext[3:node]:Owner[test/1:test > #1],cookie=a2fda7d9-72d9-4431-9b08-fd737441c0e5,auth=null}:38 after waiting > for 15,000 ms because we assume unknown Node master is never going to > appear! > > > > On Fri, Jun 4, 2021 at 12:06 PM Jonathan Mackenzie < > [email protected]> wrote: > >> Here is the junit code, it might help. >> https://junit.org/junit4/xref/org/junit/internal/runners/statements/FailOnTimeout.html >> The timeout is set in the Builder object. >> You may be suffering from a Windows process create time issue. I assume >> you are running this on the Jenkins server itself and it has to restart >> then spin up the agent and connect to it. What is the error seen after you >> added WithTimeout annotation? >> >> On Fri, Jun 4, 2021 at 11:05 AM Bryan Stopp <[email protected]> >> wrote: >> >>> Follow-up: I found a way to extend the timeout for a test (WithTimout >>> annotation), and bumped it up to 5 minutes. However, it does not solve the >>> issues. >>> >>> Any help is much appreciated. >>> >>> -Stopp >>> >>> On Friday, June 4, 2021 at 11:24:48 AM UTC-5 Bryan Stopp wrote: >>> >>>> Hello all, >>>> >>>> Looking for some advice/help here. I've added a bunch of tests for my >>>> plugin, but it seems that on Windows I get random failures of my restart >>>> test cases. It doesn't happen during the Linux runs. >>>> >>>> Essentially I'm validating that my custom steps come up clean from a >>>> reboot and then handle expected interactions correctly, and continue the >>>> pipeline. >>>> >>>> The failures are intermittent, and randomly occur on different reboot >>>> tests. I have a number of them in the plugin. At first i was getting errors >>>> because I wasn't waiting for the test Jenkins to finish its boot. But now >>>> that i protected against that, I'm getting timeouts. >>>> >>>> Two of the latest runs which show the randomness of the failures are >>>> here >>>> <https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadobe-cloud-manager-plugin/detail/PR-4/10/tests> >>>> and here >>>> <https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadobe-cloud-manager-plugin/detail/PR-4/11/tests> >>>> . >>>> >>>> Does anyone have any idea what could cause this, and is there a way for >>>> me to adjust my tests to account for the time? Is this something that i can >>>> adjust on a Jenkins CI build, or will it be ignored? >>>> >>>> Thanks in advance everyone! >>>> >>>> -Bryan >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/3824aa9f-d1df-4f82-9521-912fd70ae318n%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/3824aa9f-d1df-4f82-9521-912fd70ae318n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO1vCWF2cObf4_a0EKuYvqWf6eAcgmVHWVx6Fwh3YTwUcmhOyQ%40mail.gmail.com.
