Bad luck. I think it is related to the fact that both builds (for 7.x and master) run in the same time. I've tried to fix this once but apparently it is not enough.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sun, Jan 10, 2016 at 5:33 PM, Sebastien <[email protected]> wrote: > Tests are failing in local too for 7.x branch, but I am not sure how it is > related to my change... > These are passing on master, is it just a kind of bad luck? > > > ------------------------------------------------------------------------------- > Test set: > > org.apache.wicket.arquillian.testing.servletcontext.ArquillianContainerProvidedTest > > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.003 sec > <<< FAILURE! - in > > org.apache.wicket.arquillian.testing.servletcontext.ArquillianContainerProvidedTest > > org.apache.wicket.arquillian.testing.servletcontext.ArquillianContainerProvidedTest > Time elapsed: 0 sec <<< ERROR! > java.lang.RuntimeException:* Arquillian has previously been attempted > initialized, but failed*. See cause for previous exception > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:106) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at > > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:107) > at > > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:77) > at > > org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:53) > at > > org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:144) > at > > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at > > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: > org.jboss.arquillian.container.spi.client.container.LifecycleException: The > server is already running! Managed containers do not support connecting to > running server instances due to the possible harmful effect of connecting > to the wrong server. Please stop server before running or change to another > type of container. > To disable this check and allow Arquillian to connect to a running server, > set allowConnectingToRunningServer to true in the container configuration > > > On Sun, Jan 10, 2016 at 5:02 PM, <[email protected]> wrote: > > > The Buildbot has detected a new failure on builder wicket-branch-7.x > while > > building wicket. Full details are available at: > > http://ci.apache.org/builders/wicket-branch-7.x/builds/95 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: hemera_ubuntu > > > > Build Reason: The SingleBranchScheduler scheduler named > > 'on-wicket-branch-7.x-commit' triggered this build > > Build Source Stamp: [branch wicket-7.x] > > 3ae55ea92eda1cb6b640727f3c4c8629e212ad0f > > Blamelist: Sebastien Briquet <[email protected]> > > > > BUILD FAILED: failed compile > > > > Sincerely, > > -The Buildbot > > > > > > > > >
