You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run j2cl unit tests using the <webdriver>chrome</webdriver> option from within a docker image, the ChromeDriver fails to start with the following error:
[ERROR] Failed to execute goal com.vertispan.j2cl:j2cl-maven-plugin:0.22.0:test (test-js) on project J2clMavenProject: Failed to run tests: session not created: probably user data directory is already in use, please specify a unique value for --user-data-dir argument, or don't use --user-data-dir
[ERROR] Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
[ERROR] System info: host: '54a1659898c2', ip: '172.17.0.2', os.name: 'Linux', os.arch: 'amd64', os.version: '6.6.65-1-MANJARO', java.version: '21.0.6'
[ERROR] Driver info: driver.version: ChromeDriver
[ERROR] remote stacktrace: #0 0x55e82d96c09a <unknown>
[ERROR] #1 0x55e82d4338b0 <unknown>
[ERROR] #2 0x55e82d46cea4 <unknown>
[ERROR] #3 0x55e82d4688ff <unknown>
[ERROR] #4 0x55e82d4b929f <unknown>
[ERROR] #5 0x55e82d4b87d6 <unknown>
[ERROR] #6 0x55e82d4aa753 <unknown>
[ERROR] #7 0x55e82d47638e <unknown>
[ERROR] #8 0x55e82d477b51 <unknown>
[ERROR] #9 0x55e82d93576b <unknown>
[ERROR] #10 0x55e82d9396f2 <unknown>
[ERROR] #11 0x55e82d9218fc <unknown>
[ERROR] #12 0x55e82d93a2e4 <unknown>
[ERROR] #13 0x55e82d9059cf <unknown>
[ERROR] #14 0x55e82d95acd8 <unknown>
[ERROR] #15 0x55e82d95aeb6 <unknown>
[ERROR] #16 0x55e82d96af16 <unknown>
[ERROR] #17 0x7f1195fabaa4 <unknown>
[ERROR] #18 0x7f1196038a34 __clone
This is most likely a docker image configuration issue on my part, but I found a workaround which involves using a selenium new RemoteWebDriver(URI.create("http://localhost:4444").toURL(), new ChromeOptions()); to connect to a separate docker container running the docker image from here: (https://hub.docker.com/r/selenium/standalone-chrome).
Would you accept a PR to add support for specifying a "RemoteWebDriver" webdriver and "remote webdriver uri" in TestMojo.java? Or do you have ideas on why ChromeDriver is complaining about the user-data-directory?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I run j2cl unit tests using the
<webdriver>chrome</webdriver>
option from within a docker image, the ChromeDriver fails to start with the following error:This is most likely a docker image configuration issue on my part, but I found a workaround which involves using a selenium
new RemoteWebDriver(URI.create("http://localhost:4444").toURL(), new ChromeOptions());
to connect to a separate docker container running the docker image from here: (https://hub.docker.com/r/selenium/standalone-chrome).Would you accept a PR to add support for specifying a "RemoteWebDriver" webdriver and "remote webdriver uri" in TestMojo.java? Or do you have ideas on why ChromeDriver is complaining about the user-data-directory?
Beta Was this translation helpful? Give feedback.
All reactions