[
https://issues.jboss.org/browse/JBTM-948?page=com.atlassian.jira.plugin.s...
]
Paul Robinson edited comment on JBTM-948 at 1/24/12 10:34 AM:
--------------------------------------------------------------
This needs to run headless for CI. When I ran it headless (I simply ssh'd to localhost
then ran the test) I got this failure:
{code}
15:32:12.804 INFO - Command request: getNewBrowserSession[*firefox,
http://localhost:8080/, , ] on session null
15:32:12.807 INFO - creating new remote session
15:32:12.823 WARN - Caution: '/usr/bin/firefox': file is a script file, not a real
executable. The browser environment is no longer fully under RC control
15:32:12.824 INFO - Allocated session 963b50a8a34b41298a6691e420708596 for
http://localhost:8080/, launching...
15:32:12.843 INFO - Preparing Firefox profile...
15:32:32.954 ERROR - Failed to start new browser session, shutdown browser and clear all
session data
java.lang.RuntimeException: Timed out waiting for profile to be created!
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.waitForFullProfileToBeCreated(FirefoxChromeLauncher.java:364)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.populateCustomProfileDirectory(FirefoxChromeLauncher.java:120)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launch(FirefoxChromeLauncher.java:90)
at
org.openqa.selenium.server.browserlaunchers.FirefoxChromeLauncher.launchRemoteSession(FirefoxChromeLauncher.java:416)
at
org.openqa.selenium.server.browserlaunchers.FirefoxLauncher.launchRemoteSession(FirefoxLauncher.java:118)
at
org.openqa.selenium.server.BrowserSessionFactory.createNewRemoteSession(BrowserSessionFactory.java:374)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession(BrowserSessionFactory.java:125)
at
org.openqa.selenium.server.BrowserSessionFactory.getNewBrowserSession(BrowserSessionFactory.java:86)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.getNewBrowserSession(SeleniumDriverResourceHandler.java:808)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.doCommand(SeleniumDriverResourceHandler.java:435)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handleCommandRequest(SeleniumDriverResourceHandler.java:405)
at
org.openqa.selenium.server.SeleniumDriverResourceHandler.handle(SeleniumDriverResourceHandler.java:149)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
15:32:32.962 INFO - Got result: Failed to start new browser session: Error while launching
browser on session null
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.837 sec <<<
FAILURE!
{code}
was (Author: paul.robinson):
This needs to run headless for CI. When I ran it headless (I simply ssh'd to
localhost then ran the test) I got this failure:
Provide test coverage for WS-AT/XA Bridge Demo Application
----------------------------------------------------------
Key: JBTM-948
URL:
https://issues.jboss.org/browse/JBTM-948
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Demonstrator, Testing, TxBridge
Affects Versions: 4.15.3
Reporter: Ivo Studensky
Assignee: Ivo Studensky
Fix For: 5.0.0.M2
The WS_AT/XA bridge demo application which is shipped with JBossTS project at the moment
should be shipped with EAP6 too. For this it needs a test coverage. Hence provide a
reasonable set of tests for it. The tests should be placed to JBossTS project and it is
allowed them to be maven based.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira