Adding the build.log.

El jue., 13 dic. 2018 a las 14:54, Bruno Baptista (<[email protected]>)
escribió:

> Thanks César.
>
> Some tests seem that have hanged but they don't provide feedback and ate
> just waiting for some condition. They can be like that for up to 5min.
>
> I think you forgot the attachment :)
>
> Bruno Baptista
> https://twitter.com/brunobat_
>
>
> On 13/12/18 20:38, César Hernández Mendoza wrote:
> > Hi Bruno
> >
> > I follow the instruction you shared in this thread on my mac.
> >
> >     mvn -Pquick -Dsurefire.useFile=false -DdisableXmlReport=true
> >     -DuniqueVersion=false -ff -Dassemble -DskipTests
> >     -DfailIfNoTests=false
> >     clean install -T1C
> >
> >
> > Worked fine and it looks around 3 min in my box:
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD SUCCESS
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 03:48 min (Wall Clock)
> > [INFO] Finished at: 2018-12-13T12:41:06-06:00
> > [INFO] Final Memory: 264M/3515M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> >
> > On the other hand,  when I went to tck/microprofile-tck and ran:
> >
> >     mvn --fail-at-end clean install -Pall-adapters
> >     -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true
> >     -Dhttps.protocols=TLSv1.1,TLSv1.2 -Dsurefire.useFile=false
> >     -DdisableXmlReport=true > build.log
> >
> >
> > the build hanged after a couple of minutes. I had to kill the process.
> > I'm attaching the build.log
> >
> >
> > El jue., 13 dic. 2018 a las 11:37, Bruno Baptista (<[email protected]
> > <mailto:[email protected]>>) escribió:
> >
> >     Thanks César!
> >
> >     Bruno Baptista
> >     https://twitter.com/brunobat_
> >
> >
> >     On 13/12/18 17:15, César Hernández Mendoza wrote:
> >     > Hi Bruno,
> >     > I can test on Mac.
> >     >
> >     > El jue., 13 dic. 2018 a las 10:16, Bruno Baptista
> >     (<[email protected] <mailto:[email protected]>>)
> >     > escribió:
> >     >
> >     >> Hi All,
> >     >>
> >     >> I've updated almost all the microprofile tests to run in
> >     parallel with
> >     >> 1C: https://github.com/apache/tomee/pull/268
> >     >>
> >     >> They seem to work ok on my machine.
> >     >>
> >     >> We were getting JVM crashes due to the way we were redirecting the
> >     >> output of the remote processes. Now we use:
> >     >>
> >     >> final ProcessBuilder pb = new ProcessBuilder(args)
> >     >> .redirectOutput(Redirect.PIPE) .redirectError(Redirect.PIPE)
> >     >> .directory(home.getAbsoluteFile());
> >     >>
> >     >> I wonder if this is ok...
> >     >>
> >     >> Any volunteers to run the tck tests on a Mac and Windows?
> >     >>
> >     >>
> >     >> I also tried to run the container tests in parallel, but they
> >     also fail,
> >     >> sometimes:
> >     >>
> >     >> [INFO] Reactor Summary for OpenEJB :: Container 8.0.0-SNAPSHOT:
> >     >> [INFO]
> >     >> [INFO] OpenEJB :: Container ...............................
> >     SUCCESS [
> >     >> 0.517 s]
> >     >> [INFO] OpenEJB :: Container :: MBean Annotation API .......
> >     SUCCESS [
> >     >> 0.576 s]
> >     >> [INFO] OpenEJB :: Container :: API ........................
> >     SUCCESS [
> >     >> 0.140 s]
> >     >> [INFO] OpenEJB :: Container :: JPA Integration ............
> >     SUCCESS [
> >     >> 0.288 s]
> >     >> [INFO] OpenEJB :: Container :: Loader .....................
> >     SUCCESS [
> >     >> 12.271 s]
> >     >> [INFO] OpenEJB :: Container :: Java Agent .................
> >     SUCCESS [
> >     >> 0.072 s]
> >     >> [INFO] OpenEJB :: Container :: Java EE ....................
> >     SUCCESS [
> >     >> 9.044 s]
> >     >> [INFO] OpenEJB :: Container :: Java EE Accessors ..........
> >     SUCCESS [
> >     >> 2.365 s]
> >     >> [INFO] OpenEJB :: Container :: Core .......................
> FAILURE
> >     >> [02:27 min]
> >     >> [INFO] OpenEJB :: Container :: JUnit ......................
> SKIPPED
> >     >> [INFO]
> >     >>
> >
>  ------------------------------------------------------------------------
> >     >> [INFO] BUILD FAILURE
> >     >> [INFO]
> >     >>
> >
>  ------------------------------------------------------------------------
> >     >> [INFO] Total time:  02:52 min
> >     >> [INFO] Finished at: 2018-12-13T12:56:16Z
> >     >> [INFO]
> >     >>
> >
>  ------------------------------------------------------------------------
> >     >> [ERROR] Failed to execute goal
> >     >> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test
> >     >> (default-test) on project openejb-core: There are test failures.
> >     >> [ERROR]
> >     >> [ERROR] Please refer to
> >     >>
> >
>  /devel/code/apache/tomee/container/openejb-core/target/surefire-reports
> >     >> for the individual test results.
> >     >> [ERROR] Please refer to dump files (if any exist)
> >     [date]-jvmRun[N].dump,
> >     >> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> >     >> [ERROR] ExecutionException The forked VM terminated without
> >     properly
> >     >> saying goodbye. VM crash or System.exit called?
> >     >>
> >     >> ...
> >     >>
> >     >> In this example only 2 tests failed. Will be investigating what
> >     might be
> >     >> the cause.
> >     >>
> >     >> Cheers.
> >     >>
> >     >> Bruno Baptista
> >     >> https://twitter.com/brunobat_
> >     >>
> >     >>
> >     >> On 11/12/18 10:06, Bruno Baptista wrote:
> >     >>> Hi folks,
> >     >>>
> >     >>> Yesterday me and Roberto we dived into the parallel execution
> >     of tests
> >     >>> with Arquillian.
> >     >>>
> >     >>> Roberto had some experience with this and was aware of
> TOMEE-2176.
> >     >>>
> >     >>> I was able to perform some parallel builds in the TCK
> >     projects. The
> >     >>> full build has issues in the container that need to be
> researched.
> >     >>>
> >     >>> Unfortunately, this work uncovered other deeper issues in the
> >     >>> /RemoteServer/ class. The faster the computer, the slower the
> >     test run
> >     >>> gets!!! There are collisions of some sort going on.
> >     >>>
> >     >>>   1. We were writing STDOUT in the wrong forked JVM leading to
> >     >>>      exceptions. This might be fixed by don't inheriting the
> >     output.
> >     >>>      See PR.
> >     >>>   2. Now, sometimes the servers fail to start and be stopped
> >     I'm still
> >     >>>      figuring that out why.
> >     >>>
> >     >>> Suggestions are welcome. Will be adding some additional debugging
> >     >>> output and trying different things.
> >     >>>
> >     >>> PR: https://github.com/apache/tomee/pull/268
> >     >>>
> >     >>> Cheers
> >     >>>
> >     >>> Bruno Baptista
> >     >>> https://twitter.com/brunobat_
> >     >>>
> >     >>>
> >     >>> On 10/12/18 23:05, Bruno Baptista wrote:
> >     >>>> Thanks!
> >     >>>>
> >     >>>> Bruno Baptista
> >     >>>> https://twitter.com/brunobat_
> >     >>>>
> >     >>>>
> >     >>>> On 10/12/18 22:51, Roberto Cortez wrote:
> >     >>>>> Done. Unfortunately, only committers can do it.
> >     >>>>>
> >     >>>>>> On 10 Dec 2018, at 20:58, Bruno Baptista
> >     <[email protected] <mailto:[email protected]>> wrote:
> >     >>>>>>
> >     >>>>>> Hi folks,
> >     >>>>>>
> >     >>>>>> I've been researching why the full build is slow and I
> >     think I've
> >     >>>>>> come up with a solution...
> >     >>>>>>
> >     >>>>>> Can someone please assign this jira to me?
> >     >>>>>> https://issues.apache.org/jira/browse/TOMEE-2176
> >     >>>>>>
> >     >>>>>> If I can get assigning powers on jira would also be nice :)
> >     >>>>>>
> >     >>>>>> Cheers.
> >     >>>>>>
> >     >>>>>> --
> >     >>>>>> Bruno Baptista
> >     >>>>>> https://twitter.com/brunobat_
> >     >>>>>>
> >     >>>>>>
> >     >
> >
> >
> >
> > --
> > Atentamente:
> > César Hernández Mendoza.
>


-- 
Atentamente:
César Hernández Mendoza.

Reply via email to