The build of the java11-experimentation branch (on Java 8) is running on a
box here in my office. "Normally" a build of master on that box takes ~ 2
to 2.5 hours. The failures I listed are for that build.
The build on the Apache CI is master. Recent builds on that node seem to be
the same length of time - a couple of hours.
Let's see where we are when these are done. Certainly seeing stuff like
WARNING: 2ef75bcd694868d71565ceb30277c45c162cb6.war was not deployed
Mar 01, 2019 8:20:05 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder build
INFO: Test archive built [info:
org.jboss.cdi.tck.tests.implementation.builtin.metadata.broken.typeparam.interceptor.InterceptedBeanTypeParamInitializerTest,
time: 38 ms]
Mar 01, 2019 8:20:05 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=
http://localhost:40707/tomee/ejb}
Mar 01, 2019 8:22:57 PM org.apache.openejb.client.EventLogger log
WARNING: RequestFailed{server=http://localhost:40707/tomee/ejb}
JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object input
stream to server (OEJP/4.6) : null}
Mar 01, 2019 8:22:57 PM
org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener beforeInvocation
INFO: Invoke InterceptedBeanTypeParamInitializerTest.testDeploymentFails:
864/1,571 Failed tests: 0 (348)
Mar 01, 2019 8:22:57 PM org.apache.openejb.arquillian.common.TomEEContainer
undeploy
Even if it isn't being presented as a test failure, makes me think
something isn't right.
This isn't happening on the master build on the CI.
Jon
On Fri, Mar 1, 2019 at 8:45 PM j4fm <[email protected]> wrote:
> PR409 was the merge that was first seen being slow.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
