Unable to run JsTestDriver

[Chad Dalton]

I have a Bamboo server on RHEL 6.4 that use to successfully run Qunit test using JsTestDriver via an ant script, then some wonderful sysadmin decided to yum remove firefox so the test broke, I re-installed firefox and now the test do not work. I am running it like so,

java -jar lib/JsTestDriver-1.3.5.jar  --config js/test/jsTestDriver.conf --port 4224 --browser /usr/bin/firefox --tests all --testOutput js/test-reports/ --basePath . --runnerMode DEBUG --verbose

and get the following output,

...lots of stuff that does not look interesting...

FINE: Queueing BrowserActionRunner [com.google.jstestdriver.RunTestsAction@27f8d56c] for CommandLineBrowserRunner [

browserPath=/usr/bin/firefox

args=,

process=null,

 process log={

Not Started

}].

Apr 17, 2014 4:52:04 PM com.google.jstestdriver.browser.BrowserControl captureBrowser

FINE: Browser timeout 30000000 for 1397767924433

Apr 17, 2014 4:53:34 PM com.google.jstestdriver.browser.BrowserActionExecutorAction run

FINE: Finished BrowserActions [com.google.jstestdriver.RunTestsAction@27f8d56c].

Apr 17, 2014 4:53:34 PM com.google.jstestdriver.ActionRunner runActions

INFO: Finished com.google.jstestdriver.browser.BrowserActionExecutorAction@44925e1f

Apr 17, 2014 4:53:34 PM com.google.jstestdriver.ActionRunner runActions

INFO:

Apr 17, 2014 4:53:34 PM com.google.jstestdriver.browser.CommandLineBrowserRunner stopBrowser

WARNING: Unexpected shutdown java.lang.UNIXProcess@2f4f069b 1

Logs:error:

out:

Apr 17, 2014 4:53:34 PM com.google.jstestdriver.Main main

FINE: Error {}

Failures during test run.

Caused by:

java.lang.RuntimeException: Test run cancelled, exceeded 90s

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:135)

        at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:81)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfigurationWithFlags(JsTestDriverImpl.java:342)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfiguration(JsTestDriverImpl.java:233)

        at com.google.jstestdriver.Main.main(Main.java:70)

Caused by: java.util.concurrent.CancellationException

        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:250)

        at java.util.concurrent.FutureTask.get(FutureTask.java:111)

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:131)

        ... 4 more

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:154)

        at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:81)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfigurationWithFlags(JsTestDriverImpl.java:342)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfiguration(JsTestDriverImpl.java:233)

        at com.google.jstestdriver.Main.main(Main.java:70)

Caused by:java.lang.RuntimeException: Test run cancelled, exceeded 90s

java.lang.RuntimeException: Test run cancelled, exceeded 90s

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:135)

        at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:81)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfigurationWithFlags(JsTestDriverImpl.java:342)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfiguration(JsTestDriverImpl.java:233)

        at com.google.jstestdriver.Main.main(Main.java:70)

Caused by: java.util.concurrent.CancellationException

        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:250)

        at java.util.concurrent.FutureTask.get(FutureTask.java:111)

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:131)

        ... 4 more

Failures during test run.

Caused by:

java.lang.RuntimeException: Test run cancelled, exceeded 90s

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:135)

        at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:81)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfigurationWithFlags(JsTestDriverImpl.java:342)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfiguration(JsTestDriverImpl.java:233)

        at com.google.jstestdriver.Main.main(Main.java:70)

Caused by: java.util.concurrent.CancellationException

        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:250)

        at java.util.concurrent.FutureTask.get(FutureTask.java:111)

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:131)

        ... 4 more

        at com.google.jstestdriver.browser.BrowserActionExecutorAction.run(BrowserActionExecutorAction.java:154)

        at com.google.jstestdriver.ActionRunner.runActions(ActionRunner.java:81)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfigurationWithFlags(JsTestDriverImpl.java:342)

        at com.google.jstestdriver.embedded.JsTestDriverImpl.runConfiguration(JsTestDriverImpl.java:233)

        at com.google.jstestdriver.Main.main(Main.java:70)

Caused by:

java.lang.RuntimeException: Test run cancelled, exceeded 90s

Unexpected Runner Condition: Failures during test run.

 Use --runnerMode DEBUG for more information.

The interesting part to me is this,

args=,

process=null,

 process log={

Not Started

}].

In the old logs in Bamboo where it use to work that section looks like so,

build	24-Mar-2014 12:54:42	     [java] FINE: Browser CommandLineBrowserRunner [
build	24-Mar-2014 12:54:42	     [java] browserPath=/usr/bin/firefox
build	24-Mar-2014 12:54:42	     [java] args=,
build	24-Mar-2014 12:54:42	     [java] process=java.lang.UNIXProcess@4495f88b,
build	24-Mar-2014 12:54:42	     [java]  process log={
build	24-Mar-2014 12:54:42	     [java] error:
build	24-Mar-2014 12:54:42	     [java] 
build	24-Mar-2014 12:54:42	     [java] out:
build	24-Mar-2014 12:54:42	     [java] 
build	24-Mar-2014 12:54:42	     [java] }] started with id 1395680073374

So that indicates to me that firefox is not starting. This is a headless server and I can run firefox and display back via xming so I know its working.

Any ideas? I'd like to get it working the way it was before so we do not have to reconfigure all of our projects that run jstd this way.

Thanks,

Chad

[Cory Smith]

Looks like firefox isn't contacting the server after start up. Can you check and see if it's on a first run window?

--
You received this message because you are subscribed to the Google Groups "JsTestDriver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to js-test-drive...@googlegroups.com.
To post to this group, send email to js-test...@googlegroups.com.
Visit this group at http://groups.google.com/group/js-test-driver.
For more options, visit https://groups.google.com/d/optout.

[Chad]

How do I check if it's on a first run window? I did manage to alter the command and add xvfb-run in front of the java command and now it works but that will require us to modify all the build files that execute jstd.