Strangest thing happened today, when i launched the build again, all 4
cores where in use, thanks anyways! *shamed*
On Thursday, 25 July 2013 22:21:28 UTC+2, David Auzinger wrote:
>
> Thanks for the response!
>
> Hmm, haven't checked that yet, but i will do it as soon as I get back to
> it tomor
Thanks for the response!
Hmm, haven't checked that yet, but i will do it as soon as I get back to it
tomorrow (I'm in europe). What i can tell you is that i started the process
via mvn test as a Jenkins build and spawned subthreads from this one.
On Jul 25, 2013 10:15 PM, "JonathanRRogers"
wrote:
On Thursday, July 25, 2013 7:41:44 AM UTC-4, David Auzinger wrote:
>
> Hello!
>
> I've run into a problem while using Jenkins as a means to automate a
> JUnit/Selenium test.
> I'm working on an automated test for a Webshop using the Selenium
> WebDriver.
> I wrote the test multithreaded to us all
Btw. im launching via Maven on the server too.
On Thursday, 25 July 2013 13:41:44 UTC+2, David Auzinger wrote:
>
> Hello!
>
> I've run into a problem while using Jenkins as a means to automate a
> JUnit/Selenium test.
> I'm working on an automated test for a Webshop using the Selenium
> WebDrive
Hello!
I've run into a problem while using Jenkins as a means to automate a
JUnit/Selenium test.
I'm working on an automated test for a Webshop using the Selenium WebDriver.
I wrote the test multithreaded to us all available CPU-cores. Problem is,
while the test runs as planned on a local machin
