[ERROR] Failed to execute goal com.github.searls:jasmine-maven-plugin:2.0:test (default)

446 views
Skip to first unread message

Sven Stauber

unread,
Nov 28, 2017, 3:24:21 PM11/28/17
to Opencast Development
Dear Opencast Developers,

Since months building r/4.x always fails like this:

[ERROR] Failed to execute goal com.github.searls:jasmine-maven-plugin:2.0:test (default) on project matterhorn-engage-theodul-plugin-controls: The jasmine-maven-plugin encountered an exception:
[ERROR] org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
[ERROR] Build info: version: '2.45.0', revision: '5017cb8e7ca8e37638dc3091b2440b90a1d8686f', time: '2015-02-27 09:10:26'
[ERROR] System info: host: 'vpn-ho-c-2.switch.ch', ip: '130.59.27.2', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_65'
[ERROR] Driver info: driver.version: PhantomJSDriver
[ERROR] at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:593)
[ERROR] at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
[ERROR] at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
[ERROR] at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
[ERROR] at org.openqa.selenium.phantomjs.PhantomJSDriver.<init>(PhantomJSDriver.java:115)
[ERROR] at org.openqa.selenium.phantomjs.PhantomJSDriver.<init>(PhantomJSDriver.java:104)
[ERROR] at com.github.searls.jasmine.driver.WebDriverFactory.createPhantomJsWebDriver(WebDriverFactory.java:149)
[ERROR] at com.github.searls.jasmine.driver.WebDriverFactory.createWebDriver(WebDriverFactory.java:68)
[ERROR] at com.github.searls.jasmine.mojo.TestMojo.createDriver(TestMojo.java:260)
[ERROR] at com.github.searls.jasmine.mojo.TestMojo.executeSpecs(TestMojo.java:235)
[ERROR] at com.github.searls.jasmine.mojo.TestMojo.run(TestMojo.java:204)
[ERROR] at com.github.searls.jasmine.mojo.AbstractJasmineMojo.execute(AbstractJasmineMojo.java:385)
[ERROR] at com.github.searls.jasmine.mojo.TestMojo.execute(TestMojo.java:191)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:497)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
[ERROR] Build info: version: '2.45.0', revision: '5017cb8e7ca8e37638dc3091b2440b90a1d8686f', time: '2015-02-27 09:10:26'
[ERROR] System info: host: 'vpn-ho-c-2.switch.ch', ip: '130.59.27.2', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_65'
[ERROR] Driver info: driver.version: PhantomJSDriver
[ERROR] at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:171)
[ERROR] at org.openqa.selenium.phantomjs.PhantomJSCommandExecutor.execute(PhantomJSCommandExecutor.java:78)
[ERROR] at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:572)
[ERROR] ... 34 more
[ERROR] Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [http://localhost:40466/status] to be available after 20001 ms
[ERROR] at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:104)
[ERROR] at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:168)
[ERROR] ... 36 more
[ERROR] Caused by: com.google.common.util.concurrent.UncheckedTimeoutException: java.util.concurrent.TimeoutException
[ERROR] at com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:143)
[ERROR] at org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:79)
[ERROR] ... 37 more
[ERROR] Caused by: java.util.concurrent.TimeoutException
[ERROR] at java.util.concurrent.FutureTask.get(FutureTask.java:205)
[ERROR] at com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:130)
[ERROR] ... 38 more
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :matterhorn-engage-theodul-plugin-controls

After many times of just doing a mvn clean install -Pdev -rf :matterhorn-engage-theodul-plugin-controls -DskipTests I finally managed to copy-paste the build error.


Am I the only person running into this, or is this a known issue?

Best,
Sven

Greg Logan

unread,
Nov 28, 2017, 3:28:19 PM11/28/17
to d...@opencast.org
Hi Sven,

I have seen this very rarely, usually on my local build cluster when it's heavily loaded.  I just assumed that the node in question just didn't have enough cycles to get things built in time, and hence the timeout.  Are you seeing this on a regular basis?

G


--
You received this message because you are subscribed to the Google Groups "Opencast Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@opencast.org.

Sven Stauber

unread,
Nov 28, 2017, 3:34:33 PM11/28/17
to Opencast Development
It see that each time I build.

Lars Kiesow

unread,
Nov 28, 2017, 4:19:31 PM11/28/17
to d...@opencast.org
Hi Sven,
hi Greg,
we have this issue for quite some time. Somewhere here on list should
be of passed proposal of mine which said that these tests should be
deactivated by default since they are pretty unstable. I noticed a
while ago that someone seems to have activated them again by default (I
got the same build error). I can take a short look at it tomorrow and
again set them to be deactivated by default.
–Lars

Lars Kiesow

unread,
Nov 29, 2017, 4:02:22 PM11/29/17
to d...@opencast.org
Hi all,
I did take a look at this. The following patch would disable Jasmine
tests on all player modules:

https://bitbucket.org/lkiesow/opencast/commits/8226326c48de585b0e884e95aa6220a580fa06a9

I did notice that they are still deactivated on the core module so
maybe that was the consensus back then. I don't remember the exact
details. Not sure how we want to proceed. Options are trying to fix the
issue which is probably very hard since the issue seems to pop up at
random, completely deactivate Jasmine for the player or just
deactivate jasmine on that one particular module which is causing the
issue now. I do not have any particular strong opinion on this. Any
thoughts?
–Lars
Reply all
Reply to author
Forward
0 new messages