This could be a Selenium issue with chrome-driver.
To register a *Selenium Grid Node* for *ChromeDriver* and *Chrome* you need
to pass the absolute path of the *ChromeDriver*
*(from:
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 <
jo
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 <
jonathan.macken...@
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
Read about how Jenkins aborts a build here
https://www.jenkins.io/doc/book/using/aborting-a-build/
It is somewhat OS dependent. I was looking for the same thing on a windows
10 agent but TerminateProcess is a non-interruptible function.
I heard that some folks had tried in-memory patching on the
, Adakar
>
> W dniu wtorek, 3 grudnia 2019 16:56:54 UTC+1 użytkownik Jonathan Mackenzie
> napisał:
>>
>> C:\WINDOWS\system32>sc query "jenkins"
>>
>> SERVICE_NAME: jenkins
>> TYPE : 10 WIN32_OWN_PROCESS
>
C:\WINDOWS\system32>sc query "jenkins"
SERVICE_NAME: jenkins
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE: 0 (0x0)
SERVICE_EXIT_CODE : 0
