[INFO] OpenEJB :: Examples :: JSF2/CDI/BV/JPA/DeltaSpike .. FAILURE [ 20.204 s]

SEVERE - ==> a bad OS was mentionned

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.superbiz.deltaspike.exceptionhandling.ExceptionHandlingDemoTest
INFO - ********************************************************************************
INFO - OpenEJB http://openejb.apache.org/
INFO - Startup: Sun Jul 20 13:08:01 CDT 2014
INFO - Copyright 1999-2013 (C) Apache OpenEJB Project, All Rights Reserved.
INFO - Version: 5.0.0-SNAPSHOT
INFO - Build date: 20140720
INFO - Build time: 12:42
INFO - ******************************************************************************** INFO - openejb.home = /home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling INFO - openejb.base = /home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling INFO - Created new singletonService org.apache.openejb.cdi.ThreadSingletonServiceImpl@473b46c3
INFO - Succeeded in installing singleton service
INFO - Cannot find the configuration file [conf/openejb.xml]. Will attempt to create one for the beans deployed. INFO - Configuring Service(id=Default Security Service, type=SecurityService, provider-id=Default Security Service) INFO - Configuring Service(id=Default Transaction Manager, type=TransactionManager, provider-id=Default Transaction Manager)
INFO - Using 'openejb.deployments.classpath=false'
INFO - Creating TransactionManager(id=Default Transaction Manager)
INFO - Creating SecurityService(id=Default Security Service)
INFO - Configuring enterprise application: /home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war INFO - Configuring Service(id=Default Managed Container, type=Container, provider-id=Default Managed Container) INFO - Auto-creating a container for bean d0388df5-4c7a-4d1d-9579-2b7516069f81_org.superbiz.deltaspike.exceptionhandling.ExceptionHandlingDemoTest: Container(type=MANAGED, id=Default Managed Container)
INFO - Creating Container(id=Default Managed Container)
INFO - Using directory /tmp for stateful session passivation
INFO - Enterprise application "/home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war" loaded. INFO - Assembling app: /home/export/hanasaki/NetBeansProjects/tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war INFO - Existing thread singleton service in SystemInstance(): org.apache.openejb.cdi.ThreadSingletonServiceImpl@473b46c3
INFO - OpenWebBeans Container is starting...
INFO - Adding OpenWebBeansPlugin : [CdiPlugin]
INFO - class: org.apache.deltaspike.core.impl.config.ConfigurationExtension activated=true INFO - class: org.apache.deltaspike.core.impl.scope.DeltaSpikeContextExtension activated=true INFO - class: org.apache.deltaspike.core.impl.jmx.MBeanExtension activated=true INFO - class: org.apache.deltaspike.core.impl.message.MessageBundleExtension activated=true INFO - class: org.apache.deltaspike.core.impl.message.NamedMessageBundleInvocationHandler activated=true INFO - class: org.apache.deltaspike.core.impl.exclude.extension.ExcludeExtension activated=true INFO - class: org.apache.deltaspike.core.impl.exclude.CustomProjectStageBeanFilter activated=true INFO - class: org.apache.deltaspike.core.impl.exclude.GlobalAlternative activated=true INFO - class: org.apache.deltaspike.core.impl.exception.control.extension.ExceptionControlExtension activated=true
INFO - Computed the following DeltaSpike ProjectStage: Production
INFO - All injection points were validated successfully.
INFO - OpenWebBeans Container has started, it took 274 ms.
INFO - Deployed Application(path=...../tomee/trunk/examples/deltaspike-exception-handling/d0388df5-4c7a-4d1d-9579-2b7516069f81.war)
*********** SEVERE - ==> a bad OS was mentionned


------------------------------------------------------------------------

*From:* Romain Manni-Bucau <[email protected]>
*Sent:*  Thursday, July 17, 2014 4:42PM
*To:* [email protected]
*Subject:* Re: TomEE 1.7.0 blockers


failed : full trunk build @ 22:45 CST on 2014-07-17
"mvn clean install"


------------------------------------------------------------------------

*From:* Romain Manni-Bucau <[email protected]>
*Sent:*  Thursday, July 17, 2014 4:42PM
*To:* [email protected]
*Subject:* Re: TomEE 1.7.0 blockers

Yeah, a lot of work done!

Side node: the fact we need the javaagent is an openjpa issue of
subclassing (known but kind of regression for them without the javaagent or
build time enhancement :()
Le 17 juil. 2014 22:11, "Andy Gumbrecht" <[email protected]> a
écrit :

To sum up what was wrong with the failed release on Sunday.

There was a SNAPSHOT dependency added to the parent POM and missed on
deploy - This was a breaking issue on the staging.

The builds could not be run in parallel, as many tests were using the same
conflicting ports. We have not had concurrent builders running on the same
buildbot for some time, but we have just been 'lucky' that this was
'mostly' working.
I think I have most, if not all, the tests that bind to ports changed so
that the ports are random - There will surely be more issues, but
concurrent builds have become significantly more stable.
We have to be able to cope with this as we now run builds of TomEE 1.7.x
on Java 6/7 and TomEE 2.0.x on Java 7/8/9EA - Most of these will fire at
the same time on commits and merges.

Another big issue that cost significant effort was that the javaagent had
been commented out in the openejb-core.pom during testing on Java 7, and
unfortunately forgotten. This broke the enhancement for several tests in a
very subtle way so that it was not obvious what was going wrong, the issues
were only apparent on Java 7 build. This was also done at time that the
build was not green, so made tracking down additionally hard. Obviously
this led us to believe that the Java 8 support we were about to announce
was broken.

As trunk had already had significant formatting and finals changes
committed it was necessary to make the 1.7.x branch comparable for
successful merges. This also led to several test failures that needed to be
rectified. The upside is that many tests were tweaked and updated during
this process.

Java 7 builds on Windows platforms also revealed several 'slightly' flawed
tests, again the upside is that some minor issues were addressed during
analysis.

We are now really close to getting all issues resolved - We will have
green builds by the end of the day.

Andy.


On 17/07/2014 17:18, David Blevins wrote:

Wondering if we can get a complete list of issues holding up 1.7 on a
single thread.

On the legal side, we still need:

   - Library diff
   - Review/adjust LICENSE and NOTICE files

The last one on the list frequently tanks releases.  Doesn't affect
security releases, but with larger versions is just a bear.  Let's make
sure we do that one before we put up another vote as voting drastically
decreases each time we reroll.




--
   Andy Gumbrecht

   http://www.tomitribe.com
   [email protected]
   https://twitter.com/AndyGeeDe

   TomEE treibt Tomitribe! | http://tomee.apache.org



Reply via email to