Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Hi folks,

It is great to see so many contributions and we hope to continue and even increase the traffic.

Now, this also comes with a few challenges. Our build has been red for a while and I would like to get it green again:
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>

The latest build has some checkstyle violations and test failures:
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio <https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio>
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio <https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio>

It would be great if someone could pick these issues and fix them and we should prioritize any build fixing PR above everything else.

Also, when someone sends a PR, your work doesn’t end when it gets merged. Running a full build takes almost 5 hours, so the committer most of the times is not able to run the entire build to check your PR. I kindly ask you to monitor the tomee build bot here: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR gets merged and if you uncover something wrong, please send a corrective PR.

I’ll be out the next couple of days, so I hope someone can pick this up :)

Cheers,
Roberto

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

For the moment we can use the snapshot and monotor when bval is released
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Dec 10, 2018 at 2:45 PM Daniel Cunha <da...@apache.org> wrote:

> Hi folks,
>
> The fix for testes below is already on bval master branch.
> Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
>
> DuplicateConfigurationTest
> XMLConfigurationTest
> XMLConfiguredConstraintValidatorTest
>
> Can we use SNAPSHOT for now or wait for the next bval release?
>
>
> Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> <ra...@yahoo.com.invalid> escreveu:
>
> > Agree on both.
> >
> > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <jlmonteiro@tomitribe.com
> >
> > wrote:
> > >
> > > I only fixed the 2 imports for checkstyle
> > >
> > > I don't think from an end user perspective the information is very
> > > important in the changelog so did not created any ticket.
> > >
> > > If everyone thinks this is important for the user. I'm happy to create
> > one.
> > >
> > > In that area I don't think it makes sense either to create a bug in
> Jira
> > > for a non released feature. So if there is a new example and you find a
> > > bug. Go ahead and fix it. No need to create a new ticket. Use the one
> > > mentioning we are creating a new example.
> > >
> > >
> > >
> > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a
> écrit :
> > >
> > >> Overlooked that, sorry.
> > >> I intended to concentrate on the documentation for contribution
> > workflow,
> > >> that's why I asked.
> > >> So no problem if Jean-Louis picks it up.
> > >> And: what about a JIRA ticket for that ... ? ;-)
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> Sent from:
> > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>
> >
> >
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Working on Cesar's PR. I'll have a look after.

Le ven. 14 déc. 2018 à 11:44, Roberto Cortez <ra...@yahoo.com.invalid>
a écrit :

> It seems the build just randomly fails with this test:
> AutoConnectionTrackerTest.test
>
> [ERROR] Failures:
> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
>
> Sometimes it passes, sometimes it fails. I suspect it may be related with
> some timing issues / box speed of the build bot. I’m running the test non
> stop on my box (already executed 100+ times) and I couldn’t replicate the
> issue:
>
> Any ideias?
>
> > On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > I'll take the first one first
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> <ra...@yahoo.com.invalid>
> > wrote:
> >
> >> Thank you JL,
> >>
> >> At least this test is failing:
> >> org.apache.openejb.config.rules.CheckMissingClassTest
> >>
> >> And this one seems to fail randomly.
> >> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>
> >> Cheers,
> >> Roberto
> >>
> >>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> >> wrote:
> >>>
> >>> I have merged a couple of PR and I'm running a full build locally. I'll
> >>> work on fixes any issues if I find some but I'll report first here
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >> <ra...@yahoo.com.invalid>
> >>> wrote:
> >>>
> >>>> Hey Jon,
> >>>>
> >>>> The following commit:
> >>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>> <
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>
> >>>>
> >>>> Is failing the test:
> >>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>
> >>>> Can you help?
> >>>>
> >>>> Cheers,
> >>>> Roberto
> >>>>
> >>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> >>>>>
> >>>>> Hi Cesar,
> >>>>>
> >>>>>> This is a valuable piece of information.
> >>>>> That's what I thohght, too when I read the information on IRC ...
> >>>>> Thanks that you want to preserve it on the website.
> >>>>>
> >>>>> The JIRA task is now assigned to you.
> >>>>>
> >>>>> Frankie
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from:
> >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>
> >>>>
> >>
> >>
>
>

Re: Stabilize TomEE Build

[Richard Zowalla <ri...@zowalla.com>]

Very nice :) Thank you!

Am 20.12.2018 um 18:34 schrieb Bruno Baptista:
> That's great! :)
>
> Bruno Baptista
> https://twitter.com/brunobat_
>
>
> On 20/12/18 17:25, Jean-Louis Monteiro wrote:
>> Build is green, yeah.
>>
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
>>
>> Great community effort. Thanks everyone
>>
>> -- 
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Wed, Dec 19, 2018 at 10:56 PM Daniel Cunha <da...@apache.org> 
>> wrote:
>>
>>> Hi Roberto,
>>>
>>> I can't reproduce the issue in both 7.0.x and 7.1.x with my patch 
>>> applied,
>>> it seems passing as expected:
>>> [INFO]
>>> [INFO] -------------------------------------------------------
>>> [INFO]  T E S T S
>>> [INFO] -------------------------------------------------------
>>> [INFO] Running org.apache.tomee.TomEECliIT
>>> Must specify either a plain text to encrypt or a ciphered value to 
>>> decrypt.
>>> usage: cipher [options] <value>
>>>
>>> Uses a password cipher implementation to encrypt/decrypt a value.
>>>   -c,--cipher <c>   Specifies the password cipher implementation to use
>>>                     (default is Static3DES).
>>>   -d,--decrypt      Switches command line tool to decrypt.
>>>   -e,--encrypt      Switches command line tool to encrypt (default).
>>>   -h,--help         Lists these options and exits.
>>>
>>> Available ciphers are: cdi
>>> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
>>> 1.144 s - in org.apache.tomee.TomEECliIT
>>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
>>> Dec 19, 2018 6:52:57 PM org.apache.openejb.client.EventLogger log
>>> INFO: RemoteInitialContextCreated{providerUri=
>>> http://localhost:46355/tomee/ejb}
>>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time 
>>> elapsed: 3.25
>>> s - in org.apache.tomee.RemoteTomEEEJBContainerIT
>>> [INFO]
>>> [INFO] Results:
>>> [INFO]
>>> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
>>>
>>>
>>> Is possible to trigger build from buildbot for my PR?
>>>
>>> Em qua, 19 de dez de 2018 às 11:36, Roberto Cortez
>>> <ra...@yahoo.com.invalid> escreveu:
>>>
>>>> The CDI TCK runs after the OpenEJB Core, so you should be able to 
>>>> see the
>>>> debug information you added.
>>>>
>>>> I’m not sure if you noticed it, but I did add a @Ignore to the
>>>> AutoConnectionTracker test until we figure out what is wrong.
>>>>
>>>>> On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com>
>>>> wrote:
>>>>> Roberto, I saw you commented the test in which I added some more 
>>>>> stuff
>>> to
>>>>> test.
>>>>> Do you have some inputs after the run?
>>>>> Or are we still stuck on CDI ?
>>>>> -- 
>>>>> Jean-Louis Monteiro
>>>>> http://twitter.com/jlouismonteiro
>>>>> http://www.tomitribe.com
>>>>>
>>>>>
>>>>> On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org>
>>>> wrote:
>>>>>> I saw your comment and it's weird.
>>>>>> I'll look it again, the patch should fix exactly the test which you
>>> are
>>>>>> getting error. :)
>>>>>>
>>>>>> Thanks for review.
>>>>>>
>>>>>> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
>>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>>>
>>>>>>> Hi Daniel,
>>>>>>>
>>>>>>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can
>>> you
>>>>>>> confirm? Left you a note in the PR’s.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Roberto
>>>>>>>
>>>>>>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
>>>>>> jlmonteiro@tomitribe.com>
>>>>>>> wrote:
>>>>>>>> I pushed some debugging information on the other test and I'll be
>>>>>>>> monitoring the built
>>>>>>>> -- 
>>>>>>>> Jean-Louis Monteiro
>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>> http://www.tomitribe.com
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha 
>>>>>>>> <danielsoro@apache.org
>>>>>>> wrote:
>>>>>>>>> Nice... Thanks!
>>>>>>>>>
>>>>>>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
>>>>>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>>>>>>
>>>>>>>>>> Hi Daniel,
>>>>>>>>>> I didn't yet for the other branches. I'll do it today.
>>>>>>>>>>    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
>>>>>>>>>> danielsoro@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Roberto,
>>>>>>>>>>
>>>>>>>>>> I saw that you merged the changes on master, did you see the
>>> others
>>>>>>>>> changes
>>>>>>>>>> for branch 7.0.x and 7.1.x?
>>>>>>>>>>
>>>>>>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
>>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>>>
>>>>>>>>>>> Thank you Daniel,
>>>>>>>>>>>
>>>>>>>>>>> I’ll review and merge.
>>>>>>>>>>>
>>>>>>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it 
>>>>>>>>>>> happening a
>>>>>>> couple
>>>>>>>>>> of
>>>>>>>>>>> days before, but now it happened again. Not sure what is wrong
>>>>>> there,
>>>>>>>>>> since
>>>>>>>>>>> we used to pass it.
>>>>>>>>>>>
>>>>>>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>> Hi Roberto,
>>>>>>>>>>>>
>>>>>>>>>>>> the fix which I send is to make sure that the test is using 
>>>>>>>>>>>> the
>>>>>>>>> correct
>>>>>>>>>>>> version for libs.
>>>>>>>>>>>> For example, here
>>>>>>>>>>>>
>>> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70 
>>>
>>>>>>>>>>>> we have the version of the lib on the code.
>>>>>>>>>>>>
>>>>>>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will 
>>>>>>>>>>>> never
>>>>>>>>> works,
>>>>>>>>>>>> because for that build, it will have openejb-core-7.0.x and 
>>>>>>>>>>>> not
>>>>>>>>>>>> openejb-core-8.0.0-SNAPSHOT.
>>>>>>>>>>>>
>>>>>>>>>>>> That is the issue, we need to get the correct reference for 
>>>>>>>>>>>> the
>>>> lib
>>>>>>>>> to
>>>>>>>>>>> make
>>>>>>>>>>>> sure that the command will works.
>>>>>>>>>>>>
>>>>>>>>>>>> About the test stuck, reading the stacktrace that you send,
>>> seems
>>>>>>>>>>> something
>>>>>>>>>>>> during TCK test. Is it?
>>>>>>>>>>>>
>>>>>>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
>>>>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you please explain what the issue was?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Also, it seems our build is getting killed for taking to long
>>> due
>>>>>> to
>>>>>>>>>>> some
>>>>>>>>>>>>> tests being stuck?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Dec 17, 2018 12:06:54 PM 
>>>>>>>>>>>>> org.apache.openejb.client.EventLogger
>>>> log
>>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM 
>>>>>>>>>>>>> org.apache.openejb.client.EventLogger
>>>> log
>>>>>>>>>>>>> WARNING: 
>>>>>>>>>>>>> RequestFailed{server=http://localhost:40395/tomee/ejb
>>> }
>>>>>>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot 
>>>>>>>>>>>>> open
>>>>>>>>> object
>>>>>>>>>>> input
>>>>>>>>>>>>> stream to server (OEJP/4.6) : null}
>>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
>>>>>>>>>>> beforeInvocation
>>>>>>>>>>>>> INFO: Invoke
>>>>>>>>>>>>>
>>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor: 
>>>
>>>>>>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
>>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>>>>>>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
>>>>>> deployed
>>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
>>>>>>>>>>> build
>>>>>>>>>>>>> INFO: Test archive built [info:
>>>>>>>>>>>>>
>>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest, 
>>>
>>>>>>>>>>>>> time: 16 ms]
>>>>>>>>>>>>> Dec 17, 2018 12:10:28 PM 
>>>>>>>>>>>>> org.apache.openejb.client.EventLogger
>>>> log
>>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> command timed out: 18000 seconds without output running 
>>>>>>>>>>>>> ['mvn',
>>>>>>>>> '-U',
>>>>>>>>>>>>> '--show-version', '--fail-at-end',
>>>>>>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
>>>>>> 'install',
>>>>>>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
>>>>>>>>>> '-DdisableXmlReport=true',
>>>>>>>>>>>>> '-Dopenejb.arquillian.debug=true',
>>>>>>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>>>>>>>>>>>>> process killed by signal 9
>>>>>>>>>>>>> program finished with exit code -1
>>>>>>>>>>>>> elapsedTime=38754.464253
>>>>>>>>>>>>>
>>>>>>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30
>>> PM.
>>>>>> No
>>>>>>>>>>> logs
>>>>>>>>>>>>> in between...
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha 
>>>>>>>>>>>>>> <danielsoro@apache.org
>>>>>>>>>> wrote:
>>>>>>>>>>>>>> Hey folks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> we found an issue on TomEECliIT test.
>>>>>>>>>>>>>> I've opened fixes for test in all branch, please take a look
>>> on
>>>>>> it.
>>>>>>>>>>>>>> Fixes:
>>>>>>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
>>>>>>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>>>>>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>>>>>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Please wait a minute lol
>>>>>>>>>>>>>>> I'd rather have you help me if needed.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> First I don't have the feeling I spent time for nothing 
>>>>>>>>>>>>>>> on it
>>>>>> and
>>>>>>>>>>>>> second,
>>>>>>>>>>>>>>> at least I will learn something.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>>>>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help
>>>> look
>>>>>>>>>> into
>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It seems the build just randomly fails with this test:
>>>>>>>>>>>>>>>>> AutoConnectionTrackerTest.test
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [ERROR] Failures:
>>>>>>>>>>>>>>>>> [ERROR] AutoConnectionTrackerTest.test:198 expected:<1>
>>> but
>>>>>>>>>>> was:<0>
>>>>>>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may
>>> be
>>>>>>>>>> related
>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m
>>> running
>>>>>> the
>>>>>>>>>>> test
>>>>>>>>>>>>>>> non
>>>>>>>>>>>>>>>>> stop on my box (already executed 100+ times) and I 
>>>>>>>>>>>>>>>>> couldn’t
>>>>>>>>>>> replicate
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> issue:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Any ideias?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> I'll take the first one first
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thank you JL,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> At least this test is failing:
>>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> And this one seems to fail randomly.
>>>>>>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full
>>> build
>>>>>>>>>>> locally.
>>>>>>>>>>>>>>>> I'll
>>>>>>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll 
>>>>>>>>>>>>>>>>>>>> report
>>>>>> first
>>>>>>>>>>> here
>>>>>>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hey Jon,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The following commit:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9 
>>>
>>>>>>>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>>>>>>>>>
>>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9 
>>>
>>>>>>>>>>>>>>>>>>>>> Is failing the test:
>>>>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Can you help?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
>>>>>> kamin.feuer.2000@gmx.de
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the 
>>>>>>>>>>>>>>>>>>>>>> information
>>>> on
>>>>>>>>> IRC
>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Frankie
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>>>>>>>>>> Sent from:
>>>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html 
>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -- 
>>>>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>>>>>
>>>>>>>>>>>> -- 
>>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>>>
>>>>>>>>>> -- 
>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>
>>>>
>>> -- 
>>> Daniel "soro" Cunha
>>> https://twitter.com/dvlc_
>>>
-- 
Richard Zowalla
Lindenstraße 21
74348 Lauffen am Neckar

Re: Stabilize TomEE Build

[Bruno Baptista <br...@gmail.com>]

That's great! :)

Bruno Baptista
https://twitter.com/brunobat_


On 20/12/18 17:25, Jean-Louis Monteiro wrote:
> Build is green, yeah.
>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
>
> Great community effort. Thanks everyone
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 19, 2018 at 10:56 PM Daniel Cunha <da...@apache.org> wrote:
>
>> Hi Roberto,
>>
>> I can't reproduce the issue in both 7.0.x and 7.1.x with my patch applied,
>> it seems passing as expected:
>> [INFO]
>> [INFO] -------------------------------------------------------
>> [INFO]  T E S T S
>> [INFO] -------------------------------------------------------
>> [INFO] Running org.apache.tomee.TomEECliIT
>> Must specify either a plain text to encrypt or a ciphered value to decrypt.
>> usage: cipher [options] <value>
>>
>> Uses a password cipher implementation to encrypt/decrypt a value.
>>   -c,--cipher <c>   Specifies the password cipher implementation to use
>>                     (default is Static3DES).
>>   -d,--decrypt      Switches command line tool to decrypt.
>>   -e,--encrypt      Switches command line tool to encrypt (default).
>>   -h,--help         Lists these options and exits.
>>
>> Available ciphers are: cdi
>> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
>> 1.144 s - in org.apache.tomee.TomEECliIT
>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
>> Dec 19, 2018 6:52:57 PM org.apache.openejb.client.EventLogger log
>> INFO: RemoteInitialContextCreated{providerUri=
>> http://localhost:46355/tomee/ejb}
>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.25
>> s - in org.apache.tomee.RemoteTomEEEJBContainerIT
>> [INFO]
>> [INFO] Results:
>> [INFO]
>> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
>>
>>
>> Is possible to trigger build from buildbot for my PR?
>>
>> Em qua, 19 de dez de 2018 às 11:36, Roberto Cortez
>> <ra...@yahoo.com.invalid> escreveu:
>>
>>> The CDI TCK runs after the OpenEJB Core, so you should be able to see the
>>> debug information you added.
>>>
>>> I’m not sure if you noticed it, but I did add a @Ignore to the
>>> AutoConnectionTracker test until we figure out what is wrong.
>>>
>>>> On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>
>>> wrote:
>>>> Roberto, I saw you commented the test in which I added some more stuff
>> to
>>>> test.
>>>> Do you have some inputs after the run?
>>>> Or are we still stuck on CDI ?
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org>
>>> wrote:
>>>>> I saw your comment and it's weird.
>>>>> I'll look it again, the patch should fix exactly the test which you
>> are
>>>>> getting error. :)
>>>>>
>>>>> Thanks for review.
>>>>>
>>>>> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>>
>>>>>> Hi Daniel,
>>>>>>
>>>>>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can
>> you
>>>>>> confirm? Left you a note in the PR’s.
>>>>>>
>>>>>> Cheers,
>>>>>> Roberto
>>>>>>
>>>>>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
>>>>> jlmonteiro@tomitribe.com>
>>>>>> wrote:
>>>>>>> I pushed some debugging information on the other test and I'll be
>>>>>>> monitoring the built
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <danielsoro@apache.org
>>>>>> wrote:
>>>>>>>> Nice... Thanks!
>>>>>>>>
>>>>>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
>>>>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>>>>>
>>>>>>>>> Hi Daniel,
>>>>>>>>> I didn't yet for the other branches. I'll do it today.
>>>>>>>>>    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
>>>>>>>>> danielsoro@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi Roberto,
>>>>>>>>>
>>>>>>>>> I saw that you merged the changes on master, did you see the
>> others
>>>>>>>> changes
>>>>>>>>> for branch 7.0.x and 7.1.x?
>>>>>>>>>
>>>>>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>>
>>>>>>>>>> Thank you Daniel,
>>>>>>>>>>
>>>>>>>>>> I’ll review and merge.
>>>>>>>>>>
>>>>>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
>>>>>> couple
>>>>>>>>> of
>>>>>>>>>> days before, but now it happened again. Not sure what is wrong
>>>>> there,
>>>>>>>>> since
>>>>>>>>>> we used to pass it.
>>>>>>>>>>
>>>>>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
>>>>> wrote:
>>>>>>>>>>> Hi Roberto,
>>>>>>>>>>>
>>>>>>>>>>> the fix which I send is to make sure that the test is using the
>>>>>>>> correct
>>>>>>>>>>> version for libs.
>>>>>>>>>>> For example, here
>>>>>>>>>>>
>> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
>>>>>>>>>>> we have the version of the lib on the code.
>>>>>>>>>>>
>>>>>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
>>>>>>>> works,
>>>>>>>>>>> because for that build, it will have openejb-core-7.0.x and not
>>>>>>>>>>> openejb-core-8.0.0-SNAPSHOT.
>>>>>>>>>>>
>>>>>>>>>>> That is the issue, we need to get the correct reference for the
>>> lib
>>>>>>>> to
>>>>>>>>>> make
>>>>>>>>>>> sure that the command will works.
>>>>>>>>>>>
>>>>>>>>>>> About the test stuck, reading the stacktrace that you send,
>> seems
>>>>>>>>>> something
>>>>>>>>>>> during TCK test. Is it?
>>>>>>>>>>>
>>>>>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
>>>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you please explain what the issue was?
>>>>>>>>>>>>
>>>>>>>>>>>> Also, it seems our build is getting killed for taking to long
>> due
>>>>> to
>>>>>>>>>> some
>>>>>>>>>>>> tests being stuck?
>>>>>>>>>>>>
>>>>>>>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb
>> }
>>>>>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
>>>>>>>> object
>>>>>>>>>> input
>>>>>>>>>>>> stream to server (OEJP/4.6) : null}
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
>>>>>>>>>> beforeInvocation
>>>>>>>>>>>> INFO: Invoke
>>>>>>>>>>>>
>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
>>>>>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>>>>>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
>>>>> deployed
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
>>>>>>>>>> build
>>>>>>>>>>>> INFO: Test archive built [info:
>>>>>>>>>>>>
>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
>>>>>>>>>>>> time: 16 ms]
>>>>>>>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> command timed out: 18000 seconds without output running ['mvn',
>>>>>>>> '-U',
>>>>>>>>>>>> '--show-version', '--fail-at-end',
>>>>>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
>>>>> 'install',
>>>>>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
>>>>>>>>> '-DdisableXmlReport=true',
>>>>>>>>>>>> '-Dopenejb.arquillian.debug=true',
>>>>>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>>>>>>>>>>>> process killed by signal 9
>>>>>>>>>>>> program finished with exit code -1
>>>>>>>>>>>> elapsedTime=38754.464253
>>>>>>>>>>>>
>>>>>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30
>> PM.
>>>>> No
>>>>>>>>>> logs
>>>>>>>>>>>> in between...
>>>>>>>>>>>>
>>>>>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <danielsoro@apache.org
>>>>>>>>> wrote:
>>>>>>>>>>>>> Hey folks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> we found an issue on TomEECliIT test.
>>>>>>>>>>>>> I've opened fixes for test in all branch, please take a look
>> on
>>>>> it.
>>>>>>>>>>>>> Fixes:
>>>>>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
>>>>>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>>>>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>>>>>>>>>>>>
>>>>>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>>>>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Please wait a minute lol
>>>>>>>>>>>>>> I'd rather have you help me if needed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> First I don't have the feeling I spent time for nothing on it
>>>>> and
>>>>>>>>>>>> second,
>>>>>>>>>>>>>> at least I will learn something.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>>>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help
>>> look
>>>>>>>>> into
>>>>>>>>>>>> it.
>>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It seems the build just randomly fails with this test:
>>>>>>>>>>>>>>>> AutoConnectionTrackerTest.test
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [ERROR] Failures:
>>>>>>>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1>
>> but
>>>>>>>>>> was:<0>
>>>>>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may
>> be
>>>>>>>>> related
>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m
>> running
>>>>> the
>>>>>>>>>> test
>>>>>>>>>>>>>> non
>>>>>>>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
>>>>>>>>>> replicate
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> issue:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any ideias?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> I'll take the first one first
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thank you JL,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> At least this test is failing:
>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> And this one seems to fail randomly.
>>>>>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full
>> build
>>>>>>>>>> locally.
>>>>>>>>>>>>>>> I'll
>>>>>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
>>>>> first
>>>>>>>>>> here
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hey Jon,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The following commit:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>>>>>>>>
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>>>>> Is failing the test:
>>>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Can you help?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
>>>>> kamin.feuer.2000@gmx.de
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the information
>>> on
>>>>>>>> IRC
>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Frankie
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Sent from:
>>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>> https://twitter.com/dvlc_
>>>>>>
>>>
>> --
>> Daniel "soro" Cunha
>> https://twitter.com/dvlc_
>>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

OK, I think I fixed everything but the mp-rest-jwt-jwk example that I'm
going to start working on now

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 14, 2019 at 1:33 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> The build is now running and tests executing. I'll monitor and try to fix
> the rest.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jan 14, 2019 at 10:28 AM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> Just saw there are some checkstyle issues. Working on it.
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, Jan 7, 2019 at 3:56 PM César Hernández Mendoza <
>> cesarguate@gmail.com> wrote:
>>
>>> >
>>> > one suggestion was for committers to be able to kick off builds using a
>>> > specific commit hash, rather than automatically for each PR.
>>>
>>> My only observation about it is that this will require a non commiter to
>>> send an email to the dev list to request kick builds before actually
>>> sending the "Please review" email.
>>>
>>> could offer a nice balance - enable shorter cycles with CI builds, but
>>> not
>>> > consuming vast amounts of resource with PRs that might not be ready.
>>>
>>>
>>> +1, because we don't want to waste resource on WIP PRs.
>>>
>>> El lun., 7 ene. 2019 a las 5:58, Jonathan Gallimore (<
>>> jonathan.gallimore@gmail.com>) escribió:
>>>
>>> > A couple of updates on this. I have a Jenkins install at home, which
>>> now
>>> > runs master with 5 test failures that we don't see on buildbot, so I
>>> don't
>>> > think there is technically much that holds us back from using Jenkins
>>> over
>>> > something else.
>>> >
>>> > In terms of PR building, there's an interesting discussion on
>>> > builds@apache.org. going on right now:
>>> >
>>> >
>>> https://lists.apache.org/thread.html/fa6332c09cb0de56c7f9c88af794edb4f86f1b54734c6bf21c0faf6c@%3Cbuilds.apache.org%3E
>>> > - one suggestion was for committers to be able to kick off builds
>>> using a
>>> > specific commit hash, rather than automatically for each PR. I thought
>>> that
>>> > could offer a nice balance - enable shorter cycles with CI builds, but
>>> not
>>> > consuming vast amounts of resource with PRs that might not be ready.
>>> >
>>> > Jon
>>> >
>>> > On Mon, Jan 7, 2019 at 11:33 AM Ivan Junckes Filho <
>>> ivanjunckes@gmail.com>
>>> > wrote:
>>> >
>>> > > On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
>>> > > jonathan.gallimore@gmail.com> wrote:
>>> > >
>>> > > > On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <
>>> > ivanjunckes@gmail.com
>>> > > >
>>> > > > wrote:
>>> > > >
>>> > > > > Hey guys, can someone provide me the way to check if my PR is
>>> green?
>>> > > > >
>>> > > >
>>> > > > Yep, run the build on your branch :-). I run builds on PRs when I
>>> > review
>>> > > > them. If you don't want to run the full build, you could run tests
>>> that
>>> > > are
>>> > > > relevant to your change. If you need guidance on possible impacts
>>> of a
>>> > > PR,
>>> > > > please ask :).
>>> > > >
>>> > > I know, just thought would be cool to have it on github so it is
>>> > available
>>> > > for whoever will review the PR and others to see.
>>> > >
>>> > > >
>>> > > > Also, I wouldn't be scared of things being merged in and the build
>>> > > > breaking. The key thing is to check it, and help fix it if there
>>> is a
>>> > > > problem. The current CI builds on buildbot are available from here:
>>> > > > https://ci.apache.org/buildbot.html
>>> > > >
>>> > > > Thanks for the url.
>>> > >
>>> > > >
>>> > > > > Also, now that apache has migrated to gitbox, is there a way to
>>> > > integrate
>>> > > > > the build with github?
>>> > > > >
>>> > > >
>>> > > > This wasn't a pre-requisite of being able to build PRs on a CI. If
>>> > > someone
>>> > > > wants to have a go at setting up something to run against PRs on
>>> Travis
>>> > > or
>>> > > > on ASF infrastructure, please do go for it. Its not something we
>>> can
>>> > just
>>> > > > "switch on" though I'm afraid. We do also need to be mindful that
>>> we
>>> > have
>>> > > > 27 open PRs and a build that takes 5 hours to run fully - so if we
>>> do
>>> > > setup
>>> > > > something like this, it will consume a fair bit of resource.
>>> > > >
>>> > > Jon
>>> > > >
>>> > > > I see your point, makes sense.
>>> > >
>>> > > >
>>> > > > >
>>> > > > > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
>>> > > > > jlmonteiro@tomitribe.com> wrote:
>>> > > > >
>>> > > > > > That'd be great indeed
>>> > > > > >
>>> > > > > > --
>>> > > > > > Jean-Louis Monteiro
>>> > > > > > http://twitter.com/jlouismonteiro
>>> > > > > > http://www.tomitribe.com
>>> > > > > >
>>> > > > > >
>>> > > > > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
>>> > > > > <radcortez@yahoo.com.invalid
>>> > > > > > >
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > > > Maybe Bruno would like to work on that, since he is heavily
>>> > > involved
>>> > > > > with
>>> > > > > > > the EG and he did the integration for the last version?
>>> > > > > > >
>>> > > > > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
>>> > > > > jlmonteiro@tomitribe.com
>>> > > > > > >
>>> > > > > > > wrote:
>>> > > > > > > >
>>> > > > > > > > Ok, looks like the build is back to stable.
>>> > > > > > > > There are 2 other votes currently. I'll do an update when
>>> the
>>> > > vote
>>> > > > is
>>> > > > > > > > closed.
>>> > > > > > > >
>>> > > > > > > > Meanwhile, we need an action plan for fault tolerance. We
>>> need
>>> > to
>>> > > > > > > > investigate what happened or if we need to rework the
>>> > > integration.
>>> > > > > > > >
>>> > > > > > > > --
>>> > > > > > > > Jean-Louis Monteiro
>>> > > > > > > > http://twitter.com/jlouismonteiro
>>> > > > > > > > http://www.tomitribe.com
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <
>>> > > brunobat@gmail.com>
>>> > > > > > > wrote:
>>> > > > > > > >
>>> > > > > > > >> I think there's a vote for a minor release fixing an issue
>>> > > there.
>>> > > > > > > >>
>>> > > > > > > >> Bruno Baptista
>>> > > > > > > >> https://twitter.com/brunobat_
>>> > > > > > > >>
>>> > > > > > > >>
>>> > > > > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
>>> > > > > > > >>> The OpenTracing update was also failing the TCK. I’ve
>>> > reverted
>>> > > it
>>> > > > > > back
>>> > > > > > > >> until we figure out what is going on.
>>> > > > > > > >>>
>>> > > > > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
>>> > > > > <radcortez@yahoo.com.INVALID
>>> > > > > > >
>>> > > > > > > >> wrote:
>>> > > > > > > >>>>
>>> > > > > > > >>>> It seems to fail intermittently. It took me a few tries
>>> to
>>> > > make
>>> > > > it
>>> > > > > > > >> fail. On the latest buildbot it seems fine.
>>> > > > > > > >>>>
>>> > > > > > > >>>> Not sure if it was like this before or if it was
>>> something
>>> > we
>>> > > > did.
>>> > > > > > > >>>>
>>> > > > > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
>>> > > > > > > jlmonteiro@tomitribe.com>
>>> > > > > > > >> wrote:
>>> > > > > > > >>>>>
>>> > > > > > > >>>>> [ERROR] Failures:
>>> > > > > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219
>>> Bad
>>> > > > number
>>> > > > > > of
>>> > > > > > > >>>>> invocations for the bean "green". expected:<2> but
>>> was:<1>
>>> > > > > > > >>>>>
>>> > > > > > > >>>>> --
>>> > > > > > > >>>>> Jean-Louis Monteiro
>>> > > > > > > >>>>> http://twitter.com/jlouismonteiro
>>> > > > > > > >>>>> http://www.tomitribe.com
>>> > > > > > > >>>>>
>>> > > > > > > >>>>>
>>> > > > > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
>>> > > > > > > >> jlmonteiro@tomitribe.com>
>>> > > > > > > >>>>> wrote:
>>> > > > > > > >>>>>
>>> > > > > > > >>>>>> I also get this one locally
>>> > > > > > > >>>>>>
>>> > > > > > > >>>>>> --
>>> > > > > > > >>>>>> Jean-Louis Monteiro
>>> > > > > > > >>>>>> http://twitter.com/jlouismonteiro
>>> > > > > > > >>>>>> http://www.tomitribe.com
>>> > > > > > > >>>>>>
>>> > > > > > > >>>>>>
>>> > > > > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
>>> > > > > > > >> <ra...@yahoo.com.invalid>
>>> > > > > > > >>>>>> wrote:
>>> > > > > > > >>>>>>
>>> > > > > > > >>>>>>> One issue at least was with the Safeguard upgrade.
>>> I’ve
>>> > > > > reverted
>>> > > > > > it
>>> > > > > > > >> back.
>>> > > > > > > >>>>>>> Lets see if this helps.
>>> > > > > > > >>>>>>>
>>> > > > > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
>>> > > > > > > <radcortez@yahoo.com.INVALID
>>> > > > > > > >>>
>>> > > > > > > >>>>>>> wrote:
>>> > > > > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a
>>> > message
>>> > > > > too.
>>> > > > > > I
>>> > > > > > > >> can
>>> > > > > > > >>>>>>> have a look.
>>> > > > > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
>>> > > > > > > >> jlmonteiro@tomitribe.com>
>>> > > > > > > >>>>>>> wrote:
>>> > > > > > > >>>>>>>>> Ok, looks like we are back to red.
>>> > > > > > > >>>>>>>>> Someone working on it?
>>> > > > > > > >>>>>>>>> --
>>> > > > > > > >>>>>>>>> Jean-Louis Monteiro
>>> > > > > > > >>>>>>>>> http://twitter.com/jlouismonteiro
>>> > > > > > > >>>>>>>>> http://www.tomitribe.com
>>> > > > > > > >>>>>>>>>
>>> > > > > > > >>>>>>>>>
>>> > > > > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>>> > > > > > > >>>>>>> <ra...@yahoo.com.invalid>
>>> > > > > > > >>>>>>>>> wrote:
>>> > > > > > > >>>>>>>>>
>>> > > > > > > >>>>>>>>>> By the way, lets try to keep it that way :)
>>> > > > > > > >>>>>>>>>>
>>> > > > > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández
>>> Mendoza <
>>> > > > > > > >>>>>>> cesarguate@gmail.com>
>>> > > > > > > >>>>>>>>>> wrote:
>>> > > > > > > >>>>>>>>>>> Nice work guys!
>>> > > > > > > >>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
>>> > > > > > > >> kamin.feuer.2000@gmx.de
>>> > > > > > > >>>>>>>> )
>>> > > > > > > >>>>>>>>>>> escribió:
>>> > > > > > > >>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>> Great! Well Done!
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>> Frankie
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>> --
>>> > > > > > > >>>>>>>>>>>> Sent from:
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>
>>> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>> > > > > > > >>>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>>
>>> > > > > > > >>>>>>>>>>> --
>>> > > > > > > >>>>>>>>>>> Atentamente:
>>> > > > > > > >>>>>>>>>>> César Hernández Mendoza.
>>> > > > > > > >>>>>>>>>>
>>> > > > > > > >>>>>>>
>>> > > > > > > >>
>>> > > > > > >
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>>
>>> --
>>> Atentamente:
>>> César Hernández Mendoza.
>>>
>>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

The build is now running and tests executing. I'll monitor and try to fix
the rest.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 14, 2019 at 10:28 AM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> Just saw there are some checkstyle issues. Working on it.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Jan 7, 2019 at 3:56 PM César Hernández Mendoza <
> cesarguate@gmail.com> wrote:
>
>> >
>> > one suggestion was for committers to be able to kick off builds using a
>> > specific commit hash, rather than automatically for each PR.
>>
>> My only observation about it is that this will require a non commiter to
>> send an email to the dev list to request kick builds before actually
>> sending the "Please review" email.
>>
>> could offer a nice balance - enable shorter cycles with CI builds, but not
>> > consuming vast amounts of resource with PRs that might not be ready.
>>
>>
>> +1, because we don't want to waste resource on WIP PRs.
>>
>> El lun., 7 ene. 2019 a las 5:58, Jonathan Gallimore (<
>> jonathan.gallimore@gmail.com>) escribió:
>>
>> > A couple of updates on this. I have a Jenkins install at home, which now
>> > runs master with 5 test failures that we don't see on buildbot, so I
>> don't
>> > think there is technically much that holds us back from using Jenkins
>> over
>> > something else.
>> >
>> > In terms of PR building, there's an interesting discussion on
>> > builds@apache.org. going on right now:
>> >
>> >
>> https://lists.apache.org/thread.html/fa6332c09cb0de56c7f9c88af794edb4f86f1b54734c6bf21c0faf6c@%3Cbuilds.apache.org%3E
>> > - one suggestion was for committers to be able to kick off builds using
>> a
>> > specific commit hash, rather than automatically for each PR. I thought
>> that
>> > could offer a nice balance - enable shorter cycles with CI builds, but
>> not
>> > consuming vast amounts of resource with PRs that might not be ready.
>> >
>> > Jon
>> >
>> > On Mon, Jan 7, 2019 at 11:33 AM Ivan Junckes Filho <
>> ivanjunckes@gmail.com>
>> > wrote:
>> >
>> > > On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
>> > > jonathan.gallimore@gmail.com> wrote:
>> > >
>> > > > On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <
>> > ivanjunckes@gmail.com
>> > > >
>> > > > wrote:
>> > > >
>> > > > > Hey guys, can someone provide me the way to check if my PR is
>> green?
>> > > > >
>> > > >
>> > > > Yep, run the build on your branch :-). I run builds on PRs when I
>> > review
>> > > > them. If you don't want to run the full build, you could run tests
>> that
>> > > are
>> > > > relevant to your change. If you need guidance on possible impacts
>> of a
>> > > PR,
>> > > > please ask :).
>> > > >
>> > > I know, just thought would be cool to have it on github so it is
>> > available
>> > > for whoever will review the PR and others to see.
>> > >
>> > > >
>> > > > Also, I wouldn't be scared of things being merged in and the build
>> > > > breaking. The key thing is to check it, and help fix it if there is
>> a
>> > > > problem. The current CI builds on buildbot are available from here:
>> > > > https://ci.apache.org/buildbot.html
>> > > >
>> > > > Thanks for the url.
>> > >
>> > > >
>> > > > > Also, now that apache has migrated to gitbox, is there a way to
>> > > integrate
>> > > > > the build with github?
>> > > > >
>> > > >
>> > > > This wasn't a pre-requisite of being able to build PRs on a CI. If
>> > > someone
>> > > > wants to have a go at setting up something to run against PRs on
>> Travis
>> > > or
>> > > > on ASF infrastructure, please do go for it. Its not something we can
>> > just
>> > > > "switch on" though I'm afraid. We do also need to be mindful that we
>> > have
>> > > > 27 open PRs and a build that takes 5 hours to run fully - so if we
>> do
>> > > setup
>> > > > something like this, it will consume a fair bit of resource.
>> > > >
>> > > Jon
>> > > >
>> > > > I see your point, makes sense.
>> > >
>> > > >
>> > > > >
>> > > > > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
>> > > > > jlmonteiro@tomitribe.com> wrote:
>> > > > >
>> > > > > > That'd be great indeed
>> > > > > >
>> > > > > > --
>> > > > > > Jean-Louis Monteiro
>> > > > > > http://twitter.com/jlouismonteiro
>> > > > > > http://www.tomitribe.com
>> > > > > >
>> > > > > >
>> > > > > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
>> > > > > <radcortez@yahoo.com.invalid
>> > > > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Maybe Bruno would like to work on that, since he is heavily
>> > > involved
>> > > > > with
>> > > > > > > the EG and he did the integration for the last version?
>> > > > > > >
>> > > > > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
>> > > > > jlmonteiro@tomitribe.com
>> > > > > > >
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > Ok, looks like the build is back to stable.
>> > > > > > > > There are 2 other votes currently. I'll do an update when
>> the
>> > > vote
>> > > > is
>> > > > > > > > closed.
>> > > > > > > >
>> > > > > > > > Meanwhile, we need an action plan for fault tolerance. We
>> need
>> > to
>> > > > > > > > investigate what happened or if we need to rework the
>> > > integration.
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Jean-Louis Monteiro
>> > > > > > > > http://twitter.com/jlouismonteiro
>> > > > > > > > http://www.tomitribe.com
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <
>> > > brunobat@gmail.com>
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > >> I think there's a vote for a minor release fixing an issue
>> > > there.
>> > > > > > > >>
>> > > > > > > >> Bruno Baptista
>> > > > > > > >> https://twitter.com/brunobat_
>> > > > > > > >>
>> > > > > > > >>
>> > > > > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
>> > > > > > > >>> The OpenTracing update was also failing the TCK. I’ve
>> > reverted
>> > > it
>> > > > > > back
>> > > > > > > >> until we figure out what is going on.
>> > > > > > > >>>
>> > > > > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
>> > > > > <radcortez@yahoo.com.INVALID
>> > > > > > >
>> > > > > > > >> wrote:
>> > > > > > > >>>>
>> > > > > > > >>>> It seems to fail intermittently. It took me a few tries
>> to
>> > > make
>> > > > it
>> > > > > > > >> fail. On the latest buildbot it seems fine.
>> > > > > > > >>>>
>> > > > > > > >>>> Not sure if it was like this before or if it was
>> something
>> > we
>> > > > did.
>> > > > > > > >>>>
>> > > > > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
>> > > > > > > jlmonteiro@tomitribe.com>
>> > > > > > > >> wrote:
>> > > > > > > >>>>>
>> > > > > > > >>>>> [ERROR] Failures:
>> > > > > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219
>> Bad
>> > > > number
>> > > > > > of
>> > > > > > > >>>>> invocations for the bean "green". expected:<2> but
>> was:<1>
>> > > > > > > >>>>>
>> > > > > > > >>>>> --
>> > > > > > > >>>>> Jean-Louis Monteiro
>> > > > > > > >>>>> http://twitter.com/jlouismonteiro
>> > > > > > > >>>>> http://www.tomitribe.com
>> > > > > > > >>>>>
>> > > > > > > >>>>>
>> > > > > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
>> > > > > > > >> jlmonteiro@tomitribe.com>
>> > > > > > > >>>>> wrote:
>> > > > > > > >>>>>
>> > > > > > > >>>>>> I also get this one locally
>> > > > > > > >>>>>>
>> > > > > > > >>>>>> --
>> > > > > > > >>>>>> Jean-Louis Monteiro
>> > > > > > > >>>>>> http://twitter.com/jlouismonteiro
>> > > > > > > >>>>>> http://www.tomitribe.com
>> > > > > > > >>>>>>
>> > > > > > > >>>>>>
>> > > > > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
>> > > > > > > >> <ra...@yahoo.com.invalid>
>> > > > > > > >>>>>> wrote:
>> > > > > > > >>>>>>
>> > > > > > > >>>>>>> One issue at least was with the Safeguard upgrade.
>> I’ve
>> > > > > reverted
>> > > > > > it
>> > > > > > > >> back.
>> > > > > > > >>>>>>> Lets see if this helps.
>> > > > > > > >>>>>>>
>> > > > > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
>> > > > > > > <radcortez@yahoo.com.INVALID
>> > > > > > > >>>
>> > > > > > > >>>>>>> wrote:
>> > > > > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a
>> > message
>> > > > > too.
>> > > > > > I
>> > > > > > > >> can
>> > > > > > > >>>>>>> have a look.
>> > > > > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
>> > > > > > > >> jlmonteiro@tomitribe.com>
>> > > > > > > >>>>>>> wrote:
>> > > > > > > >>>>>>>>> Ok, looks like we are back to red.
>> > > > > > > >>>>>>>>> Someone working on it?
>> > > > > > > >>>>>>>>> --
>> > > > > > > >>>>>>>>> Jean-Louis Monteiro
>> > > > > > > >>>>>>>>> http://twitter.com/jlouismonteiro
>> > > > > > > >>>>>>>>> http://www.tomitribe.com
>> > > > > > > >>>>>>>>>
>> > > > > > > >>>>>>>>>
>> > > > > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>> > > > > > > >>>>>>> <ra...@yahoo.com.invalid>
>> > > > > > > >>>>>>>>> wrote:
>> > > > > > > >>>>>>>>>
>> > > > > > > >>>>>>>>>> By the way, lets try to keep it that way :)
>> > > > > > > >>>>>>>>>>
>> > > > > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza
>> <
>> > > > > > > >>>>>>> cesarguate@gmail.com>
>> > > > > > > >>>>>>>>>> wrote:
>> > > > > > > >>>>>>>>>>> Nice work guys!
>> > > > > > > >>>>>>>>>>>
>> > > > > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
>> > > > > > > >> kamin.feuer.2000@gmx.de
>> > > > > > > >>>>>>>> )
>> > > > > > > >>>>>>>>>>> escribió:
>> > > > > > > >>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>> Great! Well Done!
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>> Frankie
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>> --
>> > > > > > > >>>>>>>>>>>> Sent from:
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>
>> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> > > > > > > >>>>>>>>>>>>
>> > > > > > > >>>>>>>>>>>
>> > > > > > > >>>>>>>>>>> --
>> > > > > > > >>>>>>>>>>> Atentamente:
>> > > > > > > >>>>>>>>>>> César Hernández Mendoza.
>> > > > > > > >>>>>>>>>>
>> > > > > > > >>>>>>>
>> > > > > > > >>
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>>
>> --
>> Atentamente:
>> César Hernández Mendoza.
>>
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Just saw there are some checkstyle issues. Working on it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Jan 7, 2019 at 3:56 PM César Hernández Mendoza <ce...@gmail.com>
wrote:

> >
> > one suggestion was for committers to be able to kick off builds using a
> > specific commit hash, rather than automatically for each PR.
>
> My only observation about it is that this will require a non commiter to
> send an email to the dev list to request kick builds before actually
> sending the "Please review" email.
>
> could offer a nice balance - enable shorter cycles with CI builds, but not
> > consuming vast amounts of resource with PRs that might not be ready.
>
>
> +1, because we don't want to waste resource on WIP PRs.
>
> El lun., 7 ene. 2019 a las 5:58, Jonathan Gallimore (<
> jonathan.gallimore@gmail.com>) escribió:
>
> > A couple of updates on this. I have a Jenkins install at home, which now
> > runs master with 5 test failures that we don't see on buildbot, so I
> don't
> > think there is technically much that holds us back from using Jenkins
> over
> > something else.
> >
> > In terms of PR building, there's an interesting discussion on
> > builds@apache.org. going on right now:
> >
> >
> https://lists.apache.org/thread.html/fa6332c09cb0de56c7f9c88af794edb4f86f1b54734c6bf21c0faf6c@%3Cbuilds.apache.org%3E
> > - one suggestion was for committers to be able to kick off builds using a
> > specific commit hash, rather than automatically for each PR. I thought
> that
> > could offer a nice balance - enable shorter cycles with CI builds, but
> not
> > consuming vast amounts of resource with PRs that might not be ready.
> >
> > Jon
> >
> > On Mon, Jan 7, 2019 at 11:33 AM Ivan Junckes Filho <
> ivanjunckes@gmail.com>
> > wrote:
> >
> > > On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> wrote:
> > >
> > > > On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <
> > ivanjunckes@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hey guys, can someone provide me the way to check if my PR is
> green?
> > > > >
> > > >
> > > > Yep, run the build on your branch :-). I run builds on PRs when I
> > review
> > > > them. If you don't want to run the full build, you could run tests
> that
> > > are
> > > > relevant to your change. If you need guidance on possible impacts of
> a
> > > PR,
> > > > please ask :).
> > > >
> > > I know, just thought would be cool to have it on github so it is
> > available
> > > for whoever will review the PR and others to see.
> > >
> > > >
> > > > Also, I wouldn't be scared of things being merged in and the build
> > > > breaking. The key thing is to check it, and help fix it if there is a
> > > > problem. The current CI builds on buildbot are available from here:
> > > > https://ci.apache.org/buildbot.html
> > > >
> > > > Thanks for the url.
> > >
> > > >
> > > > > Also, now that apache has migrated to gitbox, is there a way to
> > > integrate
> > > > > the build with github?
> > > > >
> > > >
> > > > This wasn't a pre-requisite of being able to build PRs on a CI. If
> > > someone
> > > > wants to have a go at setting up something to run against PRs on
> Travis
> > > or
> > > > on ASF infrastructure, please do go for it. Its not something we can
> > just
> > > > "switch on" though I'm afraid. We do also need to be mindful that we
> > have
> > > > 27 open PRs and a build that takes 5 hours to run fully - so if we do
> > > setup
> > > > something like this, it will consume a fair bit of resource.
> > > >
> > > Jon
> > > >
> > > > I see your point, makes sense.
> > >
> > > >
> > > > >
> > > > > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
> > > > > jlmonteiro@tomitribe.com> wrote:
> > > > >
> > > > > > That'd be great indeed
> > > > > >
> > > > > > --
> > > > > > Jean-Louis Monteiro
> > > > > > http://twitter.com/jlouismonteiro
> > > > > > http://www.tomitribe.com
> > > > > >
> > > > > >
> > > > > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
> > > > > <radcortez@yahoo.com.invalid
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Maybe Bruno would like to work on that, since he is heavily
> > > involved
> > > > > with
> > > > > > > the EG and he did the integration for the last version?
> > > > > > >
> > > > > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
> > > > > jlmonteiro@tomitribe.com
> > > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Ok, looks like the build is back to stable.
> > > > > > > > There are 2 other votes currently. I'll do an update when the
> > > vote
> > > > is
> > > > > > > > closed.
> > > > > > > >
> > > > > > > > Meanwhile, we need an action plan for fault tolerance. We
> need
> > to
> > > > > > > > investigate what happened or if we need to rework the
> > > integration.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Jean-Louis Monteiro
> > > > > > > > http://twitter.com/jlouismonteiro
> > > > > > > > http://www.tomitribe.com
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <
> > > brunobat@gmail.com>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> I think there's a vote for a minor release fixing an issue
> > > there.
> > > > > > > >>
> > > > > > > >> Bruno Baptista
> > > > > > > >> https://twitter.com/brunobat_
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > > > > > > >>> The OpenTracing update was also failing the TCK. I’ve
> > reverted
> > > it
> > > > > > back
> > > > > > > >> until we figure out what is going on.
> > > > > > > >>>
> > > > > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
> > > > > <radcortez@yahoo.com.INVALID
> > > > > > >
> > > > > > > >> wrote:
> > > > > > > >>>>
> > > > > > > >>>> It seems to fail intermittently. It took me a few tries to
> > > make
> > > > it
> > > > > > > >> fail. On the latest buildbot it seems fine.
> > > > > > > >>>>
> > > > > > > >>>> Not sure if it was like this before or if it was something
> > we
> > > > did.
> > > > > > > >>>>
> > > > > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > > > > > > jlmonteiro@tomitribe.com>
> > > > > > > >> wrote:
> > > > > > > >>>>>
> > > > > > > >>>>> [ERROR] Failures:
> > > > > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219
> Bad
> > > > number
> > > > > > of
> > > > > > > >>>>> invocations for the bean "green". expected:<2> but
> was:<1>
> > > > > > > >>>>>
> > > > > > > >>>>> --
> > > > > > > >>>>> Jean-Louis Monteiro
> > > > > > > >>>>> http://twitter.com/jlouismonteiro
> > > > > > > >>>>> http://www.tomitribe.com
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > > > > > > >> jlmonteiro@tomitribe.com>
> > > > > > > >>>>> wrote:
> > > > > > > >>>>>
> > > > > > > >>>>>> I also get this one locally
> > > > > > > >>>>>>
> > > > > > > >>>>>> --
> > > > > > > >>>>>> Jean-Louis Monteiro
> > > > > > > >>>>>> http://twitter.com/jlouismonteiro
> > > > > > > >>>>>> http://www.tomitribe.com
> > > > > > > >>>>>>
> > > > > > > >>>>>>
> > > > > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > > > > > > >> <ra...@yahoo.com.invalid>
> > > > > > > >>>>>> wrote:
> > > > > > > >>>>>>
> > > > > > > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve
> > > > > reverted
> > > > > > it
> > > > > > > >> back.
> > > > > > > >>>>>>> Lets see if this helps.
> > > > > > > >>>>>>>
> > > > > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > > > > > > <radcortez@yahoo.com.INVALID
> > > > > > > >>>
> > > > > > > >>>>>>> wrote:
> > > > > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a
> > message
> > > > > too.
> > > > > > I
> > > > > > > >> can
> > > > > > > >>>>>>> have a look.
> > > > > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > > > > > > >> jlmonteiro@tomitribe.com>
> > > > > > > >>>>>>> wrote:
> > > > > > > >>>>>>>>> Ok, looks like we are back to red.
> > > > > > > >>>>>>>>> Someone working on it?
> > > > > > > >>>>>>>>> --
> > > > > > > >>>>>>>>> Jean-Louis Monteiro
> > > > > > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > > > > > >>>>>>>>> http://www.tomitribe.com
> > > > > > > >>>>>>>>>
> > > > > > > >>>>>>>>>
> > > > > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > > > > > > >>>>>>> <ra...@yahoo.com.invalid>
> > > > > > > >>>>>>>>> wrote:
> > > > > > > >>>>>>>>>
> > > > > > > >>>>>>>>>> By the way, lets try to keep it that way :)
> > > > > > > >>>>>>>>>>
> > > > > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > > > > > > >>>>>>> cesarguate@gmail.com>
> > > > > > > >>>>>>>>>> wrote:
> > > > > > > >>>>>>>>>>> Nice work guys!
> > > > > > > >>>>>>>>>>>
> > > > > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > > > > > > >> kamin.feuer.2000@gmx.de
> > > > > > > >>>>>>>> )
> > > > > > > >>>>>>>>>>> escribió:
> > > > > > > >>>>>>>>>>>
> > > > > > > >>>>>>>>>>>> Great! Well Done!
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>>>>>>>>>>> Frankie
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>>>>>>>>>>> --
> > > > > > > >>>>>>>>>>>> Sent from:
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>
> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > > > > >>>>>>>>>>>>
> > > > > > > >>>>>>>>>>>
> > > > > > > >>>>>>>>>>> --
> > > > > > > >>>>>>>>>>> Atentamente:
> > > > > > > >>>>>>>>>>> César Hernández Mendoza.
> > > > > > > >>>>>>>>>>
> > > > > > > >>>>>>>
> > > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
> --
> Atentamente:
> César Hernández Mendoza.
>

Re: Stabilize TomEE Build

[César Hernández Mendoza <ce...@gmail.com>]

>
> one suggestion was for committers to be able to kick off builds using a
> specific commit hash, rather than automatically for each PR.

My only observation about it is that this will require a non commiter to
send an email to the dev list to request kick builds before actually
sending the "Please review" email.

could offer a nice balance - enable shorter cycles with CI builds, but not
> consuming vast amounts of resource with PRs that might not be ready.


+1, because we don't want to waste resource on WIP PRs.

El lun., 7 ene. 2019 a las 5:58, Jonathan Gallimore (<
jonathan.gallimore@gmail.com>) escribió:

> A couple of updates on this. I have a Jenkins install at home, which now
> runs master with 5 test failures that we don't see on buildbot, so I don't
> think there is technically much that holds us back from using Jenkins over
> something else.
>
> In terms of PR building, there's an interesting discussion on
> builds@apache.org. going on right now:
>
> https://lists.apache.org/thread.html/fa6332c09cb0de56c7f9c88af794edb4f86f1b54734c6bf21c0faf6c@%3Cbuilds.apache.org%3E
> - one suggestion was for committers to be able to kick off builds using a
> specific commit hash, rather than automatically for each PR. I thought that
> could offer a nice balance - enable shorter cycles with CI builds, but not
> consuming vast amounts of resource with PRs that might not be ready.
>
> Jon
>
> On Mon, Jan 7, 2019 at 11:33 AM Ivan Junckes Filho <iv...@gmail.com>
> wrote:
>
> > On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> > > On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <
> ivanjunckes@gmail.com
> > >
> > > wrote:
> > >
> > > > Hey guys, can someone provide me the way to check if my PR is green?
> > > >
> > >
> > > Yep, run the build on your branch :-). I run builds on PRs when I
> review
> > > them. If you don't want to run the full build, you could run tests that
> > are
> > > relevant to your change. If you need guidance on possible impacts of a
> > PR,
> > > please ask :).
> > >
> > I know, just thought would be cool to have it on github so it is
> available
> > for whoever will review the PR and others to see.
> >
> > >
> > > Also, I wouldn't be scared of things being merged in and the build
> > > breaking. The key thing is to check it, and help fix it if there is a
> > > problem. The current CI builds on buildbot are available from here:
> > > https://ci.apache.org/buildbot.html
> > >
> > > Thanks for the url.
> >
> > >
> > > > Also, now that apache has migrated to gitbox, is there a way to
> > integrate
> > > > the build with github?
> > > >
> > >
> > > This wasn't a pre-requisite of being able to build PRs on a CI. If
> > someone
> > > wants to have a go at setting up something to run against PRs on Travis
> > or
> > > on ASF infrastructure, please do go for it. Its not something we can
> just
> > > "switch on" though I'm afraid. We do also need to be mindful that we
> have
> > > 27 open PRs and a build that takes 5 hours to run fully - so if we do
> > setup
> > > something like this, it will consume a fair bit of resource.
> > >
> > Jon
> > >
> > > I see your point, makes sense.
> >
> > >
> > > >
> > > > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
> > > > jlmonteiro@tomitribe.com> wrote:
> > > >
> > > > > That'd be great indeed
> > > > >
> > > > > --
> > > > > Jean-Louis Monteiro
> > > > > http://twitter.com/jlouismonteiro
> > > > > http://www.tomitribe.com
> > > > >
> > > > >
> > > > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
> > > > <radcortez@yahoo.com.invalid
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Maybe Bruno would like to work on that, since he is heavily
> > involved
> > > > with
> > > > > > the EG and he did the integration for the last version?
> > > > > >
> > > > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
> > > > jlmonteiro@tomitribe.com
> > > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Ok, looks like the build is back to stable.
> > > > > > > There are 2 other votes currently. I'll do an update when the
> > vote
> > > is
> > > > > > > closed.
> > > > > > >
> > > > > > > Meanwhile, we need an action plan for fault tolerance. We need
> to
> > > > > > > investigate what happened or if we need to rework the
> > integration.
> > > > > > >
> > > > > > > --
> > > > > > > Jean-Louis Monteiro
> > > > > > > http://twitter.com/jlouismonteiro
> > > > > > > http://www.tomitribe.com
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <
> > brunobat@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > >> I think there's a vote for a minor release fixing an issue
> > there.
> > > > > > >>
> > > > > > >> Bruno Baptista
> > > > > > >> https://twitter.com/brunobat_
> > > > > > >>
> > > > > > >>
> > > > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > > > > > >>> The OpenTracing update was also failing the TCK. I’ve
> reverted
> > it
> > > > > back
> > > > > > >> until we figure out what is going on.
> > > > > > >>>
> > > > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
> > > > <radcortez@yahoo.com.INVALID
> > > > > >
> > > > > > >> wrote:
> > > > > > >>>>
> > > > > > >>>> It seems to fail intermittently. It took me a few tries to
> > make
> > > it
> > > > > > >> fail. On the latest buildbot it seems fine.
> > > > > > >>>>
> > > > > > >>>> Not sure if it was like this before or if it was something
> we
> > > did.
> > > > > > >>>>
> > > > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > > > > > jlmonteiro@tomitribe.com>
> > > > > > >> wrote:
> > > > > > >>>>>
> > > > > > >>>>> [ERROR] Failures:
> > > > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad
> > > number
> > > > > of
> > > > > > >>>>> invocations for the bean "green". expected:<2> but was:<1>
> > > > > > >>>>>
> > > > > > >>>>> --
> > > > > > >>>>> Jean-Louis Monteiro
> > > > > > >>>>> http://twitter.com/jlouismonteiro
> > > > > > >>>>> http://www.tomitribe.com
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > > > > > >> jlmonteiro@tomitribe.com>
> > > > > > >>>>> wrote:
> > > > > > >>>>>
> > > > > > >>>>>> I also get this one locally
> > > > > > >>>>>>
> > > > > > >>>>>> --
> > > > > > >>>>>> Jean-Louis Monteiro
> > > > > > >>>>>> http://twitter.com/jlouismonteiro
> > > > > > >>>>>> http://www.tomitribe.com
> > > > > > >>>>>>
> > > > > > >>>>>>
> > > > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > > > > > >> <ra...@yahoo.com.invalid>
> > > > > > >>>>>> wrote:
> > > > > > >>>>>>
> > > > > > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve
> > > > reverted
> > > > > it
> > > > > > >> back.
> > > > > > >>>>>>> Lets see if this helps.
> > > > > > >>>>>>>
> > > > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > > > > > <radcortez@yahoo.com.INVALID
> > > > > > >>>
> > > > > > >>>>>>> wrote:
> > > > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a
> message
> > > > too.
> > > > > I
> > > > > > >> can
> > > > > > >>>>>>> have a look.
> > > > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > > > > > >> jlmonteiro@tomitribe.com>
> > > > > > >>>>>>> wrote:
> > > > > > >>>>>>>>> Ok, looks like we are back to red.
> > > > > > >>>>>>>>> Someone working on it?
> > > > > > >>>>>>>>> --
> > > > > > >>>>>>>>> Jean-Louis Monteiro
> > > > > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > > > > >>>>>>>>> http://www.tomitribe.com
> > > > > > >>>>>>>>>
> > > > > > >>>>>>>>>
> > > > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > > > > > >>>>>>> <ra...@yahoo.com.invalid>
> > > > > > >>>>>>>>> wrote:
> > > > > > >>>>>>>>>
> > > > > > >>>>>>>>>> By the way, lets try to keep it that way :)
> > > > > > >>>>>>>>>>
> > > > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > > > > > >>>>>>> cesarguate@gmail.com>
> > > > > > >>>>>>>>>> wrote:
> > > > > > >>>>>>>>>>> Nice work guys!
> > > > > > >>>>>>>>>>>
> > > > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > > > > > >> kamin.feuer.2000@gmx.de
> > > > > > >>>>>>>> )
> > > > > > >>>>>>>>>>> escribió:
> > > > > > >>>>>>>>>>>
> > > > > > >>>>>>>>>>>> Great! Well Done!
> > > > > > >>>>>>>>>>>>
> > > > > > >>>>>>>>>>>> Frankie
> > > > > > >>>>>>>>>>>>
> > > > > > >>>>>>>>>>>>
> > > > > > >>>>>>>>>>>>
> > > > > > >>>>>>>>>>>> --
> > > > > > >>>>>>>>>>>> Sent from:
> > > > > > >>>>>>>>>>>>
> > > > > > >>
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > > > >>>>>>>>>>>>
> > > > > > >>>>>>>>>>>
> > > > > > >>>>>>>>>>> --
> > > > > > >>>>>>>>>>> Atentamente:
> > > > > > >>>>>>>>>>> César Hernández Mendoza.
> > > > > > >>>>>>>>>>
> > > > > > >>>>>>>
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


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

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

A couple of updates on this. I have a Jenkins install at home, which now
runs master with 5 test failures that we don't see on buildbot, so I don't
think there is technically much that holds us back from using Jenkins over
something else.

In terms of PR building, there's an interesting discussion on
builds@apache.org. going on right now:
https://lists.apache.org/thread.html/fa6332c09cb0de56c7f9c88af794edb4f86f1b54734c6bf21c0faf6c@%3Cbuilds.apache.org%3E
- one suggestion was for committers to be able to kick off builds using a
specific commit hash, rather than automatically for each PR. I thought that
could offer a nice balance - enable shorter cycles with CI builds, but not
consuming vast amounts of resource with PRs that might not be ready.

Jon

On Mon, Jan 7, 2019 at 11:33 AM Ivan Junckes Filho <iv...@gmail.com>
wrote:

> On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <ivanjunckes@gmail.com
> >
> > wrote:
> >
> > > Hey guys, can someone provide me the way to check if my PR is green?
> > >
> >
> > Yep, run the build on your branch :-). I run builds on PRs when I review
> > them. If you don't want to run the full build, you could run tests that
> are
> > relevant to your change. If you need guidance on possible impacts of a
> PR,
> > please ask :).
> >
> I know, just thought would be cool to have it on github so it is available
> for whoever will review the PR and others to see.
>
> >
> > Also, I wouldn't be scared of things being merged in and the build
> > breaking. The key thing is to check it, and help fix it if there is a
> > problem. The current CI builds on buildbot are available from here:
> > https://ci.apache.org/buildbot.html
> >
> > Thanks for the url.
>
> >
> > > Also, now that apache has migrated to gitbox, is there a way to
> integrate
> > > the build with github?
> > >
> >
> > This wasn't a pre-requisite of being able to build PRs on a CI. If
> someone
> > wants to have a go at setting up something to run against PRs on Travis
> or
> > on ASF infrastructure, please do go for it. Its not something we can just
> > "switch on" though I'm afraid. We do also need to be mindful that we have
> > 27 open PRs and a build that takes 5 hours to run fully - so if we do
> setup
> > something like this, it will consume a fair bit of resource.
> >
> Jon
> >
> > I see your point, makes sense.
>
> >
> > >
> > > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com> wrote:
> > >
> > > > That'd be great indeed
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
> > > <radcortez@yahoo.com.invalid
> > > > >
> > > > wrote:
> > > >
> > > > > Maybe Bruno would like to work on that, since he is heavily
> involved
> > > with
> > > > > the EG and he did the integration for the last version?
> > > > >
> > > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Ok, looks like the build is back to stable.
> > > > > > There are 2 other votes currently. I'll do an update when the
> vote
> > is
> > > > > > closed.
> > > > > >
> > > > > > Meanwhile, we need an action plan for fault tolerance. We need to
> > > > > > investigate what happened or if we need to rework the
> integration.
> > > > > >
> > > > > > --
> > > > > > Jean-Louis Monteiro
> > > > > > http://twitter.com/jlouismonteiro
> > > > > > http://www.tomitribe.com
> > > > > >
> > > > > >
> > > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <
> brunobat@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > >> I think there's a vote for a minor release fixing an issue
> there.
> > > > > >>
> > > > > >> Bruno Baptista
> > > > > >> https://twitter.com/brunobat_
> > > > > >>
> > > > > >>
> > > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > > > > >>> The OpenTracing update was also failing the TCK. I’ve reverted
> it
> > > > back
> > > > > >> until we figure out what is going on.
> > > > > >>>
> > > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
> > > <radcortez@yahoo.com.INVALID
> > > > >
> > > > > >> wrote:
> > > > > >>>>
> > > > > >>>> It seems to fail intermittently. It took me a few tries to
> make
> > it
> > > > > >> fail. On the latest buildbot it seems fine.
> > > > > >>>>
> > > > > >>>> Not sure if it was like this before or if it was something we
> > did.
> > > > > >>>>
> > > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > > > > jlmonteiro@tomitribe.com>
> > > > > >> wrote:
> > > > > >>>>>
> > > > > >>>>> [ERROR] Failures:
> > > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad
> > number
> > > > of
> > > > > >>>>> invocations for the bean "green". expected:<2> but was:<1>
> > > > > >>>>>
> > > > > >>>>> --
> > > > > >>>>> Jean-Louis Monteiro
> > > > > >>>>> http://twitter.com/jlouismonteiro
> > > > > >>>>> http://www.tomitribe.com
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > > > > >> jlmonteiro@tomitribe.com>
> > > > > >>>>> wrote:
> > > > > >>>>>
> > > > > >>>>>> I also get this one locally
> > > > > >>>>>>
> > > > > >>>>>> --
> > > > > >>>>>> Jean-Louis Monteiro
> > > > > >>>>>> http://twitter.com/jlouismonteiro
> > > > > >>>>>> http://www.tomitribe.com
> > > > > >>>>>>
> > > > > >>>>>>
> > > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > > > > >> <ra...@yahoo.com.invalid>
> > > > > >>>>>> wrote:
> > > > > >>>>>>
> > > > > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve
> > > reverted
> > > > it
> > > > > >> back.
> > > > > >>>>>>> Lets see if this helps.
> > > > > >>>>>>>
> > > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > > > > <radcortez@yahoo.com.INVALID
> > > > > >>>
> > > > > >>>>>>> wrote:
> > > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a message
> > > too.
> > > > I
> > > > > >> can
> > > > > >>>>>>> have a look.
> > > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > > > > >> jlmonteiro@tomitribe.com>
> > > > > >>>>>>> wrote:
> > > > > >>>>>>>>> Ok, looks like we are back to red.
> > > > > >>>>>>>>> Someone working on it?
> > > > > >>>>>>>>> --
> > > > > >>>>>>>>> Jean-Louis Monteiro
> > > > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > > > >>>>>>>>> http://www.tomitribe.com
> > > > > >>>>>>>>>
> > > > > >>>>>>>>>
> > > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > > > > >>>>>>> <ra...@yahoo.com.invalid>
> > > > > >>>>>>>>> wrote:
> > > > > >>>>>>>>>
> > > > > >>>>>>>>>> By the way, lets try to keep it that way :)
> > > > > >>>>>>>>>>
> > > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > > > > >>>>>>> cesarguate@gmail.com>
> > > > > >>>>>>>>>> wrote:
> > > > > >>>>>>>>>>> Nice work guys!
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > > > > >> kamin.feuer.2000@gmx.de
> > > > > >>>>>>>> )
> > > > > >>>>>>>>>>> escribió:
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>>> Great! Well Done!
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>> Frankie
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>> --
> > > > > >>>>>>>>>>>> Sent from:
> > > > > >>>>>>>>>>>>
> > > > > >>
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > > >>>>>>>>>>>>
> > > > > >>>>>>>>>>>
> > > > > >>>>>>>>>>> --
> > > > > >>>>>>>>>>> Atentamente:
> > > > > >>>>>>>>>>> César Hernández Mendoza.
> > > > > >>>>>>>>>>
> > > > > >>>>>>>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Stabilize TomEE Build

[Ivan Junckes Filho <iv...@gmail.com>]

On Fri, Jan 4, 2019 at 7:24 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <iv...@gmail.com>
> wrote:
>
> > Hey guys, can someone provide me the way to check if my PR is green?
> >
>
> Yep, run the build on your branch :-). I run builds on PRs when I review
> them. If you don't want to run the full build, you could run tests that are
> relevant to your change. If you need guidance on possible impacts of a PR,
> please ask :).
>
I know, just thought would be cool to have it on github so it is available
for whoever will review the PR and others to see.

>
> Also, I wouldn't be scared of things being merged in and the build
> breaking. The key thing is to check it, and help fix it if there is a
> problem. The current CI builds on buildbot are available from here:
> https://ci.apache.org/buildbot.html
>
> Thanks for the url.

>
> > Also, now that apache has migrated to gitbox, is there a way to integrate
> > the build with github?
> >
>
> This wasn't a pre-requisite of being able to build PRs on a CI. If someone
> wants to have a go at setting up something to run against PRs on Travis or
> on ASF infrastructure, please do go for it. Its not something we can just
> "switch on" though I'm afraid. We do also need to be mindful that we have
> 27 open PRs and a build that takes 5 hours to run fully - so if we do setup
> something like this, it will consume a fair bit of resource.
>
Jon
>
> I see your point, makes sense.

>
> >
> > On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> > > That'd be great indeed
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
> > <radcortez@yahoo.com.invalid
> > > >
> > > wrote:
> > >
> > > > Maybe Bruno would like to work on that, since he is heavily involved
> > with
> > > > the EG and he did the integration for the last version?
> > > >
> > > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com
> > > >
> > > > wrote:
> > > > >
> > > > > Ok, looks like the build is back to stable.
> > > > > There are 2 other votes currently. I'll do an update when the vote
> is
> > > > > closed.
> > > > >
> > > > > Meanwhile, we need an action plan for fault tolerance. We need to
> > > > > investigate what happened or if we need to rework the integration.
> > > > >
> > > > > --
> > > > > Jean-Louis Monteiro
> > > > > http://twitter.com/jlouismonteiro
> > > > > http://www.tomitribe.com
> > > > >
> > > > >
> > > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> I think there's a vote for a minor release fixing an issue there.
> > > > >>
> > > > >> Bruno Baptista
> > > > >> https://twitter.com/brunobat_
> > > > >>
> > > > >>
> > > > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > > > >>> The OpenTracing update was also failing the TCK. I’ve reverted it
> > > back
> > > > >> until we figure out what is going on.
> > > > >>>
> > > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
> > <radcortez@yahoo.com.INVALID
> > > >
> > > > >> wrote:
> > > > >>>>
> > > > >>>> It seems to fail intermittently. It took me a few tries to make
> it
> > > > >> fail. On the latest buildbot it seems fine.
> > > > >>>>
> > > > >>>> Not sure if it was like this before or if it was something we
> did.
> > > > >>>>
> > > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > > > jlmonteiro@tomitribe.com>
> > > > >> wrote:
> > > > >>>>>
> > > > >>>>> [ERROR] Failures:
> > > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad
> number
> > > of
> > > > >>>>> invocations for the bean "green". expected:<2> but was:<1>
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> Jean-Louis Monteiro
> > > > >>>>> http://twitter.com/jlouismonteiro
> > > > >>>>> http://www.tomitribe.com
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > > > >> jlmonteiro@tomitribe.com>
> > > > >>>>> wrote:
> > > > >>>>>
> > > > >>>>>> I also get this one locally
> > > > >>>>>>
> > > > >>>>>> --
> > > > >>>>>> Jean-Louis Monteiro
> > > > >>>>>> http://twitter.com/jlouismonteiro
> > > > >>>>>> http://www.tomitribe.com
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > > > >> <ra...@yahoo.com.invalid>
> > > > >>>>>> wrote:
> > > > >>>>>>
> > > > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve
> > reverted
> > > it
> > > > >> back.
> > > > >>>>>>> Lets see if this helps.
> > > > >>>>>>>
> > > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > > > <radcortez@yahoo.com.INVALID
> > > > >>>
> > > > >>>>>>> wrote:
> > > > >>>>>>>> Yeah, just noticed it as well. Was about to send a message
> > too.
> > > I
> > > > >> can
> > > > >>>>>>> have a look.
> > > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > > > >> jlmonteiro@tomitribe.com>
> > > > >>>>>>> wrote:
> > > > >>>>>>>>> Ok, looks like we are back to red.
> > > > >>>>>>>>> Someone working on it?
> > > > >>>>>>>>> --
> > > > >>>>>>>>> Jean-Louis Monteiro
> > > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > > >>>>>>>>> http://www.tomitribe.com
> > > > >>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > > > >>>>>>> <ra...@yahoo.com.invalid>
> > > > >>>>>>>>> wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>>> By the way, lets try to keep it that way :)
> > > > >>>>>>>>>>
> > > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > > > >>>>>>> cesarguate@gmail.com>
> > > > >>>>>>>>>> wrote:
> > > > >>>>>>>>>>> Nice work guys!
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > > > >> kamin.feuer.2000@gmx.de
> > > > >>>>>>>> )
> > > > >>>>>>>>>>> escribió:
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>>> Great! Well Done!
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> Frankie
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>> --
> > > > >>>>>>>>>>>> Sent from:
> > > > >>>>>>>>>>>>
> > > > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > >>>>>>>>>>>>
> > > > >>>>>>>>>>>
> > > > >>>>>>>>>>> --
> > > > >>>>>>>>>>> Atentamente:
> > > > >>>>>>>>>>> César Hernández Mendoza.
> > > > >>>>>>>>>>
> > > > >>>>>>>
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

On Fri, Jan 4, 2019 at 6:39 PM Ivan Junckes Filho <iv...@gmail.com>
wrote:

> Hey guys, can someone provide me the way to check if my PR is green?
>

Yep, run the build on your branch :-). I run builds on PRs when I review
them. If you don't want to run the full build, you could run tests that are
relevant to your change. If you need guidance on possible impacts of a PR,
please ask :).

Also, I wouldn't be scared of things being merged in and the build
breaking. The key thing is to check it, and help fix it if there is a
problem. The current CI builds on buildbot are available from here:
https://ci.apache.org/buildbot.html


> Also, now that apache has migrated to gitbox, is there a way to integrate
> the build with github?
>

This wasn't a pre-requisite of being able to build PRs on a CI. If someone
wants to have a go at setting up something to run against PRs on Travis or
on ASF infrastructure, please do go for it. Its not something we can just
"switch on" though I'm afraid. We do also need to be mindful that we have
27 open PRs and a build that takes 5 hours to run fully - so if we do setup
something like this, it will consume a fair bit of resource.

Jon


>
> On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > That'd be great indeed
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez
> <radcortez@yahoo.com.invalid
> > >
> > wrote:
> >
> > > Maybe Bruno would like to work on that, since he is heavily involved
> with
> > > the EG and he did the integration for the last version?
> > >
> > > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com
> > >
> > > wrote:
> > > >
> > > > Ok, looks like the build is back to stable.
> > > > There are 2 other votes currently. I'll do an update when the vote is
> > > > closed.
> > > >
> > > > Meanwhile, we need an action plan for fault tolerance. We need to
> > > > investigate what happened or if we need to rework the integration.
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com>
> > > wrote:
> > > >
> > > >> I think there's a vote for a minor release fixing an issue there.
> > > >>
> > > >> Bruno Baptista
> > > >> https://twitter.com/brunobat_
> > > >>
> > > >>
> > > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > > >>> The OpenTracing update was also failing the TCK. I’ve reverted it
> > back
> > > >> until we figure out what is going on.
> > > >>>
> > > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez
> <radcortez@yahoo.com.INVALID
> > >
> > > >> wrote:
> > > >>>>
> > > >>>> It seems to fail intermittently. It took me a few tries to make it
> > > >> fail. On the latest buildbot it seems fine.
> > > >>>>
> > > >>>> Not sure if it was like this before or if it was something we did.
> > > >>>>
> > > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com>
> > > >> wrote:
> > > >>>>>
> > > >>>>> [ERROR] Failures:
> > > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number
> > of
> > > >>>>> invocations for the bean "green". expected:<2> but was:<1>
> > > >>>>>
> > > >>>>> --
> > > >>>>> Jean-Louis Monteiro
> > > >>>>> http://twitter.com/jlouismonteiro
> > > >>>>> http://www.tomitribe.com
> > > >>>>>
> > > >>>>>
> > > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > > >> jlmonteiro@tomitribe.com>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> I also get this one locally
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Jean-Louis Monteiro
> > > >>>>>> http://twitter.com/jlouismonteiro
> > > >>>>>> http://www.tomitribe.com
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > > >> <ra...@yahoo.com.invalid>
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve
> reverted
> > it
> > > >> back.
> > > >>>>>>> Lets see if this helps.
> > > >>>>>>>
> > > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > > <radcortez@yahoo.com.INVALID
> > > >>>
> > > >>>>>>> wrote:
> > > >>>>>>>> Yeah, just noticed it as well. Was about to send a message
> too.
> > I
> > > >> can
> > > >>>>>>> have a look.
> > > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > > >> jlmonteiro@tomitribe.com>
> > > >>>>>>> wrote:
> > > >>>>>>>>> Ok, looks like we are back to red.
> > > >>>>>>>>> Someone working on it?
> > > >>>>>>>>> --
> > > >>>>>>>>> Jean-Louis Monteiro
> > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > >>>>>>>>> http://www.tomitribe.com
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > > >>>>>>> <ra...@yahoo.com.invalid>
> > > >>>>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> By the way, lets try to keep it that way :)
> > > >>>>>>>>>>
> > > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > > >>>>>>> cesarguate@gmail.com>
> > > >>>>>>>>>> wrote:
> > > >>>>>>>>>>> Nice work guys!
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > > >> kamin.feuer.2000@gmx.de
> > > >>>>>>>> )
> > > >>>>>>>>>>> escribió:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> Great! Well Done!
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Frankie
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> --
> > > >>>>>>>>>>>> Sent from:
> > > >>>>>>>>>>>>
> > > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Atentamente:
> > > >>>>>>>>>>> César Hernández Mendoza.
> > > >>>>>>>>>>
> > > >>>>>>>
> > > >>
> > >
> > >
> >
>

Re: Stabilize TomEE Build

[Ivan Junckes Filho <iv...@gmail.com>]

Hey guys, can someone provide me the way to check if my PR is green?

Also, now that apache has migrated to gitbox, is there a way to integrate
the build with github?

On Thu, Jan 3, 2019 at 10:03 AM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> That'd be great indeed
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez <radcortez@yahoo.com.invalid
> >
> wrote:
>
> > Maybe Bruno would like to work on that, since he is heavily involved with
> > the EG and he did the integration for the last version?
> >
> > > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <jlmonteiro@tomitribe.com
> >
> > wrote:
> > >
> > > Ok, looks like the build is back to stable.
> > > There are 2 other votes currently. I'll do an update when the vote is
> > > closed.
> > >
> > > Meanwhile, we need an action plan for fault tolerance. We need to
> > > investigate what happened or if we need to rework the integration.
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com>
> > wrote:
> > >
> > >> I think there's a vote for a minor release fixing an issue there.
> > >>
> > >> Bruno Baptista
> > >> https://twitter.com/brunobat_
> > >>
> > >>
> > >> On 02/01/19 18:56, Roberto Cortez wrote:
> > >>> The OpenTracing update was also failing the TCK. I’ve reverted it
> back
> > >> until we figure out what is going on.
> > >>>
> > >>>> On 2 Jan 2019, at 16:50, Roberto Cortez <radcortez@yahoo.com.INVALID
> >
> > >> wrote:
> > >>>>
> > >>>> It seems to fail intermittently. It took me a few tries to make it
> > >> fail. On the latest buildbot it seems fine.
> > >>>>
> > >>>> Not sure if it was like this before or if it was something we did.
> > >>>>
> > >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com>
> > >> wrote:
> > >>>>>
> > >>>>> [ERROR] Failures:
> > >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number
> of
> > >>>>> invocations for the bean "green". expected:<2> but was:<1>
> > >>>>>
> > >>>>> --
> > >>>>> Jean-Louis Monteiro
> > >>>>> http://twitter.com/jlouismonteiro
> > >>>>> http://www.tomitribe.com
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> > >> jlmonteiro@tomitribe.com>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> I also get this one locally
> > >>>>>>
> > >>>>>> --
> > >>>>>> Jean-Louis Monteiro
> > >>>>>> http://twitter.com/jlouismonteiro
> > >>>>>> http://www.tomitribe.com
> > >>>>>>
> > >>>>>>
> > >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> > >> <ra...@yahoo.com.invalid>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> One issue at least was with the Safeguard upgrade. I’ve reverted
> it
> > >> back.
> > >>>>>>> Lets see if this helps.
> > >>>>>>>
> > >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> > <radcortez@yahoo.com.INVALID
> > >>>
> > >>>>>>> wrote:
> > >>>>>>>> Yeah, just noticed it as well. Was about to send a message too.
> I
> > >> can
> > >>>>>>> have a look.
> > >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> > >> jlmonteiro@tomitribe.com>
> > >>>>>>> wrote:
> > >>>>>>>>> Ok, looks like we are back to red.
> > >>>>>>>>> Someone working on it?
> > >>>>>>>>> --
> > >>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> > >>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> By the way, lets try to keep it that way :)
> > >>>>>>>>>>
> > >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> > >>>>>>> cesarguate@gmail.com>
> > >>>>>>>>>> wrote:
> > >>>>>>>>>>> Nice work guys!
> > >>>>>>>>>>>
> > >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> > >> kamin.feuer.2000@gmx.de
> > >>>>>>>> )
> > >>>>>>>>>>> escribió:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Great! Well Done!
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Frankie
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> --
> > >>>>>>>>>>>> Sent from:
> > >>>>>>>>>>>>
> > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Atentamente:
> > >>>>>>>>>>> César Hernández Mendoza.
> > >>>>>>>>>>
> > >>>>>>>
> > >>
> >
> >
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

That'd be great indeed

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Jan 3, 2019 at 12:26 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Maybe Bruno would like to work on that, since he is heavily involved with
> the EG and he did the integration for the last version?
>
> > On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > Ok, looks like the build is back to stable.
> > There are 2 other votes currently. I'll do an update when the vote is
> > closed.
> >
> > Meanwhile, we need an action plan for fault tolerance. We need to
> > investigate what happened or if we need to rework the integration.
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com>
> wrote:
> >
> >> I think there's a vote for a minor release fixing an issue there.
> >>
> >> Bruno Baptista
> >> https://twitter.com/brunobat_
> >>
> >>
> >> On 02/01/19 18:56, Roberto Cortez wrote:
> >>> The OpenTracing update was also failing the TCK. I’ve reverted it back
> >> until we figure out what is going on.
> >>>
> >>>> On 2 Jan 2019, at 16:50, Roberto Cortez <ra...@yahoo.com.INVALID>
> >> wrote:
> >>>>
> >>>> It seems to fail intermittently. It took me a few tries to make it
> >> fail. On the latest buildbot it seems fine.
> >>>>
> >>>> Not sure if it was like this before or if it was something we did.
> >>>>
> >>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> >> wrote:
> >>>>>
> >>>>> [ERROR] Failures:
> >>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
> >>>>> invocations for the bean "green". expected:<2> but was:<1>
> >>>>>
> >>>>> --
> >>>>> Jean-Louis Monteiro
> >>>>> http://twitter.com/jlouismonteiro
> >>>>> http://www.tomitribe.com
> >>>>>
> >>>>>
> >>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> >> jlmonteiro@tomitribe.com>
> >>>>> wrote:
> >>>>>
> >>>>>> I also get this one locally
> >>>>>>
> >>>>>> --
> >>>>>> Jean-Louis Monteiro
> >>>>>> http://twitter.com/jlouismonteiro
> >>>>>> http://www.tomitribe.com
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> >> <ra...@yahoo.com.invalid>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> One issue at least was with the Safeguard upgrade. I’ve reverted it
> >> back.
> >>>>>>> Lets see if this helps.
> >>>>>>>
> >>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez
> <radcortez@yahoo.com.INVALID
> >>>
> >>>>>>> wrote:
> >>>>>>>> Yeah, just noticed it as well. Was about to send a message too. I
> >> can
> >>>>>>> have a look.
> >>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> >> jlmonteiro@tomitribe.com>
> >>>>>>> wrote:
> >>>>>>>>> Ok, looks like we are back to red.
> >>>>>>>>> Someone working on it?
> >>>>>>>>> --
> >>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> >>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> By the way, lets try to keep it that way :)
> >>>>>>>>>>
> >>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> >>>>>>> cesarguate@gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>> Nice work guys!
> >>>>>>>>>>>
> >>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> >> kamin.feuer.2000@gmx.de
> >>>>>>>> )
> >>>>>>>>>>> escribió:
> >>>>>>>>>>>
> >>>>>>>>>>>> Great! Well Done!
> >>>>>>>>>>>>
> >>>>>>>>>>>> Frankie
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Sent from:
> >>>>>>>>>>>>
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Atentamente:
> >>>>>>>>>>> César Hernández Mendoza.
> >>>>>>>>>>
> >>>>>>>
> >>
>
>

Re: Stabilize TomEE Build

[Bruno Baptista <br...@gmail.com>]

Yes, I can have a look, but only next week.

Bruno Baptista
https://twitter.com/brunobat_


On 03/01/19 11:26, Roberto Cortez wrote:
> Maybe Bruno would like to work on that, since he is heavily involved with the EG and he did the integration for the last version?

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Maybe Bruno would like to work on that, since he is heavily involved with the EG and he did the integration for the last version?

> On 3 Jan 2019, at 11:16, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> Ok, looks like the build is back to stable.
> There are 2 other votes currently. I'll do an update when the vote is
> closed.
> 
> Meanwhile, we need an action plan for fault tolerance. We need to
> investigate what happened or if we need to rework the integration.
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com> wrote:
> 
>> I think there's a vote for a minor release fixing an issue there.
>> 
>> Bruno Baptista
>> https://twitter.com/brunobat_
>> 
>> 
>> On 02/01/19 18:56, Roberto Cortez wrote:
>>> The OpenTracing update was also failing the TCK. I’ve reverted it back
>> until we figure out what is going on.
>>> 
>>>> On 2 Jan 2019, at 16:50, Roberto Cortez <ra...@yahoo.com.INVALID>
>> wrote:
>>>> 
>>>> It seems to fail intermittently. It took me a few tries to make it
>> fail. On the latest buildbot it seems fine.
>>>> 
>>>> Not sure if it was like this before or if it was something we did.
>>>> 
>>>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <jl...@tomitribe.com>
>> wrote:
>>>>> 
>>>>> [ERROR] Failures:
>>>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
>>>>> invocations for the bean "green". expected:<2> but was:<1>
>>>>> 
>>>>> --
>>>>> Jean-Louis Monteiro
>>>>> http://twitter.com/jlouismonteiro
>>>>> http://www.tomitribe.com
>>>>> 
>>>>> 
>>>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>
>>>>> wrote:
>>>>> 
>>>>>> I also get this one locally
>>>>>> 
>>>>>> --
>>>>>> Jean-Louis Monteiro
>>>>>> http://twitter.com/jlouismonteiro
>>>>>> http://www.tomitribe.com
>>>>>> 
>>>>>> 
>>>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
>> <ra...@yahoo.com.invalid>
>>>>>> wrote:
>>>>>> 
>>>>>>> One issue at least was with the Safeguard upgrade. I’ve reverted it
>> back.
>>>>>>> Lets see if this helps.
>>>>>>> 
>>>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez <radcortez@yahoo.com.INVALID
>>> 
>>>>>>> wrote:
>>>>>>>> Yeah, just noticed it as well. Was about to send a message too. I
>> can
>>>>>>> have a look.
>>>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>
>>>>>>> wrote:
>>>>>>>>> Ok, looks like we are back to red.
>>>>>>>>> Someone working on it?
>>>>>>>>> --
>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>> http://www.tomitribe.com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> By the way, lets try to keep it that way :)
>>>>>>>>>> 
>>>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
>>>>>>> cesarguate@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>> Nice work guys!
>>>>>>>>>>> 
>>>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
>> kamin.feuer.2000@gmx.de
>>>>>>>> )
>>>>>>>>>>> escribió:
>>>>>>>>>>> 
>>>>>>>>>>>> Great! Well Done!
>>>>>>>>>>>> 
>>>>>>>>>>>> Frankie
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> Sent from:
>>>>>>>>>>>> 
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Atentamente:
>>>>>>>>>>> César Hernández Mendoza.
>>>>>>>>>> 
>>>>>>> 
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Ok, looks like the build is back to stable.
There are 2 other votes currently. I'll do an update when the vote is
closed.

Meanwhile, we need an action plan for fault tolerance. We need to
investigate what happened or if we need to rework the integration.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 2, 2019 at 7:57 PM Bruno Baptista <br...@gmail.com> wrote:

> I think there's a vote for a minor release fixing an issue there.
>
> Bruno Baptista
> https://twitter.com/brunobat_
>
>
> On 02/01/19 18:56, Roberto Cortez wrote:
> > The OpenTracing update was also failing the TCK. I’ve reverted it back
> until we figure out what is going on.
> >
> >> On 2 Jan 2019, at 16:50, Roberto Cortez <ra...@yahoo.com.INVALID>
> wrote:
> >>
> >> It seems to fail intermittently. It took me a few tries to make it
> fail. On the latest buildbot it seems fine.
> >>
> >> Not sure if it was like this before or if it was something we did.
> >>
> >>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >>>
> >>> [ERROR] Failures:
> >>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
> >>> invocations for the bean "green". expected:<2> but was:<1>
> >>>
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> >>> wrote:
> >>>
> >>>> I also get this one locally
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez
> <ra...@yahoo.com.invalid>
> >>>> wrote:
> >>>>
> >>>>> One issue at least was with the Safeguard upgrade. I’ve reverted it
> back.
> >>>>> Lets see if this helps.
> >>>>>
> >>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez <radcortez@yahoo.com.INVALID
> >
> >>>>> wrote:
> >>>>>> Yeah, just noticed it as well. Was about to send a message too. I
> can
> >>>>> have a look.
> >>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> >>>>> wrote:
> >>>>>>> Ok, looks like we are back to red.
> >>>>>>> Someone working on it?
> >>>>>>> --
> >>>>>>> Jean-Louis Monteiro
> >>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>> http://www.tomitribe.com
> >>>>>>>
> >>>>>>>
> >>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> >>>>> <ra...@yahoo.com.invalid>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> By the way, lets try to keep it that way :)
> >>>>>>>>
> >>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> >>>>> cesarguate@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>> Nice work guys!
> >>>>>>>>>
> >>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<
> kamin.feuer.2000@gmx.de
> >>>>>> )
> >>>>>>>>> escribió:
> >>>>>>>>>
> >>>>>>>>>> Great! Well Done!
> >>>>>>>>>>
> >>>>>>>>>> Frankie
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Sent from:
> >>>>>>>>>>
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Atentamente:
> >>>>>>>>> César Hernández Mendoza.
> >>>>>>>>
> >>>>>
>

Re: Stabilize TomEE Build

[Bruno Baptista <br...@gmail.com>]

I think there's a vote for a minor release fixing an issue there.

Bruno Baptista
https://twitter.com/brunobat_


On 02/01/19 18:56, Roberto Cortez wrote:
> The OpenTracing update was also failing the TCK. I’ve reverted it back until we figure out what is going on.
>
>> On 2 Jan 2019, at 16:50, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
>>
>> It seems to fail intermittently. It took me a few tries to make it fail. On the latest buildbot it seems fine.
>>
>> Not sure if it was like this before or if it was something we did.
>>
>>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
>>>
>>> [ERROR] Failures:
>>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
>>> invocations for the bean "green". expected:<2> but was:<1>
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <jl...@tomitribe.com>
>>> wrote:
>>>
>>>> I also get this one locally
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez <ra...@yahoo.com.invalid>
>>>> wrote:
>>>>
>>>>> One issue at least was with the Safeguard upgrade. I’ve reverted it back.
>>>>> Lets see if this helps.
>>>>>
>>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID>
>>>>> wrote:
>>>>>> Yeah, just noticed it as well. Was about to send a message too. I can
>>>>> have a look.
>>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com>
>>>>> wrote:
>>>>>>> Ok, looks like we are back to red.
>>>>>>> Someone working on it?
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>>>>> <ra...@yahoo.com.invalid>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> By the way, lets try to keep it that way :)
>>>>>>>>
>>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
>>>>> cesarguate@gmail.com>
>>>>>>>> wrote:
>>>>>>>>> Nice work guys!
>>>>>>>>>
>>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<kamin.feuer.2000@gmx.de
>>>>>> )
>>>>>>>>> escribió:
>>>>>>>>>
>>>>>>>>>> Great! Well Done!
>>>>>>>>>>
>>>>>>>>>> Frankie
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from:
>>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Atentamente:
>>>>>>>>> César Hernández Mendoza.
>>>>>>>>
>>>>>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

The OpenTracing update was also failing the TCK. I’ve reverted it back until we figure out what is going on.

> On 2 Jan 2019, at 16:50, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
> 
> It seems to fail intermittently. It took me a few tries to make it fail. On the latest buildbot it seems fine.
> 
> Not sure if it was like this before or if it was something we did.
> 
>> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
>> 
>> [ERROR] Failures:
>> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
>> invocations for the bean "green". expected:<2> but was:<1>
>> 
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 
>> 
>> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <jl...@tomitribe.com>
>> wrote:
>> 
>>> I also get this one locally
>>> 
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>> 
>>> 
>>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez <ra...@yahoo.com.invalid>
>>> wrote:
>>> 
>>>> One issue at least was with the Safeguard upgrade. I’ve reverted it back.
>>>> Lets see if this helps.
>>>> 
>>>>> On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID>
>>>> wrote:
>>>>> 
>>>>> Yeah, just noticed it as well. Was about to send a message too. I can
>>>> have a look.
>>>>> 
>>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com>
>>>> wrote:
>>>>>> 
>>>>>> Ok, looks like we are back to red.
>>>>>> Someone working on it?
>>>>>> --
>>>>>> Jean-Louis Monteiro
>>>>>> http://twitter.com/jlouismonteiro
>>>>>> http://www.tomitribe.com
>>>>>> 
>>>>>> 
>>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>>>> <ra...@yahoo.com.invalid>
>>>>>> wrote:
>>>>>> 
>>>>>>> By the way, lets try to keep it that way :)
>>>>>>> 
>>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
>>>> cesarguate@gmail.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Nice work guys!
>>>>>>>> 
>>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<kamin.feuer.2000@gmx.de
>>>>> )
>>>>>>>> escribió:
>>>>>>>> 
>>>>>>>>> Great! Well Done!
>>>>>>>>> 
>>>>>>>>> Frankie
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Sent from:
>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Atentamente:
>>>>>>>> César Hernández Mendoza.
>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>>> 
> 

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

It seems to fail intermittently. It took me a few tries to make it fail. On the latest buildbot it seems fine.

Not sure if it was like this before or if it was something we did.

> On 2 Jan 2019, at 12:14, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> [ERROR] Failures:
> [ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
> invocations for the bean "green". expected:<2> but was:<1>
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> 
>> I also get this one locally
>> 
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 
>> 
>> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez <ra...@yahoo.com.invalid>
>> wrote:
>> 
>>> One issue at least was with the Safeguard upgrade. I’ve reverted it back.
>>> Lets see if this helps.
>>> 
>>>> On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID>
>>> wrote:
>>>> 
>>>> Yeah, just noticed it as well. Was about to send a message too. I can
>>> have a look.
>>>> 
>>>>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com>
>>> wrote:
>>>>> 
>>>>> Ok, looks like we are back to red.
>>>>> Someone working on it?
>>>>> --
>>>>> Jean-Louis Monteiro
>>>>> http://twitter.com/jlouismonteiro
>>>>> http://www.tomitribe.com
>>>>> 
>>>>> 
>>>>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>>> <ra...@yahoo.com.invalid>
>>>>> wrote:
>>>>> 
>>>>>> By the way, lets try to keep it that way :)
>>>>>> 
>>>>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
>>> cesarguate@gmail.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> Nice work guys!
>>>>>>> 
>>>>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<kamin.feuer.2000@gmx.de
>>>> )
>>>>>>> escribió:
>>>>>>> 
>>>>>>>> Great! Well Done!
>>>>>>>> 
>>>>>>>> Frankie
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Sent from:
>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Atentamente:
>>>>>>> César Hernández Mendoza.
>>>>>> 
>>>>>> 
>>>> 
>>> 
>>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

[ERROR] Failures:
[ERROR]   LegacyServerTest.test:208->assertBalance:219 Bad number of
invocations for the bean "green". expected:<2> but was:<1>

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 2, 2019 at 1:14 PM Jean-Louis Monteiro <jl...@tomitribe.com>
wrote:

> I also get this one locally
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
>
>> One issue at least was with the Safeguard upgrade. I’ve reverted it back.
>> Lets see if this helps.
>>
>> > On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID>
>> wrote:
>> >
>> > Yeah, just noticed it as well. Was about to send a message too. I can
>> have a look.
>> >
>> >> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com>
>> wrote:
>> >>
>> >> Ok, looks like we are back to red.
>> >> Someone working on it?
>> >> --
>> >> Jean-Louis Monteiro
>> >> http://twitter.com/jlouismonteiro
>> >> http://www.tomitribe.com
>> >>
>> >>
>> >> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
>> <ra...@yahoo.com.invalid>
>> >> wrote:
>> >>
>> >>> By the way, lets try to keep it that way :)
>> >>>
>> >>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
>> cesarguate@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Nice work guys!
>> >>>>
>> >>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<kamin.feuer.2000@gmx.de
>> >)
>> >>>> escribió:
>> >>>>
>> >>>>> Great! Well Done!
>> >>>>>
>> >>>>> Frankie
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Sent from:
>> >>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Atentamente:
>> >>>> César Hernández Mendoza.
>> >>>
>> >>>
>> >
>>
>>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I also get this one locally

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 2, 2019 at 1:05 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> One issue at least was with the Safeguard upgrade. I’ve reverted it back.
> Lets see if this helps.
>
> > On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID>
> wrote:
> >
> > Yeah, just noticed it as well. Was about to send a message too. I can
> have a look.
> >
> >> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >>
> >> Ok, looks like we are back to red.
> >> Someone working on it?
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez
> <ra...@yahoo.com.invalid>
> >> wrote:
> >>
> >>> By the way, lets try to keep it that way :)
> >>>
> >>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <
> cesarguate@gmail.com>
> >>> wrote:
> >>>>
> >>>> Nice work guys!
> >>>>
> >>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<kamin.feuer.2000@gmx.de
> >)
> >>>> escribió:
> >>>>
> >>>>> Great! Well Done!
> >>>>>
> >>>>> Frankie
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from:
> >>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Atentamente:
> >>>> César Hernández Mendoza.
> >>>
> >>>
> >
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

One issue at least was with the Safeguard upgrade. I’ve reverted it back. Lets see if this helps.

> On 2 Jan 2019, at 11:33, Roberto Cortez <ra...@yahoo.com.INVALID> wrote:
> 
> Yeah, just noticed it as well. Was about to send a message too. I can have a look.
> 
>> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
>> 
>> Ok, looks like we are back to red.
>> Someone working on it?
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 
>> 
>> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez <ra...@yahoo.com.invalid>
>> wrote:
>> 
>>> By the way, lets try to keep it that way :)
>>> 
>>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <ce...@gmail.com>
>>> wrote:
>>>> 
>>>> Nice work guys!
>>>> 
>>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<ka...@gmx.de>)
>>>> escribió:
>>>> 
>>>>> Great! Well Done!
>>>>> 
>>>>> Frankie
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Sent from:
>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Atentamente:
>>>> César Hernández Mendoza.
>>> 
>>> 
> 

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Yeah, just noticed it as well. Was about to send a message too. I can have a look.

> On 2 Jan 2019, at 11:00, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> Ok, looks like we are back to red.
> Someone working on it?
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
> 
>> By the way, lets try to keep it that way :)
>> 
>>> On 20 Dec 2018, at 20:48, César Hernández Mendoza <ce...@gmail.com>
>> wrote:
>>> 
>>> Nice work guys!
>>> 
>>> El jue., 20 dic. 2018 a las 13:55, Frankie (<ka...@gmx.de>)
>>> escribió:
>>> 
>>>> Great! Well Done!
>>>> 
>>>> Frankie
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from:
>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>> 
>>> 
>>> 
>>> --
>>> Atentamente:
>>> César Hernández Mendoza.
>> 
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Ok, looks like we are back to red.
Someone working on it?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 21, 2018 at 12:59 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> By the way, lets try to keep it that way :)
>
> > On 20 Dec 2018, at 20:48, César Hernández Mendoza <ce...@gmail.com>
> wrote:
> >
> > Nice work guys!
> >
> > El jue., 20 dic. 2018 a las 13:55, Frankie (<ka...@gmx.de>)
> > escribió:
> >
> >> Great! Well Done!
> >>
> >> Frankie
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>
> >
> >
> > --
> > Atentamente:
> > César Hernández Mendoza.
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

By the way, lets try to keep it that way :)

> On 20 Dec 2018, at 20:48, César Hernández Mendoza <ce...@gmail.com> wrote:
> 
> Nice work guys!
> 
> El jue., 20 dic. 2018 a las 13:55, Frankie (<ka...@gmx.de>)
> escribió:
> 
>> Great! Well Done!
>> 
>> Frankie
>> 
>> 
>> 
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> 
> 
> 
> -- 
> Atentamente:
> César Hernández Mendoza.

Re: Stabilize TomEE Build

[César Hernández Mendoza <ce...@gmail.com>]

Nice work guys!

El jue., 20 dic. 2018 a las 13:55, Frankie (<ka...@gmx.de>)
escribió:

> Great! Well Done!
>
> Frankie
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>


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

Re: Stabilize TomEE Build

[Frankie <ka...@gmx.de>]

Great! Well Done! 

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Great! Congratulations everyone!

Did we change something on the CDI tests?

> On 20 Dec 2018, at 17:25, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> Build is green, yeah.
> 
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
> 
> Great community effort. Thanks everyone
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Dec 19, 2018 at 10:56 PM Daniel Cunha <da...@apache.org> wrote:
> 
>> Hi Roberto,
>> 
>> I can't reproduce the issue in both 7.0.x and 7.1.x with my patch applied,
>> it seems passing as expected:
>> [INFO]
>> [INFO] -------------------------------------------------------
>> [INFO]  T E S T S
>> [INFO] -------------------------------------------------------
>> [INFO] Running org.apache.tomee.TomEECliIT
>> Must specify either a plain text to encrypt or a ciphered value to decrypt.
>> usage: cipher [options] <value>
>> 
>> Uses a password cipher implementation to encrypt/decrypt a value.
>> -c,--cipher <c>   Specifies the password cipher implementation to use
>>                   (default is Static3DES).
>> -d,--decrypt      Switches command line tool to decrypt.
>> -e,--encrypt      Switches command line tool to encrypt (default).
>> -h,--help         Lists these options and exits.
>> 
>> Available ciphers are: cdi
>> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
>> 1.144 s - in org.apache.tomee.TomEECliIT
>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
>> Dec 19, 2018 6:52:57 PM org.apache.openejb.client.EventLogger log
>> INFO: RemoteInitialContextCreated{providerUri=
>> http://localhost:46355/tomee/ejb}
>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.25
>> s - in org.apache.tomee.RemoteTomEEEJBContainerIT
>> [INFO]
>> [INFO] Results:
>> [INFO]
>> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
>> 
>> 
>> Is possible to trigger build from buildbot for my PR?
>> 
>> Em qua, 19 de dez de 2018 às 11:36, Roberto Cortez
>> <ra...@yahoo.com.invalid> escreveu:
>> 
>>> The CDI TCK runs after the OpenEJB Core, so you should be able to see the
>>> debug information you added.
>>> 
>>> I’m not sure if you noticed it, but I did add a @Ignore to the
>>> AutoConnectionTracker test until we figure out what is wrong.
>>> 
>>>> On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>
>>> wrote:
>>>> 
>>>> Roberto, I saw you commented the test in which I added some more stuff
>> to
>>>> test.
>>>> Do you have some inputs after the run?
>>>> Or are we still stuck on CDI ?
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>> 
>>>> 
>>>> On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org>
>>> wrote:
>>>> 
>>>>> I saw your comment and it's weird.
>>>>> I'll look it again, the patch should fix exactly the test which you
>> are
>>>>> getting error. :)
>>>>> 
>>>>> Thanks for review.
>>>>> 
>>>>> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>> 
>>>>>> Hi Daniel,
>>>>>> 
>>>>>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can
>> you
>>>>>> confirm? Left you a note in the PR’s.
>>>>>> 
>>>>>> Cheers,
>>>>>> Roberto
>>>>>> 
>>>>>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
>>>>> jlmonteiro@tomitribe.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> I pushed some debugging information on the other test and I'll be
>>>>>>> monitoring the built
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>> 
>>>>>>> 
>>>>>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <danielsoro@apache.org
>>> 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> Nice... Thanks!
>>>>>>>> 
>>>>>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
>>>>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>>>>> 
>>>>>>>>> Hi Daniel,
>>>>>>>>> I didn't yet for the other branches. I'll do it today.
>>>>>>>>>  On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
>>>>>>>>> danielsoro@gmail.com> wrote:
>>>>>>>>> 
>>>>>>>>> Hi Roberto,
>>>>>>>>> 
>>>>>>>>> I saw that you merged the changes on master, did you see the
>> others
>>>>>>>> changes
>>>>>>>>> for branch 7.0.x and 7.1.x?
>>>>>>>>> 
>>>>>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>> 
>>>>>>>>>> Thank you Daniel,
>>>>>>>>>> 
>>>>>>>>>> I’ll review and merge.
>>>>>>>>>> 
>>>>>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
>>>>>> couple
>>>>>>>>> of
>>>>>>>>>> days before, but now it happened again. Not sure what is wrong
>>>>> there,
>>>>>>>>> since
>>>>>>>>>> we used to pass it.
>>>>>>>>>> 
>>>>>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi Roberto,
>>>>>>>>>>> 
>>>>>>>>>>> the fix which I send is to make sure that the test is using the
>>>>>>>> correct
>>>>>>>>>>> version for libs.
>>>>>>>>>>> For example, here
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
>>>>>>>>>>> we have the version of the lib on the code.
>>>>>>>>>>> 
>>>>>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
>>>>>>>> works,
>>>>>>>>>>> because for that build, it will have openejb-core-7.0.x and not
>>>>>>>>>>> openejb-core-8.0.0-SNAPSHOT.
>>>>>>>>>>> 
>>>>>>>>>>> That is the issue, we need to get the correct reference for the
>>> lib
>>>>>>>> to
>>>>>>>>>> make
>>>>>>>>>>> sure that the command will works.
>>>>>>>>>>> 
>>>>>>>>>>> About the test stuck, reading the stacktrace that you send,
>> seems
>>>>>>>>>> something
>>>>>>>>>>> during TCK test. Is it?
>>>>>>>>>>> 
>>>>>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
>>>>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>>>>> 
>>>>>>>>>>>> Hi Daniel,
>>>>>>>>>>>> 
>>>>>>>>>>>> Can you please explain what the issue was?
>>>>>>>>>>>> 
>>>>>>>>>>>> Also, it seems our build is getting killed for taking to long
>> due
>>>>> to
>>>>>>>>>> some
>>>>>>>>>>>> tests being stuck?
>>>>>>>>>>>> 
>>>>>>>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb
>> }
>>>>>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
>>>>>>>> object
>>>>>>>>>> input
>>>>>>>>>>>> stream to server (OEJP/4.6) : null}
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
>>>>>>>>>> beforeInvocation
>>>>>>>>>>>> INFO: Invoke
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
>>>>>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>>>>>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
>>>>> deployed
>>>>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
>>>>>>>>>> build
>>>>>>>>>>>> INFO: Test archive built [info:
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
>>>>>>>>>>>> time: 16 ms]
>>>>>>>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger
>>> log
>>>>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> command timed out: 18000 seconds without output running ['mvn',
>>>>>>>> '-U',
>>>>>>>>>>>> '--show-version', '--fail-at-end',
>>>>>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
>>>>> 'install',
>>>>>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
>>>>>>>>> '-DdisableXmlReport=true',
>>>>>>>>>>>> '-Dopenejb.arquillian.debug=true',
>>>>>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>>>>>>>>>>>> process killed by signal 9
>>>>>>>>>>>> program finished with exit code -1
>>>>>>>>>>>> elapsedTime=38754.464253
>>>>>>>>>>>> 
>>>>>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30
>> PM.
>>>>> No
>>>>>>>>>> logs
>>>>>>>>>>>> in between...
>>>>>>>>>>>> 
>>>>>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <danielsoro@apache.org
>>> 
>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Hey folks,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> we found an issue on TomEECliIT test.
>>>>>>>>>>>>> I've opened fixes for test in all branch, please take a look
>> on
>>>>> it.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Fixes:
>>>>>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
>>>>>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>>>>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>>>>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Please wait a minute lol
>>>>>>>>>>>>>> I'd rather have you help me if needed.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> First I don't have the feeling I spent time for nothing on it
>>>>> and
>>>>>>>>>>>> second,
>>>>>>>>>>>>>> at least I will learn something.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>>>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help
>>> look
>>>>>>>>> into
>>>>>>>>>>>> it.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> It seems the build just randomly fails with this test:
>>>>>>>>>>>>>>>> AutoConnectionTrackerTest.test
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> [ERROR] Failures:
>>>>>>>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1>
>> but
>>>>>>>>>> was:<0>
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may
>> be
>>>>>>>>> related
>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m
>> running
>>>>> the
>>>>>>>>>> test
>>>>>>>>>>>>>> non
>>>>>>>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
>>>>>>>>>> replicate
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> issue:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Any ideias?
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> I'll take the first one first
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Thank you JL,
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> At least this test is failing:
>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> And this one seems to fail randomly.
>>>>>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full
>> build
>>>>>>>>>> locally.
>>>>>>>>>>>>>>> I'll
>>>>>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
>>>>> first
>>>>>>>>>> here
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Hey Jon,
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> The following commit:
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Is failing the test:
>>>>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Can you help?
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
>>>>> kamin.feuer.2000@gmx.de
>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the information
>>> on
>>>>>>>> IRC
>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Frankie
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Sent from:
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>> 
>> --
>> Daniel "soro" Cunha
>> https://twitter.com/dvlc_
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Build is green, yeah.

https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8

Great community effort. Thanks everyone

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 19, 2018 at 10:56 PM Daniel Cunha <da...@apache.org> wrote:

> Hi Roberto,
>
> I can't reproduce the issue in both 7.0.x and 7.1.x with my patch applied,
> it seems passing as expected:
> [INFO]
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running org.apache.tomee.TomEECliIT
> Must specify either a plain text to encrypt or a ciphered value to decrypt.
> usage: cipher [options] <value>
>
> Uses a password cipher implementation to encrypt/decrypt a value.
>  -c,--cipher <c>   Specifies the password cipher implementation to use
>                    (default is Static3DES).
>  -d,--decrypt      Switches command line tool to decrypt.
>  -e,--encrypt      Switches command line tool to encrypt (default).
>  -h,--help         Lists these options and exits.
>
> Available ciphers are: cdi
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 1.144 s - in org.apache.tomee.TomEECliIT
> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
> Dec 19, 2018 6:52:57 PM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=
> http://localhost:46355/tomee/ejb}
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.25
> s - in org.apache.tomee.RemoteTomEEEJBContainerIT
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
>
>
> Is possible to trigger build from buildbot for my PR?
>
> Em qua, 19 de dez de 2018 às 11:36, Roberto Cortez
> <ra...@yahoo.com.invalid> escreveu:
>
> > The CDI TCK runs after the OpenEJB Core, so you should be able to see the
> > debug information you added.
> >
> > I’m not sure if you noticed it, but I did add a @Ignore to the
> > AutoConnectionTracker test until we figure out what is wrong.
> >
> > > On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> > wrote:
> > >
> > > Roberto, I saw you commented the test in which I added some more stuff
> to
> > > test.
> > > Do you have some inputs after the run?
> > > Or are we still stuck on CDI ?
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org>
> > wrote:
> > >
> > >> I saw your comment and it's weird.
> > >> I'll look it again, the patch should fix exactly the test which you
> are
> > >> getting error. :)
> > >>
> > >> Thanks for review.
> > >>
> > >> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
> > >> <radcortez@yahoo.com.invalid escreveu:
> > >>
> > >>> Hi Daniel,
> > >>>
> > >>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can
> you
> > >>> confirm? Left you a note in the PR’s.
> > >>>
> > >>> Cheers,
> > >>> Roberto
> > >>>
> > >>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
> > >> jlmonteiro@tomitribe.com>
> > >>> wrote:
> > >>>>
> > >>>> I pushed some debugging information on the other test and I'll be
> > >>>> monitoring the built
> > >>>> --
> > >>>> Jean-Louis Monteiro
> > >>>> http://twitter.com/jlouismonteiro
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>
> > >>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <danielsoro@apache.org
> >
> > >>> wrote:
> > >>>>
> > >>>>> Nice... Thanks!
> > >>>>>
> > >>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
> > >>>>> <radcortez@yahoo.com.invalid escreveu:
> > >>>>>
> > >>>>>> Hi Daniel,
> > >>>>>> I didn't yet for the other branches. I'll do it today.
> > >>>>>>   On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> > >>>>>> danielsoro@gmail.com> wrote:
> > >>>>>>
> > >>>>>> Hi Roberto,
> > >>>>>>
> > >>>>>> I saw that you merged the changes on master, did you see the
> others
> > >>>>> changes
> > >>>>>> for branch 7.0.x and 7.1.x?
> > >>>>>>
> > >>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> > >>>>>> <ra...@yahoo.com.invalid> escreveu:
> > >>>>>>
> > >>>>>>> Thank you Daniel,
> > >>>>>>>
> > >>>>>>> I’ll review and merge.
> > >>>>>>>
> > >>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
> > >>> couple
> > >>>>>> of
> > >>>>>>> days before, but now it happened again. Not sure what is wrong
> > >> there,
> > >>>>>> since
> > >>>>>>> we used to pass it.
> > >>>>>>>
> > >>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
> > >> wrote:
> > >>>>>>>>
> > >>>>>>>> Hi Roberto,
> > >>>>>>>>
> > >>>>>>>> the fix which I send is to make sure that the test is using the
> > >>>>> correct
> > >>>>>>>> version for libs.
> > >>>>>>>> For example, here
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > >>>>>>>> we have the version of the lib on the code.
> > >>>>>>>>
> > >>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
> > >>>>> works,
> > >>>>>>>> because for that build, it will have openejb-core-7.0.x and not
> > >>>>>>>> openejb-core-8.0.0-SNAPSHOT.
> > >>>>>>>>
> > >>>>>>>> That is the issue, we need to get the correct reference for the
> > lib
> > >>>>> to
> > >>>>>>> make
> > >>>>>>>> sure that the command will works.
> > >>>>>>>>
> > >>>>>>>> About the test stuck, reading the stacktrace that you send,
> seems
> > >>>>>>> something
> > >>>>>>>> during TCK test. Is it?
> > >>>>>>>>
> > >>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > >>>>>>>> <ra...@yahoo.com.invalid> escreveu:
> > >>>>>>>>
> > >>>>>>>>> Hi Daniel,
> > >>>>>>>>>
> > >>>>>>>>> Can you please explain what the issue was?
> > >>>>>>>>>
> > >>>>>>>>> Also, it seems our build is getting killed for taking to long
> due
> > >> to
> > >>>>>>> some
> > >>>>>>>>> tests being stuck?
> > >>>>>>>>>
> > >>>>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger
> > log
> > >>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
> > >>>>>>>>> http://localhost:40395/tomee/ejb}
> > >>>>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger
> > log
> > >>>>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb
> }
> > >>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
> > >>>>> object
> > >>>>>>> input
> > >>>>>>>>> stream to server (OEJP/4.6) : null}
> > >>>>>>>>> Dec 17, 2018 12:10:27 PM
> > >>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> > >>>>>>> beforeInvocation
> > >>>>>>>>> INFO: Invoke
> > >>>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> >
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> > >>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
> > >>>>>>>>> Dec 17, 2018 12:10:27 PM
> > >>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> > >>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
> > >> deployed
> > >>>>>>>>> Dec 17, 2018 12:10:27 PM
> > >> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> > >>>>>>> build
> > >>>>>>>>> INFO: Test archive built [info:
> > >>>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> >
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> > >>>>>>>>> time: 16 ms]
> > >>>>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger
> > log
> > >>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
> > >>>>>>>>> http://localhost:40395/tomee/ejb}
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> command timed out: 18000 seconds without output running ['mvn',
> > >>>>> '-U',
> > >>>>>>>>> '--show-version', '--fail-at-end',
> > >>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
> > >> 'install',
> > >>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
> > >>>>>> '-DdisableXmlReport=true',
> > >>>>>>>>> '-Dopenejb.arquillian.debug=true',
> > >>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> > >>>>>>>>> process killed by signal 9
> > >>>>>>>>> program finished with exit code -1
> > >>>>>>>>> elapsedTime=38754.464253
> > >>>>>>>>>
> > >>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30
> PM.
> > >> No
> > >>>>>>> logs
> > >>>>>>>>> in between...
> > >>>>>>>>>
> > >>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <danielsoro@apache.org
> >
> > >>>>>> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>> Hey folks,
> > >>>>>>>>>>
> > >>>>>>>>>> we found an issue on TomEECliIT test.
> > >>>>>>>>>> I've opened fixes for test in all branch, please take a look
> on
> > >> it.
> > >>>>>>>>>>
> > >>>>>>>>>> Fixes:
> > >>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
> > >>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
> > >>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
> > >>>>>>>>>>
> > >>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> > >>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
> > >>>>>>>>>>
> > >>>>>>>>>>> Please wait a minute lol
> > >>>>>>>>>>> I'd rather have you help me if needed.
> > >>>>>>>>>>>
> > >>>>>>>>>>> First I don't have the feeling I spent time for nothing on it
> > >> and
> > >>>>>>>>> second,
> > >>>>>>>>>>> at least I will learn something.
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> > >>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help
> > look
> > >>>>>> into
> > >>>>>>>>> it.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> > >>>>>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> It seems the build just randomly fails with this test:
> > >>>>>>>>>>>>> AutoConnectionTrackerTest.test
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> [ERROR] Failures:
> > >>>>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1>
> but
> > >>>>>>> was:<0>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may
> be
> > >>>>>> related
> > >>>>>>>>>>> with
> > >>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m
> running
> > >> the
> > >>>>>>> test
> > >>>>>>>>>>> non
> > >>>>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
> > >>>>>>> replicate
> > >>>>>>>>>>> the
> > >>>>>>>>>>>>> issue:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> Any ideias?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> > >>>>>>>>>>>> jlmonteiro@tomitribe.com>
> > >>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> I'll take the first one first
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > >>>>>>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Thank you JL,
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> At least this test is failing:
> > >>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> And this one seems to fail randomly.
> > >>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>>>>> Roberto
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > >>>>>>>>>>>>> jlmonteiro@tomitribe.com>
> > >>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full
> build
> > >>>>>>> locally.
> > >>>>>>>>>>>> I'll
> > >>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
> > >> first
> > >>>>>>> here
> > >>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > >>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Hey Jon,
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> The following commit:
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>>>>>>>>> <
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Is failing the test:
> > >>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Can you help?
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>>>>>>> Roberto
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
> > >> kamin.feuer.2000@gmx.de
> > >>>>>>
> > >>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> Hi Cesar,
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
> > >>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the information
> > on
> > >>>>> IRC
> > >>>>>>> ...
> > >>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> Frankie
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>>>>> Sent from:
> > >>>>>>>>>>>>>>>>>
> > >>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Daniel "soro" Cunha
> > >>>>>>>>>> https://twitter.com/dvlc_
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Daniel "soro" Cunha
> > >>>>>>>> https://twitter.com/dvlc_
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Daniel "soro" Cunha
> > >>>>>> https://twitter.com/dvlc_
> > >>>>>
> > >>>
> > >>>
> > >>
> >
> >
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

Hi Roberto,

I can't reproduce the issue in both 7.0.x and 7.1.x with my patch applied,
it seems passing as expected:
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.tomee.TomEECliIT
Must specify either a plain text to encrypt or a ciphered value to decrypt.
usage: cipher [options] <value>

Uses a password cipher implementation to encrypt/decrypt a value.
 -c,--cipher <c>   Specifies the password cipher implementation to use
                   (default is Static3DES).
 -d,--decrypt      Switches command line tool to decrypt.
 -e,--encrypt      Switches command line tool to encrypt (default).
 -h,--help         Lists these options and exits.

Available ciphers are: cdi
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
1.144 s - in org.apache.tomee.TomEECliIT
[INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
Dec 19, 2018 6:52:57 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=
http://localhost:46355/tomee/ejb}
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.25
s - in org.apache.tomee.RemoteTomEEEJBContainerIT
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0


Is possible to trigger build from buildbot for my PR?

Em qua, 19 de dez de 2018 às 11:36, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> The CDI TCK runs after the OpenEJB Core, so you should be able to see the
> debug information you added.
>
> I’m not sure if you noticed it, but I did add a @Ignore to the
> AutoConnectionTracker test until we figure out what is wrong.
>
> > On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > Roberto, I saw you commented the test in which I added some more stuff to
> > test.
> > Do you have some inputs after the run?
> > Or are we still stuck on CDI ?
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org>
> wrote:
> >
> >> I saw your comment and it's weird.
> >> I'll look it again, the patch should fix exactly the test which you are
> >> getting error. :)
> >>
> >> Thanks for review.
> >>
> >> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
> >> <radcortez@yahoo.com.invalid escreveu:
> >>
> >>> Hi Daniel,
> >>>
> >>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can you
> >>> confirm? Left you a note in the PR’s.
> >>>
> >>> Cheers,
> >>> Roberto
> >>>
> >>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
> >> jlmonteiro@tomitribe.com>
> >>> wrote:
> >>>>
> >>>> I pushed some debugging information on the other test and I'll be
> >>>> monitoring the built
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org>
> >>> wrote:
> >>>>
> >>>>> Nice... Thanks!
> >>>>>
> >>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
> >>>>> <radcortez@yahoo.com.invalid escreveu:
> >>>>>
> >>>>>> Hi Daniel,
> >>>>>> I didn't yet for the other branches. I'll do it today.
> >>>>>>   On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> >>>>>> danielsoro@gmail.com> wrote:
> >>>>>>
> >>>>>> Hi Roberto,
> >>>>>>
> >>>>>> I saw that you merged the changes on master, did you see the others
> >>>>> changes
> >>>>>> for branch 7.0.x and 7.1.x?
> >>>>>>
> >>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid> escreveu:
> >>>>>>
> >>>>>>> Thank you Daniel,
> >>>>>>>
> >>>>>>> I’ll review and merge.
> >>>>>>>
> >>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
> >>> couple
> >>>>>> of
> >>>>>>> days before, but now it happened again. Not sure what is wrong
> >> there,
> >>>>>> since
> >>>>>>> we used to pass it.
> >>>>>>>
> >>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
> >> wrote:
> >>>>>>>>
> >>>>>>>> Hi Roberto,
> >>>>>>>>
> >>>>>>>> the fix which I send is to make sure that the test is using the
> >>>>> correct
> >>>>>>>> version for libs.
> >>>>>>>> For example, here
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> >>>>>>>> we have the version of the lib on the code.
> >>>>>>>>
> >>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
> >>>>> works,
> >>>>>>>> because for that build, it will have openejb-core-7.0.x and not
> >>>>>>>> openejb-core-8.0.0-SNAPSHOT.
> >>>>>>>>
> >>>>>>>> That is the issue, we need to get the correct reference for the
> lib
> >>>>> to
> >>>>>>> make
> >>>>>>>> sure that the command will works.
> >>>>>>>>
> >>>>>>>> About the test stuck, reading the stacktrace that you send, seems
> >>>>>>> something
> >>>>>>>> during TCK test. Is it?
> >>>>>>>>
> >>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> >>>>>>>> <ra...@yahoo.com.invalid> escreveu:
> >>>>>>>>
> >>>>>>>>> Hi Daniel,
> >>>>>>>>>
> >>>>>>>>> Can you please explain what the issue was?
> >>>>>>>>>
> >>>>>>>>> Also, it seems our build is getting killed for taking to long due
> >> to
> >>>>>>> some
> >>>>>>>>> tests being stuck?
> >>>>>>>>>
> >>>>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger
> log
> >>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
> >>>>>>>>> http://localhost:40395/tomee/ejb}
> >>>>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger
> log
> >>>>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> >>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
> >>>>> object
> >>>>>>> input
> >>>>>>>>> stream to server (OEJP/4.6) : null}
> >>>>>>>>> Dec 17, 2018 12:10:27 PM
> >>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> >>>>>>> beforeInvocation
> >>>>>>>>> INFO: Invoke
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> >>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
> >>>>>>>>> Dec 17, 2018 12:10:27 PM
> >>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> >>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
> >> deployed
> >>>>>>>>> Dec 17, 2018 12:10:27 PM
> >> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> >>>>>>> build
> >>>>>>>>> INFO: Test archive built [info:
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> >>>>>>>>> time: 16 ms]
> >>>>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger
> log
> >>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
> >>>>>>>>> http://localhost:40395/tomee/ejb}
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> command timed out: 18000 seconds without output running ['mvn',
> >>>>> '-U',
> >>>>>>>>> '--show-version', '--fail-at-end',
> >>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
> >> 'install',
> >>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
> >>>>>> '-DdisableXmlReport=true',
> >>>>>>>>> '-Dopenejb.arquillian.debug=true',
> >>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> >>>>>>>>> process killed by signal 9
> >>>>>>>>> program finished with exit code -1
> >>>>>>>>> elapsedTime=38754.464253
> >>>>>>>>>
> >>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30 PM.
> >> No
> >>>>>>> logs
> >>>>>>>>> in between...
> >>>>>>>>>
> >>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
> >>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hey folks,
> >>>>>>>>>>
> >>>>>>>>>> we found an issue on TomEECliIT test.
> >>>>>>>>>> I've opened fixes for test in all branch, please take a look on
> >> it.
> >>>>>>>>>>
> >>>>>>>>>> Fixes:
> >>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
> >>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
> >>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
> >>>>>>>>>>
> >>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> >>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
> >>>>>>>>>>
> >>>>>>>>>>> Please wait a minute lol
> >>>>>>>>>>> I'd rather have you help me if needed.
> >>>>>>>>>>>
> >>>>>>>>>>> First I don't have the feeling I spent time for nothing on it
> >> and
> >>>>>>>>> second,
> >>>>>>>>>>> at least I will learn something.
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> >>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help
> look
> >>>>>> into
> >>>>>>>>> it.
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> >>>>>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> It seems the build just randomly fails with this test:
> >>>>>>>>>>>>> AutoConnectionTrackerTest.test
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> [ERROR] Failures:
> >>>>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> >>>>>>> was:<0>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
> >>>>>> related
> >>>>>>>>>>> with
> >>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m running
> >> the
> >>>>>>> test
> >>>>>>>>>>> non
> >>>>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
> >>>>>>> replicate
> >>>>>>>>>>> the
> >>>>>>>>>>>>> issue:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Any ideias?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> >>>>>>>>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'll take the first one first
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> >>>>>>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thank you JL,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> At least this test is failing:
> >>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> And this one seems to fail randomly.
> >>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>>> Roberto
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> >>>>>>>>>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full build
> >>>>>>> locally.
> >>>>>>>>>>>> I'll
> >>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
> >> first
> >>>>>>> here
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Hey Jon,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The following commit:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>>>>>>> <
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Is failing the test:
> >>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Can you help?
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>>>>> Roberto
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
> >> kamin.feuer.2000@gmx.de
> >>>>>>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Hi Cesar,
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
> >>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the information
> on
> >>>>> IRC
> >>>>>>> ...
> >>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Frankie
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> Sent from:
> >>>>>>>>>>>>>>>>>
> >>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Daniel "soro" Cunha
> >>>>>>>>>> https://twitter.com/dvlc_
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Daniel "soro" Cunha
> >>>>>>>> https://twitter.com/dvlc_
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Daniel "soro" Cunha
> >>>>>> https://twitter.com/dvlc_
> >>>>>
> >>>
> >>>
> >>
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

The CDI TCK runs after the OpenEJB Core, so you should be able to see the debug information you added.

I’m not sure if you noticed it, but I did add a @Ignore to the AutoConnectionTracker test until we figure out what is wrong.

> On 19 Dec 2018, at 13:51, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> Roberto, I saw you commented the test in which I added some more stuff to
> test.
> Do you have some inputs after the run?
> Or are we still stuck on CDI ?
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org> wrote:
> 
>> I saw your comment and it's weird.
>> I'll look it again, the patch should fix exactly the test which you are
>> getting error. :)
>> 
>> Thanks for review.
>> 
>> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
>> <radcortez@yahoo.com.invalid escreveu:
>> 
>>> Hi Daniel,
>>> 
>>> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can you
>>> confirm? Left you a note in the PR’s.
>>> 
>>> Cheers,
>>> Roberto
>>> 
>>>> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com>
>>> wrote:
>>>> 
>>>> I pushed some debugging information on the other test and I'll be
>>>> monitoring the built
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>> 
>>>> 
>>>> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org>
>>> wrote:
>>>> 
>>>>> Nice... Thanks!
>>>>> 
>>>>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
>>>>> <radcortez@yahoo.com.invalid escreveu:
>>>>> 
>>>>>> Hi Daniel,
>>>>>> I didn't yet for the other branches. I'll do it today.
>>>>>>   On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
>>>>>> danielsoro@gmail.com> wrote:
>>>>>> 
>>>>>> Hi Roberto,
>>>>>> 
>>>>>> I saw that you merged the changes on master, did you see the others
>>>>> changes
>>>>>> for branch 7.0.x and 7.1.x?
>>>>>> 
>>>>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>> 
>>>>>>> Thank you Daniel,
>>>>>>> 
>>>>>>> I’ll review and merge.
>>>>>>> 
>>>>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
>>> couple
>>>>>> of
>>>>>>> days before, but now it happened again. Not sure what is wrong
>> there,
>>>>>> since
>>>>>>> we used to pass it.
>>>>>>> 
>>>>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
>> wrote:
>>>>>>>> 
>>>>>>>> Hi Roberto,
>>>>>>>> 
>>>>>>>> the fix which I send is to make sure that the test is using the
>>>>> correct
>>>>>>>> version for libs.
>>>>>>>> For example, here
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
>>>>>>>> we have the version of the lib on the code.
>>>>>>>> 
>>>>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
>>>>> works,
>>>>>>>> because for that build, it will have openejb-core-7.0.x and not
>>>>>>>> openejb-core-8.0.0-SNAPSHOT.
>>>>>>>> 
>>>>>>>> That is the issue, we need to get the correct reference for the lib
>>>>> to
>>>>>>> make
>>>>>>>> sure that the command will works.
>>>>>>>> 
>>>>>>>> About the test stuck, reading the stacktrace that you send, seems
>>>>>>> something
>>>>>>>> during TCK test. Is it?
>>>>>>>> 
>>>>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
>>>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>>>> 
>>>>>>>>> Hi Daniel,
>>>>>>>>> 
>>>>>>>>> Can you please explain what the issue was?
>>>>>>>>> 
>>>>>>>>> Also, it seems our build is getting killed for taking to long due
>> to
>>>>>>> some
>>>>>>>>> tests being stuck?
>>>>>>>>> 
>>>>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
>>>>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
>>>>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
>>>>> object
>>>>>>> input
>>>>>>>>> stream to server (OEJP/4.6) : null}
>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
>>>>>>> beforeInvocation
>>>>>>>>> INFO: Invoke
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
>>>>>>>>> 1,203/1,571 Failed tests: 59 (476)
>>>>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>>>>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
>> deployed
>>>>>>>>> Dec 17, 2018 12:10:27 PM
>> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
>>>>>>> build
>>>>>>>>> INFO: Test archive built [info:
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
>>>>>>>>> time: 16 ms]
>>>>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
>>>>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>>>>> http://localhost:40395/tomee/ejb}
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> command timed out: 18000 seconds without output running ['mvn',
>>>>> '-U',
>>>>>>>>> '--show-version', '--fail-at-end',
>>>>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
>> 'install',
>>>>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
>>>>>> '-DdisableXmlReport=true',
>>>>>>>>> '-Dopenejb.arquillian.debug=true',
>>>>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>>>>>>>>> process killed by signal 9
>>>>>>>>> program finished with exit code -1
>>>>>>>>> elapsedTime=38754.464253
>>>>>>>>> 
>>>>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30 PM.
>> No
>>>>>>> logs
>>>>>>>>> in between...
>>>>>>>>> 
>>>>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hey folks,
>>>>>>>>>> 
>>>>>>>>>> we found an issue on TomEECliIT test.
>>>>>>>>>> I've opened fixes for test in all branch, please take a look on
>> it.
>>>>>>>>>> 
>>>>>>>>>> Fixes:
>>>>>>>>>> master -> https://github.com/apache/tomee/pull/288
>>>>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>>>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>>>>>>>>> 
>>>>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>>>>>>>>> jlmonteiro@tomitribe.com> escreveu:
>>>>>>>>>> 
>>>>>>>>>>> Please wait a minute lol
>>>>>>>>>>> I'd rather have you help me if needed.
>>>>>>>>>>> 
>>>>>>>>>>> First I don't have the feeling I spent time for nothing on it
>> and
>>>>>>>>> second,
>>>>>>>>>>> at least I will learn something.
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>>>>>>>>> jonathan.gallimore@gmail.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> I added this test, and it was pretty stable. Happy to help look
>>>>>> into
>>>>>>>>> it.
>>>>>>>>>>>> 
>>>>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>>> It seems the build just randomly fails with this test:
>>>>>>>>>>>>> AutoConnectionTrackerTest.test
>>>>>>>>>>>>> 
>>>>>>>>>>>>> [ERROR] Failures:
>>>>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
>>>>>>> was:<0>
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
>>>>>> related
>>>>>>>>>>> with
>>>>>>>>>>>>> some timing issues / box speed of the build bot. I’m running
>> the
>>>>>>> test
>>>>>>>>>>> non
>>>>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
>>>>>>> replicate
>>>>>>>>>>> the
>>>>>>>>>>>>> issue:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Any ideias?
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I'll take the first one first
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Thank you JL,
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> At least this test is failing:
>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> And this one seems to fail randomly.
>>>>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full build
>>>>>>> locally.
>>>>>>>>>>>> I'll
>>>>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
>> first
>>>>>>> here
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Hey Jon,
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> The following commit:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Is failing the test:
>>>>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Can you help?
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
>> kamin.feuer.2000@gmx.de
>>>>>> 
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>>>>>>>>> That's what I thohght, too when I read the information on
>>>>> IRC
>>>>>>> ...
>>>>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Frankie
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Sent from:
>>>>>>>>>>>>>>>>> 
>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --
>>>>>>>>>> Daniel "soro" Cunha
>>>>>>>>>> https://twitter.com/dvlc_
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Daniel "soro" Cunha
>>>>>>>> https://twitter.com/dvlc_
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Daniel "soro" Cunha
>>>>>> https://twitter.com/dvlc_
>>>>> 
>>> 
>>> 
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Roberto, I saw you commented the test in which I added some more stuff to
test.
Do you have some inputs after the run?
Or are we still stuck on CDI ?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 19, 2018 at 12:44 PM Daniel Cunha <da...@apache.org> wrote:

> I saw your comment and it's weird.
> I'll look it again, the patch should fix exactly the test which you are
> getting error. :)
>
> Thanks for review.
>
> Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
> <radcortez@yahoo.com.invalid escreveu:
>
> > Hi Daniel,
> >
> > I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can you
> > confirm? Left you a note in the PR’s.
> >
> > Cheers,
> > Roberto
> >
> > > On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> > wrote:
> > >
> > > I pushed some debugging information on the other test and I'll be
> > > monitoring the built
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org>
> > wrote:
> > >
> > >> Nice... Thanks!
> > >>
> > >> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
> > >> <radcortez@yahoo.com.invalid escreveu:
> > >>
> > >>> Hi Daniel,
> > >>> I didn't yet for the other branches. I'll do it today.
> > >>>    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> > >>> danielsoro@gmail.com> wrote:
> > >>>
> > >>> Hi Roberto,
> > >>>
> > >>> I saw that you merged the changes on master, did you see the others
> > >> changes
> > >>> for branch 7.0.x and 7.1.x?
> > >>>
> > >>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> > >>> <ra...@yahoo.com.invalid> escreveu:
> > >>>
> > >>>> Thank you Daniel,
> > >>>>
> > >>>> I’ll review and merge.
> > >>>>
> > >>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
> > couple
> > >>> of
> > >>>> days before, but now it happened again. Not sure what is wrong
> there,
> > >>> since
> > >>>> we used to pass it.
> > >>>>
> > >>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com>
> wrote:
> > >>>>>
> > >>>>> Hi Roberto,
> > >>>>>
> > >>>>> the fix which I send is to make sure that the test is using the
> > >> correct
> > >>>>> version for libs.
> > >>>>> For example, here
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > >>>>> we have the version of the lib on the code.
> > >>>>>
> > >>>>> Which means that, if you try run it on TomEE 7.0.x it will never
> > >> works,
> > >>>>> because for that build, it will have openejb-core-7.0.x and not
> > >>>>> openejb-core-8.0.0-SNAPSHOT.
> > >>>>>
> > >>>>> That is the issue, we need to get the correct reference for the lib
> > >> to
> > >>>> make
> > >>>>> sure that the command will works.
> > >>>>>
> > >>>>> About the test stuck, reading the stacktrace that you send, seems
> > >>>> something
> > >>>>> during TCK test. Is it?
> > >>>>>
> > >>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > >>>>> <ra...@yahoo.com.invalid> escreveu:
> > >>>>>
> > >>>>>> Hi Daniel,
> > >>>>>>
> > >>>>>> Can you please explain what the issue was?
> > >>>>>>
> > >>>>>> Also, it seems our build is getting killed for taking to long due
> to
> > >>>> some
> > >>>>>> tests being stuck?
> > >>>>>>
> > >>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> > >>>>>> INFO: RemoteInitialContextCreated{providerUri=
> > >>>>>> http://localhost:40395/tomee/ejb}
> > >>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> > >>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> > >>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
> > >> object
> > >>>> input
> > >>>>>> stream to server (OEJP/4.6) : null}
> > >>>>>> Dec 17, 2018 12:10:27 PM
> > >>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> > >>>> beforeInvocation
> > >>>>>> INFO: Invoke
> > >>>>>>
> > >>>>
> > >>>
> > >>
> >
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> > >>>>>> 1,203/1,571 Failed tests: 59 (476)
> > >>>>>> Dec 17, 2018 12:10:27 PM
> > >>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> > >>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not
> deployed
> > >>>>>> Dec 17, 2018 12:10:27 PM
> org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> > >>>> build
> > >>>>>> INFO: Test archive built [info:
> > >>>>>>
> > >>>>
> > >>>
> > >>
> >
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> > >>>>>> time: 16 ms]
> > >>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> > >>>>>> INFO: RemoteInitialContextCreated{providerUri=
> > >>>>>> http://localhost:40395/tomee/ejb}
> > >>>>>>
> > >>>>>>
> > >>>>>> command timed out: 18000 seconds without output running ['mvn',
> > >> '-U',
> > >>>>>> '--show-version', '--fail-at-end',
> > >>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean',
> 'install',
> > >>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
> > >>> '-DdisableXmlReport=true',
> > >>>>>> '-Dopenejb.arquillian.debug=true',
> > >>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> > >>>>>> process killed by signal 9
> > >>>>>> program finished with exit code -1
> > >>>>>> elapsedTime=38754.464253
> > >>>>>>
> > >>>>>> Last log is from 12:10:28. Process was killed around 17:10:30 PM.
> No
> > >>>> logs
> > >>>>>> in between...
> > >>>>>>
> > >>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
> > >>> wrote:
> > >>>>>>>
> > >>>>>>> Hey folks,
> > >>>>>>>
> > >>>>>>> we found an issue on TomEECliIT test.
> > >>>>>>> I've opened fixes for test in all branch, please take a look on
> it.
> > >>>>>>>
> > >>>>>>> Fixes:
> > >>>>>>> master -> https://github.com/apache/tomee/pull/288
> > >>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
> > >>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
> > >>>>>>>
> > >>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> > >>>>>>> jlmonteiro@tomitribe.com> escreveu:
> > >>>>>>>
> > >>>>>>>> Please wait a minute lol
> > >>>>>>>> I'd rather have you help me if needed.
> > >>>>>>>>
> > >>>>>>>> First I don't have the feeling I spent time for nothing on it
> and
> > >>>>>> second,
> > >>>>>>>> at least I will learn something.
> > >>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Jean-Louis Monteiro
> > >>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>> http://www.tomitribe.com
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> > >>>>>>>> jonathan.gallimore@gmail.com> wrote:
> > >>>>>>>>
> > >>>>>>>>> I added this test, and it was pretty stable. Happy to help look
> > >>> into
> > >>>>>> it.
> > >>>>>>>>>
> > >>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> > >>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> It seems the build just randomly fails with this test:
> > >>>>>>>>>> AutoConnectionTrackerTest.test
> > >>>>>>>>>>
> > >>>>>>>>>> [ERROR] Failures:
> > >>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> > >>>> was:<0>
> > >>>>>>>>>>
> > >>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
> > >>> related
> > >>>>>>>> with
> > >>>>>>>>>> some timing issues / box speed of the build bot. I’m running
> the
> > >>>> test
> > >>>>>>>> non
> > >>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
> > >>>> replicate
> > >>>>>>>> the
> > >>>>>>>>>> issue:
> > >>>>>>>>>>
> > >>>>>>>>>> Any ideias?
> > >>>>>>>>>>
> > >>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> > >>>>>>>>> jlmonteiro@tomitribe.com>
> > >>>>>>>>>> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> I'll take the first one first
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > >>>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>>>> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Thank you JL,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> At least this test is failing:
> > >>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> And this one seems to fail randomly.
> > >>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>> Roberto
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > >>>>>>>>>> jlmonteiro@tomitribe.com>
> > >>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> I have merged a couple of PR and I'm running a full build
> > >>>> locally.
> > >>>>>>>>> I'll
> > >>>>>>>>>>>>> work on fixes any issues if I find some but I'll report
> first
> > >>>> here
> > >>>>>>>>>>>>> --
> > >>>>>>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > >>>>>>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>>>>>> wrote:
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Hey Jon,
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> The following commit:
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>>>>>> <
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>
> > >>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Is failing the test:
> > >>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Can you help?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Cheers,
> > >>>>>>>>>>>>>> Roberto
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <
> kamin.feuer.2000@gmx.de
> > >>>
> > >>>>>>>> wrote:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Hi Cesar,
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> This is a valuable piece of information.
> > >>>>>>>>>>>>>>> That's what I thohght, too when I read the information on
> > >> IRC
> > >>>> ...
> > >>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> The JIRA task is now assigned to you.
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> Frankie
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> --
> > >>>>>>>>>>>>>>> Sent from:
> > >>>>>>>>>>>>>>
> > >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Daniel "soro" Cunha
> > >>>>>>> https://twitter.com/dvlc_
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Daniel "soro" Cunha
> > >>>>> https://twitter.com/dvlc_
> > >>>>
> > >>>>
> > >>>
> > >>> --
> > >>> Daniel "soro" Cunha
> > >>> https://twitter.com/dvlc_
> > >>
> >
> >
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

I saw your comment and it's weird.
I'll look it again, the patch should fix exactly the test which you are
getting error. :)

Thanks for review.

Em qua, 19 de dez de 2018 8:08 AM, Roberto Cortez
<radcortez@yahoo.com.invalid escreveu:

> Hi Daniel,
>
> I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can you
> confirm? Left you a note in the PR’s.
>
> Cheers,
> Roberto
>
> > On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > I pushed some debugging information on the other test and I'll be
> > monitoring the built
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org>
> wrote:
> >
> >> Nice... Thanks!
> >>
> >> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
> >> <radcortez@yahoo.com.invalid escreveu:
> >>
> >>> Hi Daniel,
> >>> I didn't yet for the other branches. I'll do it today.
> >>>    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> >>> danielsoro@gmail.com> wrote:
> >>>
> >>> Hi Roberto,
> >>>
> >>> I saw that you merged the changes on master, did you see the others
> >> changes
> >>> for branch 7.0.x and 7.1.x?
> >>>
> >>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> >>> <ra...@yahoo.com.invalid> escreveu:
> >>>
> >>>> Thank you Daniel,
> >>>>
> >>>> I’ll review and merge.
> >>>>
> >>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a
> couple
> >>> of
> >>>> days before, but now it happened again. Not sure what is wrong there,
> >>> since
> >>>> we used to pass it.
> >>>>
> >>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> >>>>>
> >>>>> Hi Roberto,
> >>>>>
> >>>>> the fix which I send is to make sure that the test is using the
> >> correct
> >>>>> version for libs.
> >>>>> For example, here
> >>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> >>>>> we have the version of the lib on the code.
> >>>>>
> >>>>> Which means that, if you try run it on TomEE 7.0.x it will never
> >> works,
> >>>>> because for that build, it will have openejb-core-7.0.x and not
> >>>>> openejb-core-8.0.0-SNAPSHOT.
> >>>>>
> >>>>> That is the issue, we need to get the correct reference for the lib
> >> to
> >>>> make
> >>>>> sure that the command will works.
> >>>>>
> >>>>> About the test stuck, reading the stacktrace that you send, seems
> >>>> something
> >>>>> during TCK test. Is it?
> >>>>>
> >>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> >>>>> <ra...@yahoo.com.invalid> escreveu:
> >>>>>
> >>>>>> Hi Daniel,
> >>>>>>
> >>>>>> Can you please explain what the issue was?
> >>>>>>
> >>>>>> Also, it seems our build is getting killed for taking to long due to
> >>>> some
> >>>>>> tests being stuck?
> >>>>>>
> >>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> >>>>>> INFO: RemoteInitialContextCreated{providerUri=
> >>>>>> http://localhost:40395/tomee/ejb}
> >>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> >>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> >>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
> >> object
> >>>> input
> >>>>>> stream to server (OEJP/4.6) : null}
> >>>>>> Dec 17, 2018 12:10:27 PM
> >>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> >>>> beforeInvocation
> >>>>>> INFO: Invoke
> >>>>>>
> >>>>
> >>>
> >>
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> >>>>>> 1,203/1,571 Failed tests: 59 (476)
> >>>>>> Dec 17, 2018 12:10:27 PM
> >>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> >>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> >>>>>> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> >>>> build
> >>>>>> INFO: Test archive built [info:
> >>>>>>
> >>>>
> >>>
> >>
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> >>>>>> time: 16 ms]
> >>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> >>>>>> INFO: RemoteInitialContextCreated{providerUri=
> >>>>>> http://localhost:40395/tomee/ejb}
> >>>>>>
> >>>>>>
> >>>>>> command timed out: 18000 seconds without output running ['mvn',
> >> '-U',
> >>>>>> '--show-version', '--fail-at-end',
> >>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> >>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
> >>> '-DdisableXmlReport=true',
> >>>>>> '-Dopenejb.arquillian.debug=true',
> >>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> >>>>>> process killed by signal 9
> >>>>>> program finished with exit code -1
> >>>>>> elapsedTime=38754.464253
> >>>>>>
> >>>>>> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
> >>>> logs
> >>>>>> in between...
> >>>>>>
> >>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
> >>> wrote:
> >>>>>>>
> >>>>>>> Hey folks,
> >>>>>>>
> >>>>>>> we found an issue on TomEECliIT test.
> >>>>>>> I've opened fixes for test in all branch, please take a look on it.
> >>>>>>>
> >>>>>>> Fixes:
> >>>>>>> master -> https://github.com/apache/tomee/pull/288
> >>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
> >>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
> >>>>>>>
> >>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> >>>>>>> jlmonteiro@tomitribe.com> escreveu:
> >>>>>>>
> >>>>>>>> Please wait a minute lol
> >>>>>>>> I'd rather have you help me if needed.
> >>>>>>>>
> >>>>>>>> First I don't have the feeling I spent time for nothing on it and
> >>>>>> second,
> >>>>>>>> at least I will learn something.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Jean-Louis Monteiro
> >>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>> http://www.tomitribe.com
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> >>>>>>>> jonathan.gallimore@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>>> I added this test, and it was pretty stable. Happy to help look
> >>> into
> >>>>>> it.
> >>>>>>>>>
> >>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> >>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> It seems the build just randomly fails with this test:
> >>>>>>>>>> AutoConnectionTrackerTest.test
> >>>>>>>>>>
> >>>>>>>>>> [ERROR] Failures:
> >>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> >>>> was:<0>
> >>>>>>>>>>
> >>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
> >>> related
> >>>>>>>> with
> >>>>>>>>>> some timing issues / box speed of the build bot. I’m running the
> >>>> test
> >>>>>>>> non
> >>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
> >>>> replicate
> >>>>>>>> the
> >>>>>>>>>> issue:
> >>>>>>>>>>
> >>>>>>>>>> Any ideias?
> >>>>>>>>>>
> >>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> >>>>>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I'll take the first one first
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> >>>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Thank you JL,
> >>>>>>>>>>>>
> >>>>>>>>>>>> At least this test is failing:
> >>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>>>
> >>>>>>>>>>>> And this one seems to fail randomly.
> >>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers,
> >>>>>>>>>>>> Roberto
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> >>>>>>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I have merged a couple of PR and I'm running a full build
> >>>> locally.
> >>>>>>>>> I'll
> >>>>>>>>>>>>> work on fixes any issues if I find some but I'll report first
> >>>> here
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >>>>>>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hey Jon,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The following commit:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>>>> <
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Is failing the test:
> >>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Can you help?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>> Roberto
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <kamin.feuer.2000@gmx.de
> >>>
> >>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi Cesar,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> This is a valuable piece of information.
> >>>>>>>>>>>>>>> That's what I thohght, too when I read the information on
> >> IRC
> >>>> ...
> >>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> The JIRA task is now assigned to you.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Frankie
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>> Sent from:
> >>>>>>>>>>>>>>
> >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Daniel "soro" Cunha
> >>>>>>> https://twitter.com/dvlc_
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Daniel "soro" Cunha
> >>>>> https://twitter.com/dvlc_
> >>>>
> >>>>
> >>>
> >>> --
> >>> Daniel "soro" Cunha
> >>> https://twitter.com/dvlc_
> >>
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Hi Daniel,

I’m having test failures in the PR updates for 7.0.x and 7.1.x. Can you confirm? Left you a note in the PR’s.

Cheers,
Roberto

> On 18 Dec 2018, at 15:18, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> I pushed some debugging information on the other test and I'll be
> monitoring the built
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org> wrote:
> 
>> Nice... Thanks!
>> 
>> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
>> <radcortez@yahoo.com.invalid escreveu:
>> 
>>> Hi Daniel,
>>> I didn't yet for the other branches. I'll do it today.
>>>    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
>>> danielsoro@gmail.com> wrote:
>>> 
>>> Hi Roberto,
>>> 
>>> I saw that you merged the changes on master, did you see the others
>> changes
>>> for branch 7.0.x and 7.1.x?
>>> 
>>> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
>>> <ra...@yahoo.com.invalid> escreveu:
>>> 
>>>> Thank you Daniel,
>>>> 
>>>> I’ll review and merge.
>>>> 
>>>> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple
>>> of
>>>> days before, but now it happened again. Not sure what is wrong there,
>>> since
>>>> we used to pass it.
>>>> 
>>>>> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
>>>>> 
>>>>> Hi Roberto,
>>>>> 
>>>>> the fix which I send is to make sure that the test is using the
>> correct
>>>>> version for libs.
>>>>> For example, here
>>>>> 
>>>> 
>>> 
>> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
>>>>> we have the version of the lib on the code.
>>>>> 
>>>>> Which means that, if you try run it on TomEE 7.0.x it will never
>> works,
>>>>> because for that build, it will have openejb-core-7.0.x and not
>>>>> openejb-core-8.0.0-SNAPSHOT.
>>>>> 
>>>>> That is the issue, we need to get the correct reference for the lib
>> to
>>>> make
>>>>> sure that the command will works.
>>>>> 
>>>>> About the test stuck, reading the stacktrace that you send, seems
>>>> something
>>>>> during TCK test. Is it?
>>>>> 
>>>>> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>> 
>>>>>> Hi Daniel,
>>>>>> 
>>>>>> Can you please explain what the issue was?
>>>>>> 
>>>>>> Also, it seems our build is getting killed for taking to long due to
>>>> some
>>>>>> tests being stuck?
>>>>>> 
>>>>>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>> http://localhost:40395/tomee/ejb}
>>>>>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
>>>>>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
>>>>>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
>> object
>>>> input
>>>>>> stream to server (OEJP/4.6) : null}
>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
>>>> beforeInvocation
>>>>>> INFO: Invoke
>>>>>> 
>>>> 
>>> 
>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
>>>>>> 1,203/1,571 Failed tests: 59 (476)
>>>>>> Dec 17, 2018 12:10:27 PM
>>>>>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>>>>>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
>>>>>> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
>>>> build
>>>>>> INFO: Test archive built [info:
>>>>>> 
>>>> 
>>> 
>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
>>>>>> time: 16 ms]
>>>>>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
>>>>>> INFO: RemoteInitialContextCreated{providerUri=
>>>>>> http://localhost:40395/tomee/ejb}
>>>>>> 
>>>>>> 
>>>>>> command timed out: 18000 seconds without output running ['mvn',
>> '-U',
>>>>>> '--show-version', '--fail-at-end',
>>>>>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
>>>>>> '-Pall-adapters', '-Dsurefire.useFile=false',
>>> '-DdisableXmlReport=true',
>>>>>> '-Dopenejb.arquillian.debug=true',
>>>>>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>>>>>> process killed by signal 9
>>>>>> program finished with exit code -1
>>>>>> elapsedTime=38754.464253
>>>>>> 
>>>>>> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
>>>> logs
>>>>>> in between...
>>>>>> 
>>>>>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
>>> wrote:
>>>>>>> 
>>>>>>> Hey folks,
>>>>>>> 
>>>>>>> we found an issue on TomEECliIT test.
>>>>>>> I've opened fixes for test in all branch, please take a look on it.
>>>>>>> 
>>>>>>> Fixes:
>>>>>>> master -> https://github.com/apache/tomee/pull/288
>>>>>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>>>>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>>>>>> 
>>>>>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>>>>>> jlmonteiro@tomitribe.com> escreveu:
>>>>>>> 
>>>>>>>> Please wait a minute lol
>>>>>>>> I'd rather have you help me if needed.
>>>>>>>> 
>>>>>>>> First I don't have the feeling I spent time for nothing on it and
>>>>>> second,
>>>>>>>> at least I will learn something.
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Jean-Louis Monteiro
>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>> http://www.tomitribe.com
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>>>>>> jonathan.gallimore@gmail.com> wrote:
>>>>>>>> 
>>>>>>>>> I added this test, and it was pretty stable. Happy to help look
>>> into
>>>>>> it.
>>>>>>>>> 
>>>>>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> It seems the build just randomly fails with this test:
>>>>>>>>>> AutoConnectionTrackerTest.test
>>>>>>>>>> 
>>>>>>>>>> [ERROR] Failures:
>>>>>>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
>>>> was:<0>
>>>>>>>>>> 
>>>>>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
>>> related
>>>>>>>> with
>>>>>>>>>> some timing issues / box speed of the build bot. I’m running the
>>>> test
>>>>>>>> non
>>>>>>>>>> stop on my box (already executed 100+ times) and I couldn’t
>>>> replicate
>>>>>>>> the
>>>>>>>>>> issue:
>>>>>>>>>> 
>>>>>>>>>> Any ideias?
>>>>>>>>>> 
>>>>>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I'll take the first one first
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> Thank you JL,
>>>>>>>>>>>> 
>>>>>>>>>>>> At least this test is failing:
>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>> 
>>>>>>>>>>>> And this one seems to fail randomly.
>>>>>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>>>>>> 
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Roberto
>>>>>>>>>>>> 
>>>>>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I have merged a couple of PR and I'm running a full build
>>>> locally.
>>>>>>>>> I'll
>>>>>>>>>>>>> work on fixes any issues if I find some but I'll report first
>>>> here
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>>>>>> http://www.tomitribe.com
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Hey Jon,
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> The following commit:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>> <
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Is failing the test:
>>>>>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Can you help?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>> Roberto
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <kamin.feuer.2000@gmx.de
>>> 
>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>>>>>> That's what I thohght, too when I read the information on
>> IRC
>>>> ...
>>>>>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Frankie
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Sent from:
>>>>>>>>>>>>>> 
>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --
>>>>>>> Daniel "soro" Cunha
>>>>>>> https://twitter.com/dvlc_
>>>>>> 
>>>>>> 
>>>>> 
>>>>> --
>>>>> Daniel "soro" Cunha
>>>>> https://twitter.com/dvlc_
>>>> 
>>>> 
>>> 
>>> --
>>> Daniel "soro" Cunha
>>> https://twitter.com/dvlc_
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I pushed some debugging information on the other test and I'll be
monitoring the built
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, Dec 18, 2018 at 4:16 PM Daniel Cunha <da...@apache.org> wrote:

> Nice... Thanks!
>
> Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
> <radcortez@yahoo.com.invalid escreveu:
>
> >  Hi Daniel,
> > I didn't yet for the other branches. I'll do it today.
> >     On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> > danielsoro@gmail.com> wrote:
> >
> >  Hi Roberto,
> >
> > I saw that you merged the changes on master, did you see the others
> changes
> > for branch 7.0.x and 7.1.x?
> >
> > Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> > <ra...@yahoo.com.invalid> escreveu:
> >
> > > Thank you Daniel,
> > >
> > > I’ll review and merge.
> > >
> > > Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple
> > of
> > > days before, but now it happened again. Not sure what is wrong there,
> > since
> > > we used to pass it.
> > >
> > > > On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> > > >
> > > > Hi Roberto,
> > > >
> > > > the fix which I send is to make sure that the test is using the
> correct
> > > > version for libs.
> > > > For example, here
> > > >
> > >
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > > > we have the version of the lib on the code.
> > > >
> > > > Which means that, if you try run it on TomEE 7.0.x it will never
> works,
> > > > because for that build, it will have openejb-core-7.0.x and not
> > > > openejb-core-8.0.0-SNAPSHOT.
> > > >
> > > > That is the issue, we need to get the correct reference for the lib
> to
> > > make
> > > > sure that the command will works.
> > > >
> > > > About the test stuck, reading the stacktrace that you send, seems
> > > something
> > > > during TCK test. Is it?
> > > >
> > > > Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > > > <ra...@yahoo.com.invalid> escreveu:
> > > >
> > > >> Hi Daniel,
> > > >>
> > > >> Can you please explain what the issue was?
> > > >>
> > > >> Also, it seems our build is getting killed for taking to long due to
> > > some
> > > >> tests being stuck?
> > > >>
> > > >> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> > > >> INFO: RemoteInitialContextCreated{providerUri=
> > > >> http://localhost:40395/tomee/ejb}
> > > >> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> > > >> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> > > >> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open
> object
> > > input
> > > >> stream to server (OEJP/4.6) : null}
> > > >> Dec 17, 2018 12:10:27 PM
> > > >> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> > > beforeInvocation
> > > >> INFO: Invoke
> > > >>
> > >
> >
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> > > >> 1,203/1,571 Failed tests: 59 (476)
> > > >> Dec 17, 2018 12:10:27 PM
> > > >> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> > > >> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> > > >> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> > > build
> > > >> INFO: Test archive built [info:
> > > >>
> > >
> >
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> > > >> time: 16 ms]
> > > >> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> > > >> INFO: RemoteInitialContextCreated{providerUri=
> > > >> http://localhost:40395/tomee/ejb}
> > > >>
> > > >>
> > > >> command timed out: 18000 seconds without output running ['mvn',
> '-U',
> > > >> '--show-version', '--fail-at-end',
> > > >> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> > > >> '-Pall-adapters', '-Dsurefire.useFile=false',
> > '-DdisableXmlReport=true',
> > > >> '-Dopenejb.arquillian.debug=true',
> > > >> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> > > >> process killed by signal 9
> > > >> program finished with exit code -1
> > > >> elapsedTime=38754.464253
> > > >>
> > > >> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
> > > logs
> > > >> in between...
> > > >>
> > > >>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
> > wrote:
> > > >>>
> > > >>> Hey folks,
> > > >>>
> > > >>> we found an issue on TomEECliIT test.
> > > >>> I've opened fixes for test in all branch, please take a look on it.
> > > >>>
> > > >>> Fixes:
> > > >>> master -> https://github.com/apache/tomee/pull/288
> > > >>> 7.1.x -> https://github.com/apache/tomee/pull/287
> > > >>> 7.0.x -> https://github.com/apache/tomee/pull/286
> > > >>>
> > > >>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> > > >>> jlmonteiro@tomitribe.com> escreveu:
> > > >>>
> > > >>>> Please wait a minute lol
> > > >>>> I'd rather have you help me if needed.
> > > >>>>
> > > >>>> First I don't have the feeling I spent time for nothing on it and
> > > >> second,
> > > >>>> at least I will learn something.
> > > >>>>
> > > >>>> --
> > > >>>> Jean-Louis Monteiro
> > > >>>> http://twitter.com/jlouismonteiro
> > > >>>> http://www.tomitribe.com
> > > >>>>
> > > >>>>
> > > >>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> > > >>>> jonathan.gallimore@gmail.com> wrote:
> > > >>>>
> > > >>>>> I added this test, and it was pretty stable. Happy to help look
> > into
> > > >> it.
> > > >>>>>
> > > >>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> > > >>>>> <ra...@yahoo.com.invalid>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> It seems the build just randomly fails with this test:
> > > >>>>>> AutoConnectionTrackerTest.test
> > > >>>>>>
> > > >>>>>> [ERROR] Failures:
> > > >>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> > > was:<0>
> > > >>>>>>
> > > >>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
> > related
> > > >>>> with
> > > >>>>>> some timing issues / box speed of the build bot. I’m running the
> > > test
> > > >>>> non
> > > >>>>>> stop on my box (already executed 100+ times) and I couldn’t
> > > replicate
> > > >>>> the
> > > >>>>>> issue:
> > > >>>>>>
> > > >>>>>> Any ideias?
> > > >>>>>>
> > > >>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> > > >>>>> jlmonteiro@tomitribe.com>
> > > >>>>>> wrote:
> > > >>>>>>>
> > > >>>>>>> I'll take the first one first
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> Jean-Louis Monteiro
> > > >>>>>>> http://twitter.com/jlouismonteiro
> > > >>>>>>> http://www.tomitribe.com
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > > >>>>>> <ra...@yahoo.com.invalid>
> > > >>>>>>> wrote:
> > > >>>>>>>
> > > >>>>>>>> Thank you JL,
> > > >>>>>>>>
> > > >>>>>>>> At least this test is failing:
> > > >>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > > >>>>>>>>
> > > >>>>>>>> And this one seems to fail randomly.
> > > >>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> > > >>>>>>>>
> > > >>>>>>>> Cheers,
> > > >>>>>>>> Roberto
> > > >>>>>>>>
> > > >>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > > >>>>>> jlmonteiro@tomitribe.com>
> > > >>>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> I have merged a couple of PR and I'm running a full build
> > > locally.
> > > >>>>> I'll
> > > >>>>>>>>> work on fixes any issues if I find some but I'll report first
> > > here
> > > >>>>>>>>> --
> > > >>>>>>>>> Jean-Louis Monteiro
> > > >>>>>>>>> http://twitter.com/jlouismonteiro
> > > >>>>>>>>> http://www.tomitribe.com
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > > >>>>>>>> <ra...@yahoo.com.invalid>
> > > >>>>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> Hey Jon,
> > > >>>>>>>>>>
> > > >>>>>>>>>> The following commit:
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>
> > >
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > > >>>>>>>>>> <
> > > >>>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>
> > >
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> Is failing the test:
> > > >>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > > >>>>>>>>>>
> > > >>>>>>>>>> Can you help?
> > > >>>>>>>>>>
> > > >>>>>>>>>> Cheers,
> > > >>>>>>>>>> Roberto
> > > >>>>>>>>>>
> > > >>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <kamin.feuer.2000@gmx.de
> >
> > > >>>> wrote:
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Hi Cesar,
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> This is a valuable piece of information.
> > > >>>>>>>>>>> That's what I thohght, too when I read the information on
> IRC
> > > ...
> > > >>>>>>>>>>> Thanks that you want to preserve it on the website.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> The JIRA task is now assigned to you.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Frankie
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> --
> > > >>>>>>>>>>> Sent from:
> > > >>>>>>>>>>
> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> Daniel "soro" Cunha
> > > >>> https://twitter.com/dvlc_
> > > >>
> > > >>
> > > >
> > > > --
> > > > Daniel "soro" Cunha
> > > > https://twitter.com/dvlc_
> > >
> > >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

Nice... Thanks!

Em ter, 18 de dez de 2018 11:48 AM, Roberto Cortez
<radcortez@yahoo.com.invalid escreveu:

>  Hi Daniel,
> I didn't yet for the other branches. I'll do it today.
>     On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <
> danielsoro@gmail.com> wrote:
>
>  Hi Roberto,
>
> I saw that you merged the changes on master, did you see the others changes
> for branch 7.0.x and 7.1.x?
>
> Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
> <ra...@yahoo.com.invalid> escreveu:
>
> > Thank you Daniel,
> >
> > I’ll review and merge.
> >
> > Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple
> of
> > days before, but now it happened again. Not sure what is wrong there,
> since
> > we used to pass it.
> >
> > > On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> > >
> > > Hi Roberto,
> > >
> > > the fix which I send is to make sure that the test is using the correct
> > > version for libs.
> > > For example, here
> > >
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > > we have the version of the lib on the code.
> > >
> > > Which means that, if you try run it on TomEE 7.0.x it will never works,
> > > because for that build, it will have openejb-core-7.0.x and not
> > > openejb-core-8.0.0-SNAPSHOT.
> > >
> > > That is the issue, we need to get the correct reference for the lib to
> > make
> > > sure that the command will works.
> > >
> > > About the test stuck, reading the stacktrace that you send, seems
> > something
> > > during TCK test. Is it?
> > >
> > > Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > > <ra...@yahoo.com.invalid> escreveu:
> > >
> > >> Hi Daniel,
> > >>
> > >> Can you please explain what the issue was?
> > >>
> > >> Also, it seems our build is getting killed for taking to long due to
> > some
> > >> tests being stuck?
> > >>
> > >> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> > >> INFO: RemoteInitialContextCreated{providerUri=
> > >> http://localhost:40395/tomee/ejb}
> > >> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> > >> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> > >> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object
> > input
> > >> stream to server (OEJP/4.6) : null}
> > >> Dec 17, 2018 12:10:27 PM
> > >> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> > beforeInvocation
> > >> INFO: Invoke
> > >>
> >
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> > >> 1,203/1,571 Failed tests: 59 (476)
> > >> Dec 17, 2018 12:10:27 PM
> > >> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> > >> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> > >> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> > build
> > >> INFO: Test archive built [info:
> > >>
> >
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> > >> time: 16 ms]
> > >> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> > >> INFO: RemoteInitialContextCreated{providerUri=
> > >> http://localhost:40395/tomee/ejb}
> > >>
> > >>
> > >> command timed out: 18000 seconds without output running ['mvn', '-U',
> > >> '--show-version', '--fail-at-end',
> > >> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> > >> '-Pall-adapters', '-Dsurefire.useFile=false',
> '-DdisableXmlReport=true',
> > >> '-Dopenejb.arquillian.debug=true',
> > >> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> > >> process killed by signal 9
> > >> program finished with exit code -1
> > >> elapsedTime=38754.464253
> > >>
> > >> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
> > logs
> > >> in between...
> > >>
> > >>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org>
> wrote:
> > >>>
> > >>> Hey folks,
> > >>>
> > >>> we found an issue on TomEECliIT test.
> > >>> I've opened fixes for test in all branch, please take a look on it.
> > >>>
> > >>> Fixes:
> > >>> master -> https://github.com/apache/tomee/pull/288
> > >>> 7.1.x -> https://github.com/apache/tomee/pull/287
> > >>> 7.0.x -> https://github.com/apache/tomee/pull/286
> > >>>
> > >>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> > >>> jlmonteiro@tomitribe.com> escreveu:
> > >>>
> > >>>> Please wait a minute lol
> > >>>> I'd rather have you help me if needed.
> > >>>>
> > >>>> First I don't have the feeling I spent time for nothing on it and
> > >> second,
> > >>>> at least I will learn something.
> > >>>>
> > >>>> --
> > >>>> Jean-Louis Monteiro
> > >>>> http://twitter.com/jlouismonteiro
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>
> > >>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> > >>>> jonathan.gallimore@gmail.com> wrote:
> > >>>>
> > >>>>> I added this test, and it was pretty stable. Happy to help look
> into
> > >> it.
> > >>>>>
> > >>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> > >>>>> <ra...@yahoo.com.invalid>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> It seems the build just randomly fails with this test:
> > >>>>>> AutoConnectionTrackerTest.test
> > >>>>>>
> > >>>>>> [ERROR] Failures:
> > >>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> > was:<0>
> > >>>>>>
> > >>>>>> Sometimes it passes, sometimes it fails. I suspect it may be
> related
> > >>>> with
> > >>>>>> some timing issues / box speed of the build bot. I’m running the
> > test
> > >>>> non
> > >>>>>> stop on my box (already executed 100+ times) and I couldn’t
> > replicate
> > >>>> the
> > >>>>>> issue:
> > >>>>>>
> > >>>>>> Any ideias?
> > >>>>>>
> > >>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> > >>>>> jlmonteiro@tomitribe.com>
> > >>>>>> wrote:
> > >>>>>>>
> > >>>>>>> I'll take the first one first
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> Jean-Louis Monteiro
> > >>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>> http://www.tomitribe.com
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > >>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>> wrote:
> > >>>>>>>
> > >>>>>>>> Thank you JL,
> > >>>>>>>>
> > >>>>>>>> At least this test is failing:
> > >>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>
> > >>>>>>>> And this one seems to fail randomly.
> > >>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> > >>>>>>>>
> > >>>>>>>> Cheers,
> > >>>>>>>> Roberto
> > >>>>>>>>
> > >>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > >>>>>> jlmonteiro@tomitribe.com>
> > >>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> I have merged a couple of PR and I'm running a full build
> > locally.
> > >>>>> I'll
> > >>>>>>>>> work on fixes any issues if I find some but I'll report first
> > here
> > >>>>>>>>> --
> > >>>>>>>>> Jean-Louis Monteiro
> > >>>>>>>>> http://twitter.com/jlouismonteiro
> > >>>>>>>>> http://www.tomitribe.com
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > >>>>>>>> <ra...@yahoo.com.invalid>
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> Hey Jon,
> > >>>>>>>>>>
> > >>>>>>>>>> The following commit:
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>> <
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> Is failing the test:
> > >>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>>>>>>>
> > >>>>>>>>>> Can you help?
> > >>>>>>>>>>
> > >>>>>>>>>> Cheers,
> > >>>>>>>>>> Roberto
> > >>>>>>>>>>
> > >>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
> > >>>> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>> Hi Cesar,
> > >>>>>>>>>>>
> > >>>>>>>>>>>> This is a valuable piece of information.
> > >>>>>>>>>>> That's what I thohght, too when I read the information on IRC
> > ...
> > >>>>>>>>>>> Thanks that you want to preserve it on the website.
> > >>>>>>>>>>>
> > >>>>>>>>>>> The JIRA task is now assigned to you.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Frankie
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> --
> > >>>>>>>>>>> Sent from:
> > >>>>>>>>>>
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> --
> > >>> Daniel "soro" Cunha
> > >>> https://twitter.com/dvlc_
> > >>
> > >>
> > >
> > > --
> > > Daniel "soro" Cunha
> > > https://twitter.com/dvlc_
> >
> >
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

 Hi Daniel,
I didn't yet for the other branches. I'll do it today.
    On Tuesday, December 18, 2018, 1:37:34 PM GMT, Daniel Cunha <da...@gmail.com> wrote:  
 
 Hi Roberto,

I saw that you merged the changes on master, did you see the others changes
for branch 7.0.x and 7.1.x?

Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> Thank you Daniel,
>
> I’ll review and merge.
>
> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple of
> days before, but now it happened again. Not sure what is wrong there, since
> we used to pass it.
>
> > On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> >
> > Hi Roberto,
> >
> > the fix which I send is to make sure that the test is using the correct
> > version for libs.
> > For example, here
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > we have the version of the lib on the code.
> >
> > Which means that, if you try run it on TomEE 7.0.x it will never works,
> > because for that build, it will have openejb-core-7.0.x and not
> > openejb-core-8.0.0-SNAPSHOT.
> >
> > That is the issue, we need to get the correct reference for the lib to
> make
> > sure that the command will works.
> >
> > About the test stuck, reading the stacktrace that you send, seems
> something
> > during TCK test. Is it?
> >
> > Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > <ra...@yahoo.com.invalid> escreveu:
> >
> >> Hi Daniel,
> >>
> >> Can you please explain what the issue was?
> >>
> >> Also, it seems our build is getting killed for taking to long due to
> some
> >> tests being stuck?
> >>
> >> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> >> INFO: RemoteInitialContextCreated{providerUri=
> >> http://localhost:40395/tomee/ejb}
> >> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> >> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> >> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object
> input
> >> stream to server (OEJP/4.6) : null}
> >> Dec 17, 2018 12:10:27 PM
> >> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> beforeInvocation
> >> INFO: Invoke
> >>
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> >> 1,203/1,571 Failed tests: 59 (476)
> >> Dec 17, 2018 12:10:27 PM
> >> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> >> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> >> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> build
> >> INFO: Test archive built [info:
> >>
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> >> time: 16 ms]
> >> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> >> INFO: RemoteInitialContextCreated{providerUri=
> >> http://localhost:40395/tomee/ejb}
> >>
> >>
> >> command timed out: 18000 seconds without output running ['mvn', '-U',
> >> '--show-version', '--fail-at-end',
> >> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> >> '-Pall-adapters', '-Dsurefire.useFile=false', '-DdisableXmlReport=true',
> >> '-Dopenejb.arquillian.debug=true',
> >> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> >> process killed by signal 9
> >> program finished with exit code -1
> >> elapsedTime=38754.464253
> >>
> >> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
> logs
> >> in between...
> >>
> >>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org> wrote:
> >>>
> >>> Hey folks,
> >>>
> >>> we found an issue on TomEECliIT test.
> >>> I've opened fixes for test in all branch, please take a look on it.
> >>>
> >>> Fixes:
> >>> master -> https://github.com/apache/tomee/pull/288
> >>> 7.1.x -> https://github.com/apache/tomee/pull/287
> >>> 7.0.x -> https://github.com/apache/tomee/pull/286
> >>>
> >>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com> escreveu:
> >>>
> >>>> Please wait a minute lol
> >>>> I'd rather have you help me if needed.
> >>>>
> >>>> First I don't have the feeling I spent time for nothing on it and
> >> second,
> >>>> at least I will learn something.
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> wrote:
> >>>>
> >>>>> I added this test, and it was pretty stable. Happy to help look into
> >> it.
> >>>>>
> >>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> >>>>> <ra...@yahoo.com.invalid>
> >>>>> wrote:
> >>>>>
> >>>>>> It seems the build just randomly fails with this test:
> >>>>>> AutoConnectionTrackerTest.test
> >>>>>>
> >>>>>> [ERROR] Failures:
> >>>>>> [ERROR]  AutoConnectionTrackerTest.test:198 expected:<1> but
> was:<0>
> >>>>>>
> >>>>>> Sometimes it passes, sometimes it fails. I suspect it may be related
> >>>> with
> >>>>>> some timing issues / box speed of the build bot. I’m running the
> test
> >>>> non
> >>>>>> stop on my box (already executed 100+ times) and I couldn’t
> replicate
> >>>> the
> >>>>>> issue:
> >>>>>>
> >>>>>> Any ideias?
> >>>>>>
> >>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> >>>>> jlmonteiro@tomitribe.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> I'll take the first one first
> >>>>>>>
> >>>>>>> --
> >>>>>>> Jean-Louis Monteiro
> >>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>> http://www.tomitribe.com
> >>>>>>>
> >>>>>>>
> >>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Thank you JL,
> >>>>>>>>
> >>>>>>>> At least this test is failing:
> >>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>
> >>>>>>>> And this one seems to fail randomly.
> >>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Roberto
> >>>>>>>>
> >>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> >>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I have merged a couple of PR and I'm running a full build
> locally.
> >>>>> I'll
> >>>>>>>>> work on fixes any issues if I find some but I'll report first
> here
> >>>>>>>>> --
> >>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hey Jon,
> >>>>>>>>>>
> >>>>>>>>>> The following commit:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>> <
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Is failing the test:
> >>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>
> >>>>>>>>>> Can you help?
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Roberto
> >>>>>>>>>>
> >>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
> >>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi Cesar,
> >>>>>>>>>>>
> >>>>>>>>>>>> This is a valuable piece of information.
> >>>>>>>>>>> That's what I thohght, too when I read the information on IRC
> ...
> >>>>>>>>>>> Thanks that you want to preserve it on the website.
> >>>>>>>>>>>
> >>>>>>>>>>> The JIRA task is now assigned to you.
> >>>>>>>>>>>
> >>>>>>>>>>> Frankie
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Sent from:
> >>>>>>>>>>
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Daniel "soro" Cunha
> >>> https://twitter.com/dvlc_
> >>
> >>
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_  

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Hi Roberto,

I saw that you merged the changes on master, did you see the others changes
for branch 7.0.x and 7.1.x?

Em seg, 17 de dez de 2018 às 18:07, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> Thank you Daniel,
>
> I’ll review and merge.
>
> Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple of
> days before, but now it happened again. Not sure what is wrong there, since
> we used to pass it.
>
> > On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> >
> > Hi Roberto,
> >
> > the fix which I send is to make sure that the test is using the correct
> > version for libs.
> > For example, here
> >
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> > we have the version of the lib on the code.
> >
> > Which means that, if you try run it on TomEE 7.0.x it will never works,
> > because for that build, it will have openejb-core-7.0.x and not
> > openejb-core-8.0.0-SNAPSHOT.
> >
> > That is the issue, we need to get the correct reference for the lib to
> make
> > sure that the command will works.
> >
> > About the test stuck, reading the stacktrace that you send, seems
> something
> > during TCK test. Is it?
> >
> > Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> > <ra...@yahoo.com.invalid> escreveu:
> >
> >> Hi Daniel,
> >>
> >> Can you please explain what the issue was?
> >>
> >> Also, it seems our build is getting killed for taking to long due to
> some
> >> tests being stuck?
> >>
> >> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> >> INFO: RemoteInitialContextCreated{providerUri=
> >> http://localhost:40395/tomee/ejb}
> >> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> >> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> >> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object
> input
> >> stream to server (OEJP/4.6) : null}
> >> Dec 17, 2018 12:10:27 PM
> >> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener
> beforeInvocation
> >> INFO: Invoke
> >>
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> >> 1,203/1,571 Failed tests: 59 (476)
> >> Dec 17, 2018 12:10:27 PM
> >> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> >> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> >> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder
> build
> >> INFO: Test archive built [info:
> >>
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> >> time: 16 ms]
> >> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> >> INFO: RemoteInitialContextCreated{providerUri=
> >> http://localhost:40395/tomee/ejb}
> >>
> >>
> >> command timed out: 18000 seconds without output running ['mvn', '-U',
> >> '--show-version', '--fail-at-end',
> >> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> >> '-Pall-adapters', '-Dsurefire.useFile=false', '-DdisableXmlReport=true',
> >> '-Dopenejb.arquillian.debug=true',
> >> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> >> process killed by signal 9
> >> program finished with exit code -1
> >> elapsedTime=38754.464253
> >>
> >> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No
> logs
> >> in between...
> >>
> >>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org> wrote:
> >>>
> >>> Hey folks,
> >>>
> >>> we found an issue on TomEECliIT test.
> >>> I've opened fixes for test in all branch, please take a look on it.
> >>>
> >>> Fixes:
> >>> master -> https://github.com/apache/tomee/pull/288
> >>> 7.1.x -> https://github.com/apache/tomee/pull/287
> >>> 7.0.x -> https://github.com/apache/tomee/pull/286
> >>>
> >>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com> escreveu:
> >>>
> >>>> Please wait a minute lol
> >>>> I'd rather have you help me if needed.
> >>>>
> >>>> First I don't have the feeling I spent time for nothing on it and
> >> second,
> >>>> at least I will learn something.
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> wrote:
> >>>>
> >>>>> I added this test, and it was pretty stable. Happy to help look into
> >> it.
> >>>>>
> >>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> >>>>> <ra...@yahoo.com.invalid>
> >>>>> wrote:
> >>>>>
> >>>>>> It seems the build just randomly fails with this test:
> >>>>>> AutoConnectionTrackerTest.test
> >>>>>>
> >>>>>> [ERROR] Failures:
> >>>>>> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but
> was:<0>
> >>>>>>
> >>>>>> Sometimes it passes, sometimes it fails. I suspect it may be related
> >>>> with
> >>>>>> some timing issues / box speed of the build bot. I’m running the
> test
> >>>> non
> >>>>>> stop on my box (already executed 100+ times) and I couldn’t
> replicate
> >>>> the
> >>>>>> issue:
> >>>>>>
> >>>>>> Any ideias?
> >>>>>>
> >>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> >>>>> jlmonteiro@tomitribe.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> I'll take the first one first
> >>>>>>>
> >>>>>>> --
> >>>>>>> Jean-Louis Monteiro
> >>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>> http://www.tomitribe.com
> >>>>>>>
> >>>>>>>
> >>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Thank you JL,
> >>>>>>>>
> >>>>>>>> At least this test is failing:
> >>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>
> >>>>>>>> And this one seems to fail randomly.
> >>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Roberto
> >>>>>>>>
> >>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> >>>>>> jlmonteiro@tomitribe.com>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> I have merged a couple of PR and I'm running a full build
> locally.
> >>>>> I'll
> >>>>>>>>> work on fixes any issues if I find some but I'll report first
> here
> >>>>>>>>> --
> >>>>>>>>> Jean-Louis Monteiro
> >>>>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>>>> http://www.tomitribe.com
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >>>>>>>> <ra...@yahoo.com.invalid>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Hey Jon,
> >>>>>>>>>>
> >>>>>>>>>> The following commit:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>> <
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Is failing the test:
> >>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>>>
> >>>>>>>>>> Can you help?
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Roberto
> >>>>>>>>>>
> >>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
> >>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> Hi Cesar,
> >>>>>>>>>>>
> >>>>>>>>>>>> This is a valuable piece of information.
> >>>>>>>>>>> That's what I thohght, too when I read the information on IRC
> ...
> >>>>>>>>>>> Thanks that you want to preserve it on the website.
> >>>>>>>>>>>
> >>>>>>>>>>> The JIRA task is now assigned to you.
> >>>>>>>>>>>
> >>>>>>>>>>> Frankie
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Sent from:
> >>>>>>>>>>
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Daniel "soro" Cunha
> >>> https://twitter.com/dvlc_
> >>
> >>
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Thank you Daniel,

I’ll review and merge.

Yeah it seems it gets stuck in the CDI TCK. I saw it happening a couple of days before, but now it happened again. Not sure what is wrong there, since we used to pass it.

> On 17 Dec 2018, at 20:16, Daniel Cunha <da...@gmail.com> wrote:
> 
> Hi Roberto,
> 
> the fix which I send is to make sure that the test is using the correct
> version for libs.
> For example, here
> https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
> we have the version of the lib on the code.
> 
> Which means that, if you try run it on TomEE 7.0.x it will never works,
> because for that build, it will have openejb-core-7.0.x and not
> openejb-core-8.0.0-SNAPSHOT.
> 
> That is the issue, we need to get the correct reference for the lib to make
> sure that the command will works.
> 
> About the test stuck, reading the stacktrace that you send, seems something
> during TCK test. Is it?
> 
> Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
> <ra...@yahoo.com.invalid> escreveu:
> 
>> Hi Daniel,
>> 
>> Can you please explain what the issue was?
>> 
>> Also, it seems our build is getting killed for taking to long due to some
>> tests being stuck?
>> 
>> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
>> INFO: RemoteInitialContextCreated{providerUri=
>> http://localhost:40395/tomee/ejb}
>> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
>> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
>> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object input
>> stream to server (OEJP/4.6) : null}
>> Dec 17, 2018 12:10:27 PM
>> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener beforeInvocation
>> INFO: Invoke
>> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
>> 1,203/1,571 Failed tests: 59 (476)
>> Dec 17, 2018 12:10:27 PM
>> org.apache.openejb.arquillian.common.TomEEContainer undeploy
>> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
>> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder build
>> INFO: Test archive built [info:
>> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
>> time: 16 ms]
>> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
>> INFO: RemoteInitialContextCreated{providerUri=
>> http://localhost:40395/tomee/ejb}
>> 
>> 
>> command timed out: 18000 seconds without output running ['mvn', '-U',
>> '--show-version', '--fail-at-end',
>> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
>> '-Pall-adapters', '-Dsurefire.useFile=false', '-DdisableXmlReport=true',
>> '-Dopenejb.arquillian.debug=true',
>> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
>> process killed by signal 9
>> program finished with exit code -1
>> elapsedTime=38754.464253
>> 
>> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No logs
>> in between...
>> 
>>> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org> wrote:
>>> 
>>> Hey folks,
>>> 
>>> we found an issue on TomEECliIT test.
>>> I've opened fixes for test in all branch, please take a look on it.
>>> 
>>> Fixes:
>>> master -> https://github.com/apache/tomee/pull/288
>>> 7.1.x -> https://github.com/apache/tomee/pull/287
>>> 7.0.x -> https://github.com/apache/tomee/pull/286
>>> 
>>> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com> escreveu:
>>> 
>>>> Please wait a minute lol
>>>> I'd rather have you help me if needed.
>>>> 
>>>> First I don't have the feeling I spent time for nothing on it and
>> second,
>>>> at least I will learn something.
>>>> 
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>> 
>>>> 
>>>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>>>> jonathan.gallimore@gmail.com> wrote:
>>>> 
>>>>> I added this test, and it was pretty stable. Happy to help look into
>> it.
>>>>> 
>>>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>>>> <ra...@yahoo.com.invalid>
>>>>> wrote:
>>>>> 
>>>>>> It seems the build just randomly fails with this test:
>>>>>> AutoConnectionTrackerTest.test
>>>>>> 
>>>>>> [ERROR] Failures:
>>>>>> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
>>>>>> 
>>>>>> Sometimes it passes, sometimes it fails. I suspect it may be related
>>>> with
>>>>>> some timing issues / box speed of the build bot. I’m running the test
>>>> non
>>>>>> stop on my box (already executed 100+ times) and I couldn’t replicate
>>>> the
>>>>>> issue:
>>>>>> 
>>>>>> Any ideias?
>>>>>> 
>>>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>>>> jlmonteiro@tomitribe.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> I'll take the first one first
>>>>>>> 
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>> 
>>>>>>> 
>>>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>>>> <ra...@yahoo.com.invalid>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Thank you JL,
>>>>>>>> 
>>>>>>>> At least this test is failing:
>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>> 
>>>>>>>> And this one seems to fail randomly.
>>>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Roberto
>>>>>>>> 
>>>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>>>> jlmonteiro@tomitribe.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> I have merged a couple of PR and I'm running a full build locally.
>>>>> I'll
>>>>>>>>> work on fixes any issues if I find some but I'll report first here
>>>>>>>>> --
>>>>>>>>> Jean-Louis Monteiro
>>>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>>>> http://www.tomitribe.com
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>>>> <ra...@yahoo.com.invalid>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Hey Jon,
>>>>>>>>>> 
>>>>>>>>>> The following commit:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>> <
>>>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Is failing the test:
>>>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>>>> 
>>>>>>>>>> Can you help?
>>>>>>>>>> 
>>>>>>>>>> Cheers,
>>>>>>>>>> Roberto
>>>>>>>>>> 
>>>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi Cesar,
>>>>>>>>>>> 
>>>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>>>> That's what I thohght, too when I read the information on IRC ...
>>>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>>>> 
>>>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>>>> 
>>>>>>>>>>> Frankie
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> --
>>>>>>>>>>> Sent from:
>>>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Daniel "soro" Cunha
>>> https://twitter.com/dvlc_
>> 
>> 
> 
> -- 
> Daniel "soro" Cunha
> https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Hi Roberto,

the fix which I send is to make sure that the test is using the correct
version for libs.
For example, here
https://github.com/apache/tomee/pull/287/files#diff-88785d5b00bc141a892b2e21e6aaabcaL70
we have the version of the lib on the code.

Which means that, if you try run it on TomEE 7.0.x it will never works,
because for that build, it will have openejb-core-7.0.x and not
openejb-core-8.0.0-SNAPSHOT.

That is the issue, we need to get the correct reference for the lib to make
sure that the command will works.

About the test stuck, reading the stacktrace that you send, seems something
during TCK test. Is it?

Em seg, 17 de dez de 2018 às 17:08, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> Hi Daniel,
>
> Can you please explain what the issue was?
>
> Also, it seems our build is getting killed for taking to long due to some
> tests being stuck?
>
> Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=
> http://localhost:40395/tomee/ejb}
> Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
> WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb}
> JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object input
> stream to server (OEJP/4.6) : null}
> Dec 17, 2018 12:10:27 PM
> org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener beforeInvocation
> INFO: Invoke
> FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor:
> 1,203/1,571 Failed tests: 59 (476)
> Dec 17, 2018 12:10:27 PM
> org.apache.openejb.arquillian.common.TomEEContainer undeploy
> WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
> Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder build
> INFO: Test archive built [info:
> org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest,
> time: 16 ms]
> Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
> INFO: RemoteInitialContextCreated{providerUri=
> http://localhost:40395/tomee/ejb}
>
>
> command timed out: 18000 seconds without output running ['mvn', '-U',
> '--show-version', '--fail-at-end',
> '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install',
> '-Pall-adapters', '-Dsurefire.useFile=false', '-DdisableXmlReport=true',
> '-Dopenejb.arquillian.debug=true',
> '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
> process killed by signal 9
> program finished with exit code -1
> elapsedTime=38754.464253
>
> Last log is from 12:10:28. Process was killed around 17:10:30 PM. No logs
> in between...
>
> > On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org> wrote:
> >
> > Hey folks,
> >
> > we found an issue on TomEECliIT test.
> > I've opened fixes for test in all branch, please take a look on it.
> >
> > Fixes:
> > master -> https://github.com/apache/tomee/pull/288
> > 7.1.x -> https://github.com/apache/tomee/pull/287
> > 7.0.x -> https://github.com/apache/tomee/pull/286
> >
> > Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> escreveu:
> >
> >> Please wait a minute lol
> >> I'd rather have you help me if needed.
> >>
> >> First I don't have the feeling I spent time for nothing on it and
> second,
> >> at least I will learn something.
> >>
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> >> jonathan.gallimore@gmail.com> wrote:
> >>
> >>> I added this test, and it was pretty stable. Happy to help look into
> it.
> >>>
> >>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> >>> <ra...@yahoo.com.invalid>
> >>> wrote:
> >>>
> >>>> It seems the build just randomly fails with this test:
> >>>> AutoConnectionTrackerTest.test
> >>>>
> >>>> [ERROR] Failures:
> >>>> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
> >>>>
> >>>> Sometimes it passes, sometimes it fails. I suspect it may be related
> >> with
> >>>> some timing issues / box speed of the build bot. I’m running the test
> >> non
> >>>> stop on my box (already executed 100+ times) and I couldn’t replicate
> >> the
> >>>> issue:
> >>>>
> >>>> Any ideias?
> >>>>
> >>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com>
> >>>> wrote:
> >>>>>
> >>>>> I'll take the first one first
> >>>>>
> >>>>> --
> >>>>> Jean-Louis Monteiro
> >>>>> http://twitter.com/jlouismonteiro
> >>>>> http://www.tomitribe.com
> >>>>>
> >>>>>
> >>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> >>>> <ra...@yahoo.com.invalid>
> >>>>> wrote:
> >>>>>
> >>>>>> Thank you JL,
> >>>>>>
> >>>>>> At least this test is failing:
> >>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>
> >>>>>> And this one seems to fail randomly.
> >>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Roberto
> >>>>>>
> >>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> >>>> jlmonteiro@tomitribe.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> I have merged a couple of PR and I'm running a full build locally.
> >>> I'll
> >>>>>>> work on fixes any issues if I find some but I'll report first here
> >>>>>>> --
> >>>>>>> Jean-Louis Monteiro
> >>>>>>> http://twitter.com/jlouismonteiro
> >>>>>>> http://www.tomitribe.com
> >>>>>>>
> >>>>>>>
> >>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hey Jon,
> >>>>>>>>
> >>>>>>>> The following commit:
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>> <
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Is failing the test:
> >>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>>>>>
> >>>>>>>> Can you help?
> >>>>>>>>
> >>>>>>>> Cheers,
> >>>>>>>> Roberto
> >>>>>>>>
> >>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
> >> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi Cesar,
> >>>>>>>>>
> >>>>>>>>>> This is a valuable piece of information.
> >>>>>>>>> That's what I thohght, too when I read the information on IRC ...
> >>>>>>>>> Thanks that you want to preserve it on the website.
> >>>>>>>>>
> >>>>>>>>> The JIRA task is now assigned to you.
> >>>>>>>>>
> >>>>>>>>> Frankie
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Sent from:
> >>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >>
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Hi Daniel,

Can you please explain what the issue was?

Also, it seems our build is getting killed for taking to long due to some tests being stuck?

Dec 17, 2018 12:06:54 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=http://localhost:40395/tomee/ejb}
Dec 17, 2018 12:10:27 PM org.apache.openejb.client.EventLogger log
WARNING: RequestFailed{server=http://localhost:40395/tomee/ejb} JNDI_LOOKUP:/openejb/DeployerBusinessRemote {error=Cannot open object input stream to server (OEJP/4.6) : null}
Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.impl.testng.ProgressLoggingTestListener beforeInvocation
INFO: Invoke FinalMethodWithInheritedStereotypeInterceptorTest.testFinalClassWithInheritedStereotypeInterceptor: 1,203/1,571 Failed tests: 59 (476)
Dec 17, 2018 12:10:27 PM org.apache.openejb.arquillian.common.TomEEContainer undeploy
WARNING: d18bed2dab5751811c186784503e2ad69ae6c9.war was not deployed
Dec 17, 2018 12:10:27 PM org.jboss.cdi.tck.shrinkwrap.ArchiveBuilder build
INFO: Test archive built [info: org.jboss.cdi.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.InterceptorCalledBeforeDecoratorTest, time: 16 ms]
Dec 17, 2018 12:10:28 PM org.apache.openejb.client.EventLogger log
INFO: RemoteInitialContextCreated{providerUri=http://localhost:40395/tomee/ejb}


command timed out: 18000 seconds without output running ['mvn', '-U', '--show-version', '--fail-at-end', '-Djava.io.tmpdir=/tmp/tomee-trunk-ubuntu-jvm8', 'clean', 'install', '-Pall-adapters', '-Dsurefire.useFile=false', '-DdisableXmlReport=true', '-Dopenejb.arquillian.debug=true', '-DTOMEE_LOCK_FILE=/tmp/tomee.port.lock'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=38754.464253

Last log is from 12:10:28. Process was killed around 17:10:30 PM. No logs in between...

> On 17 Dec 2018, at 17:27, Daniel Cunha <da...@apache.org> wrote:
> 
> Hey folks,
> 
> we found an issue on TomEECliIT test.
> I've opened fixes for test in all branch, please take a look on it.
> 
> Fixes:
> master -> https://github.com/apache/tomee/pull/288
> 7.1.x -> https://github.com/apache/tomee/pull/287
> 7.0.x -> https://github.com/apache/tomee/pull/286
> 
> Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> escreveu:
> 
>> Please wait a minute lol
>> I'd rather have you help me if needed.
>> 
>> First I don't have the feeling I spent time for nothing on it and second,
>> at least I will learn something.
>> 
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 
>> 
>> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>> 
>>> I added this test, and it was pretty stable. Happy to help look into it.
>>> 
>>> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
>>> <ra...@yahoo.com.invalid>
>>> wrote:
>>> 
>>>> It seems the build just randomly fails with this test:
>>>> AutoConnectionTrackerTest.test
>>>> 
>>>> [ERROR] Failures:
>>>> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
>>>> 
>>>> Sometimes it passes, sometimes it fails. I suspect it may be related
>> with
>>>> some timing issues / box speed of the build bot. I’m running the test
>> non
>>>> stop on my box (already executed 100+ times) and I couldn’t replicate
>> the
>>>> issue:
>>>> 
>>>> Any ideias?
>>>> 
>>>>> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com>
>>>> wrote:
>>>>> 
>>>>> I'll take the first one first
>>>>> 
>>>>> --
>>>>> Jean-Louis Monteiro
>>>>> http://twitter.com/jlouismonteiro
>>>>> http://www.tomitribe.com
>>>>> 
>>>>> 
>>>>> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
>>>> <ra...@yahoo.com.invalid>
>>>>> wrote:
>>>>> 
>>>>>> Thank you JL,
>>>>>> 
>>>>>> At least this test is failing:
>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>> 
>>>>>> And this one seems to fail randomly.
>>>>>> org.apache.openejb.resource.AutoConnectionTrackerTest
>>>>>> 
>>>>>> Cheers,
>>>>>> Roberto
>>>>>> 
>>>>>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
>>>> jlmonteiro@tomitribe.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> I have merged a couple of PR and I'm running a full build locally.
>>> I'll
>>>>>>> work on fixes any issues if I find some but I'll report first here
>>>>>>> --
>>>>>>> Jean-Louis Monteiro
>>>>>>> http://twitter.com/jlouismonteiro
>>>>>>> http://www.tomitribe.com
>>>>>>> 
>>>>>>> 
>>>>>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>>>>>> <ra...@yahoo.com.invalid>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Hey Jon,
>>>>>>>> 
>>>>>>>> The following commit:
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>> <
>>>>>>>> 
>>>>>> 
>>>> 
>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> Is failing the test:
>>>>>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>>>>>> 
>>>>>>>> Can you help?
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Roberto
>>>>>>>> 
>>>>>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
>> wrote:
>>>>>>>>> 
>>>>>>>>> Hi Cesar,
>>>>>>>>> 
>>>>>>>>>> This is a valuable piece of information.
>>>>>>>>> That's what I thohght, too when I read the information on IRC ...
>>>>>>>>> Thanks that you want to preserve it on the website.
>>>>>>>>> 
>>>>>>>>> The JIRA task is now assigned to you.
>>>>>>>>> 
>>>>>>>>> Frankie
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Sent from:
>>>>>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>> 
>> 
> 
> 
> -- 
> Daniel "soro" Cunha
> https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

Hey folks,

we found an issue on TomEECliIT test.
I've opened fixes for test in all branch, please take a look on it.

Fixes:
master -> https://github.com/apache/tomee/pull/288
7.1.x -> https://github.com/apache/tomee/pull/287
7.0.x -> https://github.com/apache/tomee/pull/286

Em sex, 14 de dez de 2018 às 12:36, Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> escreveu:

> Please wait a minute lol
> I'd rather have you help me if needed.
>
> First I don't have the feeling I spent time for nothing on it and second,
> at least I will learn something.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > I added this test, and it was pretty stable. Happy to help look into it.
> >
> > On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> > <ra...@yahoo.com.invalid>
> > wrote:
> >
> > > It seems the build just randomly fails with this test:
> > > AutoConnectionTrackerTest.test
> > >
> > > [ERROR] Failures:
> > > [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
> > >
> > > Sometimes it passes, sometimes it fails. I suspect it may be related
> with
> > > some timing issues / box speed of the build bot. I’m running the test
> non
> > > stop on my box (already executed 100+ times) and I couldn’t replicate
> the
> > > issue:
> > >
> > > Any ideias?
> > >
> > > > On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com>
> > > wrote:
> > > >
> > > > I'll take the first one first
> > > >
> > > > --
> > > > Jean-Louis Monteiro
> > > > http://twitter.com/jlouismonteiro
> > > > http://www.tomitribe.com
> > > >
> > > >
> > > > On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > > <ra...@yahoo.com.invalid>
> > > > wrote:
> > > >
> > > >> Thank you JL,
> > > >>
> > > >> At least this test is failing:
> > > >> org.apache.openejb.config.rules.CheckMissingClassTest
> > > >>
> > > >> And this one seems to fail randomly.
> > > >> org.apache.openejb.resource.AutoConnectionTrackerTest
> > > >>
> > > >> Cheers,
> > > >> Roberto
> > > >>
> > > >>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com>
> > > >> wrote:
> > > >>>
> > > >>> I have merged a couple of PR and I'm running a full build locally.
> > I'll
> > > >>> work on fixes any issues if I find some but I'll report first here
> > > >>> --
> > > >>> Jean-Louis Monteiro
> > > >>> http://twitter.com/jlouismonteiro
> > > >>> http://www.tomitribe.com
> > > >>>
> > > >>>
> > > >>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > > >> <ra...@yahoo.com.invalid>
> > > >>> wrote:
> > > >>>
> > > >>>> Hey Jon,
> > > >>>>
> > > >>>> The following commit:
> > > >>>>
> > > >>>>
> > > >>
> > >
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > > >>>> <
> > > >>>>
> > > >>
> > >
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > > >>>>>
> > > >>>>
> > > >>>> Is failing the test:
> > > >>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > > >>>>
> > > >>>> Can you help?
> > > >>>>
> > > >>>> Cheers,
> > > >>>> Roberto
> > > >>>>
> > > >>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de>
> wrote:
> > > >>>>>
> > > >>>>> Hi Cesar,
> > > >>>>>
> > > >>>>>> This is a valuable piece of information.
> > > >>>>> That's what I thohght, too when I read the information on IRC ...
> > > >>>>> Thanks that you want to preserve it on the website.
> > > >>>>>
> > > >>>>> The JIRA task is now assigned to you.
> > > >>>>>
> > > >>>>> Frankie
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> --
> > > >>>>> Sent from:
> > > >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > >>>>
> > > >>>>
> > > >>
> > > >>
> > >
> > >
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Please wait a minute lol
I'd rather have you help me if needed.

First I don't have the feeling I spent time for nothing on it and second,
at least I will learn something.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 14, 2018 at 4:33 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I added this test, and it was pretty stable. Happy to help look into it.
>
> On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez
> <ra...@yahoo.com.invalid>
> wrote:
>
> > It seems the build just randomly fails with this test:
> > AutoConnectionTrackerTest.test
> >
> > [ERROR] Failures:
> > [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
> >
> > Sometimes it passes, sometimes it fails. I suspect it may be related with
> > some timing issues / box speed of the build bot. I’m running the test non
> > stop on my box (already executed 100+ times) and I couldn’t replicate the
> > issue:
> >
> > Any ideias?
> >
> > > On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> > wrote:
> > >
> > > I'll take the first one first
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> > <ra...@yahoo.com.invalid>
> > > wrote:
> > >
> > >> Thank you JL,
> > >>
> > >> At least this test is failing:
> > >> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>
> > >> And this one seems to fail randomly.
> > >> org.apache.openejb.resource.AutoConnectionTrackerTest
> > >>
> > >> Cheers,
> > >> Roberto
> > >>
> > >>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com>
> > >> wrote:
> > >>>
> > >>> I have merged a couple of PR and I'm running a full build locally.
> I'll
> > >>> work on fixes any issues if I find some but I'll report first here
> > >>> --
> > >>> Jean-Louis Monteiro
> > >>> http://twitter.com/jlouismonteiro
> > >>> http://www.tomitribe.com
> > >>>
> > >>>
> > >>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> > >> <ra...@yahoo.com.invalid>
> > >>> wrote:
> > >>>
> > >>>> Hey Jon,
> > >>>>
> > >>>> The following commit:
> > >>>>
> > >>>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>> <
> > >>>>
> > >>
> >
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> > >>>>>
> > >>>>
> > >>>> Is failing the test:
> > >>>> org.apache.openejb.config.rules.CheckMissingClassTest
> > >>>>
> > >>>> Can you help?
> > >>>>
> > >>>> Cheers,
> > >>>> Roberto
> > >>>>
> > >>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> > >>>>>
> > >>>>> Hi Cesar,
> > >>>>>
> > >>>>>> This is a valuable piece of information.
> > >>>>> That's what I thohght, too when I read the information on IRC ...
> > >>>>> Thanks that you want to preserve it on the website.
> > >>>>>
> > >>>>> The JIRA task is now assigned to you.
> > >>>>>
> > >>>>> Frankie
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Sent from:
> > >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>>
> > >>>>
> > >>
> > >>
> >
> >
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I added this test, and it was pretty stable. Happy to help look into it.

On Fri, Dec 14, 2018 at 10:44 AM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> It seems the build just randomly fails with this test:
> AutoConnectionTrackerTest.test
>
> [ERROR] Failures:
> [ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>
>
> Sometimes it passes, sometimes it fails. I suspect it may be related with
> some timing issues / box speed of the build bot. I’m running the test non
> stop on my box (already executed 100+ times) and I couldn’t replicate the
> issue:
>
> Any ideias?
>
> > On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > I'll take the first one first
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez
> <ra...@yahoo.com.invalid>
> > wrote:
> >
> >> Thank you JL,
> >>
> >> At least this test is failing:
> >> org.apache.openejb.config.rules.CheckMissingClassTest
> >>
> >> And this one seems to fail randomly.
> >> org.apache.openejb.resource.AutoConnectionTrackerTest
> >>
> >> Cheers,
> >> Roberto
> >>
> >>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> >> wrote:
> >>>
> >>> I have merged a couple of PR and I'm running a full build locally. I'll
> >>> work on fixes any issues if I find some but I'll report first here
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> >> <ra...@yahoo.com.invalid>
> >>> wrote:
> >>>
> >>>> Hey Jon,
> >>>>
> >>>> The following commit:
> >>>>
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>> <
> >>>>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>>>
> >>>>
> >>>> Is failing the test:
> >>>> org.apache.openejb.config.rules.CheckMissingClassTest
> >>>>
> >>>> Can you help?
> >>>>
> >>>> Cheers,
> >>>> Roberto
> >>>>
> >>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> >>>>>
> >>>>> Hi Cesar,
> >>>>>
> >>>>>> This is a valuable piece of information.
> >>>>> That's what I thohght, too when I read the information on IRC ...
> >>>>> Thanks that you want to preserve it on the website.
> >>>>>
> >>>>> The JIRA task is now assigned to you.
> >>>>>
> >>>>> Frankie
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from:
> >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>
> >>>>
> >>
> >>
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

It seems the build just randomly fails with this test:
AutoConnectionTrackerTest.test

[ERROR] Failures: 
[ERROR]   AutoConnectionTrackerTest.test:198 expected:<1> but was:<0>

Sometimes it passes, sometimes it fails. I suspect it may be related with some timing issues / box speed of the build bot. I’m running the test non stop on my box (already executed 100+ times) and I couldn’t replicate the issue:

Any ideias?

> On 12 Dec 2018, at 16:25, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> I'll take the first one first
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
> 
>> Thank you JL,
>> 
>> At least this test is failing:
>> org.apache.openejb.config.rules.CheckMissingClassTest
>> 
>> And this one seems to fail randomly.
>> org.apache.openejb.resource.AutoConnectionTrackerTest
>> 
>> Cheers,
>> Roberto
>> 
>>> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <jl...@tomitribe.com>
>> wrote:
>>> 
>>> I have merged a couple of PR and I'm running a full build locally. I'll
>>> work on fixes any issues if I find some but I'll report first here
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>> 
>>> 
>>> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
>> <ra...@yahoo.com.invalid>
>>> wrote:
>>> 
>>>> Hey Jon,
>>>> 
>>>> The following commit:
>>>> 
>>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>> <
>>>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>>>> 
>>>> 
>>>> Is failing the test:
>>>> org.apache.openejb.config.rules.CheckMissingClassTest
>>>> 
>>>> Can you help?
>>>> 
>>>> Cheers,
>>>> Roberto
>>>> 
>>>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
>>>>> 
>>>>> Hi Cesar,
>>>>> 
>>>>>> This is a valuable piece of information.
>>>>> That's what I thohght, too when I read the information on IRC ...
>>>>> Thanks that you want to preserve it on the website.
>>>>> 
>>>>> The JIRA task is now assigned to you.
>>>>> 
>>>>> Frankie
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Sent from:
>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>> 
>>>> 
>> 
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I'll take the first one first

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 12, 2018 at 5:21 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Thank you JL,
>
> At least this test is failing:
> org.apache.openejb.config.rules.CheckMissingClassTest
>
> And this one seems to fail randomly.
> org.apache.openejb.resource.AutoConnectionTrackerTest
>
> Cheers,
> Roberto
>
> > On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > I have merged a couple of PR and I'm running a full build locally. I'll
> > work on fixes any issues if I find some but I'll report first here
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez
> <ra...@yahoo.com.invalid>
> > wrote:
> >
> >> Hey Jon,
> >>
> >> The following commit:
> >>
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >> <
> >>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >>>
> >>
> >> Is failing the test:
> >> org.apache.openejb.config.rules.CheckMissingClassTest
> >>
> >> Can you help?
> >>
> >> Cheers,
> >> Roberto
> >>
> >>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> >>>
> >>> Hi Cesar,
> >>>
> >>>> This is a valuable piece of information.
> >>> That's what I thohght, too when I read the information on IRC ...
> >>> Thanks that you want to preserve it on the website.
> >>>
> >>> The JIRA task is now assigned to you.
> >>>
> >>> Frankie
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>
> >>
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Thank you JL,

At least this test is failing:
org.apache.openejb.config.rules.CheckMissingClassTest

And this one seems to fail randomly.
org.apache.openejb.resource.AutoConnectionTrackerTest

Cheers,
Roberto

> On 12 Dec 2018, at 16:18, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> I have merged a couple of PR and I'm running a full build locally. I'll
> work on fixes any issues if I find some but I'll report first here
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez <ra...@yahoo.com.invalid>
> wrote:
> 
>> Hey Jon,
>> 
>> The following commit:
>> 
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>> <
>> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
>>> 
>> 
>> Is failing the test:
>> org.apache.openejb.config.rules.CheckMissingClassTest
>> 
>> Can you help?
>> 
>> Cheers,
>> Roberto
>> 
>>> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
>>> 
>>> Hi Cesar,
>>> 
>>>> This is a valuable piece of information.
>>> That's what I thohght, too when I read the information on IRC ...
>>> Thanks that you want to preserve it on the website.
>>> 
>>> The JIRA task is now assigned to you.
>>> 
>>> Frankie
>>> 
>>> 
>>> 
>>> --
>>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> 
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I have merged a couple of PR and I'm running a full build locally. I'll
work on fixes any issues if I find some but I'll report first here
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 12, 2018 at 3:33 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Hey Jon,
>
> The following commit:
>
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> <
> https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9
> >
>
> Is failing the test:
> org.apache.openejb.config.rules.CheckMissingClassTest
>
> Can you help?
>
> Cheers,
> Roberto
>
> > On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> >
> > Hi Cesar,
> >
> >> This is a valuable piece of information.
> > That's what I thohght, too when I read the information on IRC ...
> > Thanks that you want to preserve it on the website.
> >
> > The JIRA task is now assigned to you.
> >
> > Frankie
> >
> >
> >
> > --
> > Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Hey Jon,

The following commit:
https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9 <https://github.com/apache/tomee/commit/4d535f969e9769f0403fddd100b085a0d1de15a9>

Is failing the test:
org.apache.openejb.config.rules.CheckMissingClassTest

Can you help?

Cheers,
Roberto

> On 12 Dec 2018, at 04:41, Frankie <ka...@gmx.de> wrote:
> 
> Hi Cesar,
> 
>> This is a valuable piece of information.
> That's what I thohght, too when I read the information on IRC ... 
> Thanks that you want to preserve it on the website.
> 
> The JIRA task is now assigned to you. 
> 
> Frankie
> 
> 
> 
> --
> Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Frankie <ka...@gmx.de>]

Hi Cesar,

> This is a valuable piece of information.
That's what I thohght, too when I read the information on IRC ... 
Thanks that you want to preserve it on the website.

The JIRA task is now assigned to you. 

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[César Hernández Mendoza <ce...@gmail.com>]

Thanks, Jean-Louis and Roberto,

This is a valuable piece of information.
I'm planning to open a PR to add this information to the
http://tomee.apache.org/community/ section under an "Infra" (or maybe
"Continous Integration") category. (Suggestion?)

I created https://issues.apache.org/jira/browse/TOMEE-2356  and I would
like to request to a JIRA admin to assign the ticket to me so I can start
working on this ticket.



El mar., 11 dic. 2018 a las 4:35, Roberto Cortez
(<ra...@yahoo.com.invalid>) escribió:

> To give some more detail:
>
>  - Connect to irc.freenode.net <http://irc.freenode.net/> (I use an app
> called LimeChat for Mac)
>  - Join #openejb channel
>  - There is a bot there called tomee-bot that accepts instructions.
>  - Message the bot privately with for instance “commands” to see what is
> available.
>  - Use the command "force build tomee-trunk-ubuntu-jvm8” to force a build
> of the current master.
>
> Cheers,
> Roberto
>
> > On 11 Dec 2018, at 07:01, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > Yes you can do that with IRC
> >
> > Le mar. 11 déc. 2018 à 04:27, César Hernández Mendoza <
> cesarguate@gmail.com>
> > a écrit :
> >
> >> Hi,
> >> Is there a way to trigger a Buildbot just against current master and not
> >> related with a specific PR?
> >> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
> >>
> >>
> >> El lun., 10 dic. 2018 a las 8:25, Jonathan Gallimore (<
> >> jonathan.gallimore@gmail.com>) escribió:
> >>
> >>> Pulling and building it now :). Thanks Dani!
> >>>
> >>> On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com>
> >> wrote:
> >>>
> >>>> Nice!
> >>>>
> >>>> PR opened: https://github.com/apache/tomee/pull/267
> >>>>
> >>>> Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> escreveu:
> >>>>
> >>>>> Awesome, SNAPSHOT is good. Send a PR :)
> >>>>>
> >>>>>
> >>>>> On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi folks,
> >>>>>>
> >>>>>> The fix for testes below is already on bval master branch.
> >>>>>> Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> >>>>>>
> >>>>>> DuplicateConfigurationTest
> >>>>>> XMLConfigurationTest
> >>>>>> XMLConfiguredConstraintValidatorTest
> >>>>>>
> >>>>>> Can we use SNAPSHOT for now or wait for the next bval release?
> >>>>>>
> >>>>>>
> >>>>>> Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid> escreveu:
> >>>>>>
> >>>>>>> Agree on both.
> >>>>>>>
> >>>>>>>> On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> >>>>> jlmonteiro@tomitribe.com
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> I only fixed the 2 imports for checkstyle
> >>>>>>>>
> >>>>>>>> I don't think from an end user perspective the information is
> >>> very
> >>>>>>>> important in the changelog so did not created any ticket.
> >>>>>>>>
> >>>>>>>> If everyone thinks this is important for the user. I'm happy to
> >>>>> create
> >>>>>>> one.
> >>>>>>>>
> >>>>>>>> In that area I don't think it makes sense either to create a
> >> bug
> >>> in
> >>>>>> Jira
> >>>>>>>> for a non released feature. So if there is a new example and
> >> you
> >>>>> find a
> >>>>>>>> bug. Go ahead and fix it. No need to create a new ticket. Use
> >> the
> >>>> one
> >>>>>>>> mentioning we are creating a new example.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de>
> >> a
> >>>>>> écrit :
> >>>>>>>>
> >>>>>>>>> Overlooked that, sorry.
> >>>>>>>>> I intended to concentrate on the documentation for
> >> contribution
> >>>>>>> workflow,
> >>>>>>>>> that's why I asked.
> >>>>>>>>> So no problem if Jean-Louis picks it up.
> >>>>>>>>> And: what about a JIRA ticket for that ... ? ;-)
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Sent from:
> >>>>>>>>>
> >>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Daniel "soro" Cunha
> >>>>>> https://twitter.com/dvlc_
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Daniel "soro" Cunha
> >>>> https://twitter.com/dvlc_
> >>>>
> >>>
> >>
> >>
> >> --
> >> Atentamente:
> >> César Hernández Mendoza.
> >>
>
>

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

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

Good to know.

Thanks Roberto! :D

Em ter, 11 de dez de 2018 às 07:35, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> To give some more detail:
>
>  - Connect to irc.freenode.net <http://irc.freenode.net/> (I use an app
> called LimeChat for Mac)
>  - Join #openejb channel
>  - There is a bot there called tomee-bot that accepts instructions.
>  - Message the bot privately with for instance “commands” to see what is
> available.
>  - Use the command "force build tomee-trunk-ubuntu-jvm8” to force a build
> of the current master.
>
> Cheers,
> Roberto
>
> > On 11 Dec 2018, at 07:01, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > Yes you can do that with IRC
> >
> > Le mar. 11 déc. 2018 à 04:27, César Hernández Mendoza <
> cesarguate@gmail.com>
> > a écrit :
> >
> >> Hi,
> >> Is there a way to trigger a Buildbot just against current master and not
> >> related with a specific PR?
> >> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
> >>
> >>
> >> El lun., 10 dic. 2018 a las 8:25, Jonathan Gallimore (<
> >> jonathan.gallimore@gmail.com>) escribió:
> >>
> >>> Pulling and building it now :). Thanks Dani!
> >>>
> >>> On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com>
> >> wrote:
> >>>
> >>>> Nice!
> >>>>
> >>>> PR opened: https://github.com/apache/tomee/pull/267
> >>>>
> >>>> Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> escreveu:
> >>>>
> >>>>> Awesome, SNAPSHOT is good. Send a PR :)
> >>>>>
> >>>>>
> >>>>> On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi folks,
> >>>>>>
> >>>>>> The fix for testes below is already on bval master branch.
> >>>>>> Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> >>>>>>
> >>>>>> DuplicateConfigurationTest
> >>>>>> XMLConfigurationTest
> >>>>>> XMLConfiguredConstraintValidatorTest
> >>>>>>
> >>>>>> Can we use SNAPSHOT for now or wait for the next bval release?
> >>>>>>
> >>>>>>
> >>>>>> Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> >>>>>> <ra...@yahoo.com.invalid> escreveu:
> >>>>>>
> >>>>>>> Agree on both.
> >>>>>>>
> >>>>>>>> On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> >>>>> jlmonteiro@tomitribe.com
> >>>>>>>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> I only fixed the 2 imports for checkstyle
> >>>>>>>>
> >>>>>>>> I don't think from an end user perspective the information is
> >>> very
> >>>>>>>> important in the changelog so did not created any ticket.
> >>>>>>>>
> >>>>>>>> If everyone thinks this is important for the user. I'm happy to
> >>>>> create
> >>>>>>> one.
> >>>>>>>>
> >>>>>>>> In that area I don't think it makes sense either to create a
> >> bug
> >>> in
> >>>>>> Jira
> >>>>>>>> for a non released feature. So if there is a new example and
> >> you
> >>>>> find a
> >>>>>>>> bug. Go ahead and fix it. No need to create a new ticket. Use
> >> the
> >>>> one
> >>>>>>>> mentioning we are creating a new example.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de>
> >> a
> >>>>>> écrit :
> >>>>>>>>
> >>>>>>>>> Overlooked that, sorry.
> >>>>>>>>> I intended to concentrate on the documentation for
> >> contribution
> >>>>>>> workflow,
> >>>>>>>>> that's why I asked.
> >>>>>>>>> So no problem if Jean-Louis picks it up.
> >>>>>>>>> And: what about a JIRA ticket for that ... ? ;-)
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Sent from:
> >>>>>>>>>
> >>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Daniel "soro" Cunha
> >>>>>> https://twitter.com/dvlc_
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Daniel "soro" Cunha
> >>>> https://twitter.com/dvlc_
> >>>>
> >>>
> >>
> >>
> >> --
> >> Atentamente:
> >> César Hernández Mendoza.
> >>
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

To give some more detail:

 - Connect to irc.freenode.net <http://irc.freenode.net/> (I use an app called LimeChat for Mac)
 - Join #openejb channel
 - There is a bot there called tomee-bot that accepts instructions.
 - Message the bot privately with for instance “commands” to see what is available.
 - Use the command "force build tomee-trunk-ubuntu-jvm8” to force a build of the current master.

Cheers,
Roberto

> On 11 Dec 2018, at 07:01, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> Yes you can do that with IRC
> 
> Le mar. 11 déc. 2018 à 04:27, César Hernández Mendoza <ce...@gmail.com>
> a écrit :
> 
>> Hi,
>> Is there a way to trigger a Buildbot just against current master and not
>> related with a specific PR?
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
>> 
>> 
>> El lun., 10 dic. 2018 a las 8:25, Jonathan Gallimore (<
>> jonathan.gallimore@gmail.com>) escribió:
>> 
>>> Pulling and building it now :). Thanks Dani!
>>> 
>>> On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com>
>> wrote:
>>> 
>>>> Nice!
>>>> 
>>>> PR opened: https://github.com/apache/tomee/pull/267
>>>> 
>>>> Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
>>>> jonathan.gallimore@gmail.com> escreveu:
>>>> 
>>>>> Awesome, SNAPSHOT is good. Send a PR :)
>>>>> 
>>>>> 
>>>>> On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
>>>>> wrote:
>>>>> 
>>>>>> Hi folks,
>>>>>> 
>>>>>> The fix for testes below is already on bval master branch.
>>>>>> Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
>>>>>> 
>>>>>> DuplicateConfigurationTest
>>>>>> XMLConfigurationTest
>>>>>> XMLConfiguredConstraintValidatorTest
>>>>>> 
>>>>>> Can we use SNAPSHOT for now or wait for the next bval release?
>>>>>> 
>>>>>> 
>>>>>> Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
>>>>>> <ra...@yahoo.com.invalid> escreveu:
>>>>>> 
>>>>>>> Agree on both.
>>>>>>> 
>>>>>>>> On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
>>>>> jlmonteiro@tomitribe.com
>>>>>>> 
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> I only fixed the 2 imports for checkstyle
>>>>>>>> 
>>>>>>>> I don't think from an end user perspective the information is
>>> very
>>>>>>>> important in the changelog so did not created any ticket.
>>>>>>>> 
>>>>>>>> If everyone thinks this is important for the user. I'm happy to
>>>>> create
>>>>>>> one.
>>>>>>>> 
>>>>>>>> In that area I don't think it makes sense either to create a
>> bug
>>> in
>>>>>> Jira
>>>>>>>> for a non released feature. So if there is a new example and
>> you
>>>>> find a
>>>>>>>> bug. Go ahead and fix it. No need to create a new ticket. Use
>> the
>>>> one
>>>>>>>> mentioning we are creating a new example.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de>
>> a
>>>>>> écrit :
>>>>>>>> 
>>>>>>>>> Overlooked that, sorry.
>>>>>>>>> I intended to concentrate on the documentation for
>> contribution
>>>>>>> workflow,
>>>>>>>>> that's why I asked.
>>>>>>>>> So no problem if Jean-Louis picks it up.
>>>>>>>>> And: what about a JIRA ticket for that ... ? ;-)
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> --
>>>>>>>>> Sent from:
>>>>>>>>> 
>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Daniel "soro" Cunha
>>>>>> https://twitter.com/dvlc_
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> Daniel "soro" Cunha
>>>> https://twitter.com/dvlc_
>>>> 
>>> 
>> 
>> 
>> --
>> Atentamente:
>> César Hernández Mendoza.
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Yes you can do that with IRC

Le mar. 11 déc. 2018 à 04:27, César Hernández Mendoza <ce...@gmail.com>
a écrit :

> Hi,
> Is there a way to trigger a Buildbot just against current master and not
> related with a specific PR?
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8
>
>
> El lun., 10 dic. 2018 a las 8:25, Jonathan Gallimore (<
> jonathan.gallimore@gmail.com>) escribió:
>
> > Pulling and building it now :). Thanks Dani!
> >
> > On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com>
> wrote:
> >
> > > Nice!
> > >
> > > PR opened: https://github.com/apache/tomee/pull/267
> > >
> > > Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> escreveu:
> > >
> > > > Awesome, SNAPSHOT is good. Send a PR :)
> > > >
> > > >
> > > > On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > The fix for testes below is already on bval master branch.
> > > > > Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> > > > >
> > > > > DuplicateConfigurationTest
> > > > > XMLConfigurationTest
> > > > > XMLConfiguredConstraintValidatorTest
> > > > >
> > > > > Can we use SNAPSHOT for now or wait for the next bval release?
> > > > >
> > > > >
> > > > > Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> > > > > <ra...@yahoo.com.invalid> escreveu:
> > > > >
> > > > > > Agree on both.
> > > > > >
> > > > > > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> > > > jlmonteiro@tomitribe.com
> > > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > I only fixed the 2 imports for checkstyle
> > > > > > >
> > > > > > > I don't think from an end user perspective the information is
> > very
> > > > > > > important in the changelog so did not created any ticket.
> > > > > > >
> > > > > > > If everyone thinks this is important for the user. I'm happy to
> > > > create
> > > > > > one.
> > > > > > >
> > > > > > > In that area I don't think it makes sense either to create a
> bug
> > in
> > > > > Jira
> > > > > > > for a non released feature. So if there is a new example and
> you
> > > > find a
> > > > > > > bug. Go ahead and fix it. No need to create a new ticket. Use
> the
> > > one
> > > > > > > mentioning we are creating a new example.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de>
> a
> > > > > écrit :
> > > > > > >
> > > > > > >> Overlooked that, sorry.
> > > > > > >> I intended to concentrate on the documentation for
> contribution
> > > > > > workflow,
> > > > > > >> that's why I asked.
> > > > > > >> So no problem if Jean-Louis picks it up.
> > > > > > >> And: what about a JIRA ticket for that ... ? ;-)
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> Sent from:
> > > > > > >>
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Daniel "soro" Cunha
> > > > > https://twitter.com/dvlc_
> > > > >
> > > >
> > >
> > >
> > > --
> > > Daniel "soro" Cunha
> > > https://twitter.com/dvlc_
> > >
> >
>
>
> --
> Atentamente:
> César Hernández Mendoza.
>

Re: Stabilize TomEE Build

[César Hernández Mendoza <ce...@gmail.com>]

Hi,
Is there a way to trigger a Buildbot just against current master and not
related with a specific PR?
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8


El lun., 10 dic. 2018 a las 8:25, Jonathan Gallimore (<
jonathan.gallimore@gmail.com>) escribió:

> Pulling and building it now :). Thanks Dani!
>
> On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com> wrote:
>
> > Nice!
> >
> > PR opened: https://github.com/apache/tomee/pull/267
> >
> > Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> escreveu:
> >
> > > Awesome, SNAPSHOT is good. Send a PR :)
> > >
> > >
> > > On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> > > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > The fix for testes below is already on bval master branch.
> > > > Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> > > >
> > > > DuplicateConfigurationTest
> > > > XMLConfigurationTest
> > > > XMLConfiguredConstraintValidatorTest
> > > >
> > > > Can we use SNAPSHOT for now or wait for the next bval release?
> > > >
> > > >
> > > > Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> > > > <ra...@yahoo.com.invalid> escreveu:
> > > >
> > > > > Agree on both.
> > > > >
> > > > > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> > > jlmonteiro@tomitribe.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > I only fixed the 2 imports for checkstyle
> > > > > >
> > > > > > I don't think from an end user perspective the information is
> very
> > > > > > important in the changelog so did not created any ticket.
> > > > > >
> > > > > > If everyone thinks this is important for the user. I'm happy to
> > > create
> > > > > one.
> > > > > >
> > > > > > In that area I don't think it makes sense either to create a bug
> in
> > > > Jira
> > > > > > for a non released feature. So if there is a new example and you
> > > find a
> > > > > > bug. Go ahead and fix it. No need to create a new ticket. Use the
> > one
> > > > > > mentioning we are creating a new example.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a
> > > > écrit :
> > > > > >
> > > > > >> Overlooked that, sorry.
> > > > > >> I intended to concentrate on the documentation for contribution
> > > > > workflow,
> > > > > >> that's why I asked.
> > > > > >> So no problem if Jean-Louis picks it up.
> > > > > >> And: what about a JIRA ticket for that ... ? ;-)
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Sent from:
> > > > > >>
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > > >>
> > > > >
> > > > >
> > > >
> > > > --
> > > > Daniel "soro" Cunha
> > > > https://twitter.com/dvlc_
> > > >
> > >
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
> >
>


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

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Pulling and building it now :). Thanks Dani!

On Mon, Dec 10, 2018 at 2:23 PM Daniel Cunha <da...@gmail.com> wrote:

> Nice!
>
> PR opened: https://github.com/apache/tomee/pull/267
>
> Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> escreveu:
>
> > Awesome, SNAPSHOT is good. Send a PR :)
> >
> >
> > On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> > wrote:
> >
> > > Hi folks,
> > >
> > > The fix for testes below is already on bval master branch.
> > > Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> > >
> > > DuplicateConfigurationTest
> > > XMLConfigurationTest
> > > XMLConfiguredConstraintValidatorTest
> > >
> > > Can we use SNAPSHOT for now or wait for the next bval release?
> > >
> > >
> > > Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> > > <ra...@yahoo.com.invalid> escreveu:
> > >
> > > > Agree on both.
> > > >
> > > > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com
> > > >
> > > > wrote:
> > > > >
> > > > > I only fixed the 2 imports for checkstyle
> > > > >
> > > > > I don't think from an end user perspective the information is very
> > > > > important in the changelog so did not created any ticket.
> > > > >
> > > > > If everyone thinks this is important for the user. I'm happy to
> > create
> > > > one.
> > > > >
> > > > > In that area I don't think it makes sense either to create a bug in
> > > Jira
> > > > > for a non released feature. So if there is a new example and you
> > find a
> > > > > bug. Go ahead and fix it. No need to create a new ticket. Use the
> one
> > > > > mentioning we are creating a new example.
> > > > >
> > > > >
> > > > >
> > > > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a
> > > écrit :
> > > > >
> > > > >> Overlooked that, sorry.
> > > > >> I intended to concentrate on the documentation for contribution
> > > > workflow,
> > > > >> that's why I asked.
> > > > >> So no problem if Jean-Louis picks it up.
> > > > >> And: what about a JIRA ticket for that ... ? ;-)
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Sent from:
> > > > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > >>
> > > >
> > > >
> > >
> > > --
> > > Daniel "soro" Cunha
> > > https://twitter.com/dvlc_
> > >
> >
>
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Nice!

PR opened: https://github.com/apache/tomee/pull/267

Em seg, 10 de dez de 2018 às 11:01, Jonathan Gallimore <
jonathan.gallimore@gmail.com> escreveu:

> Awesome, SNAPSHOT is good. Send a PR :)
>
>
> On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org>
> wrote:
>
> > Hi folks,
> >
> > The fix for testes below is already on bval master branch.
> > Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
> >
> > DuplicateConfigurationTest
> > XMLConfigurationTest
> > XMLConfiguredConstraintValidatorTest
> >
> > Can we use SNAPSHOT for now or wait for the next bval release?
> >
> >
> > Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> > <ra...@yahoo.com.invalid> escreveu:
> >
> > > Agree on both.
> > >
> > > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com
> > >
> > > wrote:
> > > >
> > > > I only fixed the 2 imports for checkstyle
> > > >
> > > > I don't think from an end user perspective the information is very
> > > > important in the changelog so did not created any ticket.
> > > >
> > > > If everyone thinks this is important for the user. I'm happy to
> create
> > > one.
> > > >
> > > > In that area I don't think it makes sense either to create a bug in
> > Jira
> > > > for a non released feature. So if there is a new example and you
> find a
> > > > bug. Go ahead and fix it. No need to create a new ticket. Use the one
> > > > mentioning we are creating a new example.
> > > >
> > > >
> > > >
> > > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a
> > écrit :
> > > >
> > > >> Overlooked that, sorry.
> > > >> I intended to concentrate on the documentation for contribution
> > > workflow,
> > > >> that's why I asked.
> > > >> So no problem if Jean-Louis picks it up.
> > > >> And: what about a JIRA ticket for that ... ? ;-)
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Sent from:
> > > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > >>
> > >
> > >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Awesome, SNAPSHOT is good. Send a PR :)


On Mon, Dec 10, 2018 at 1:45 PM Daniel Cunha <da...@apache.org> wrote:

> Hi folks,
>
> The fix for testes below is already on bval master branch.
> Just update bval to 2.0.1-SNAPSHOT and it will be fixed.
>
> DuplicateConfigurationTest
> XMLConfigurationTest
> XMLConfiguredConstraintValidatorTest
>
> Can we use SNAPSHOT for now or wait for the next bval release?
>
>
> Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
> <ra...@yahoo.com.invalid> escreveu:
>
> > Agree on both.
> >
> > > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <jlmonteiro@tomitribe.com
> >
> > wrote:
> > >
> > > I only fixed the 2 imports for checkstyle
> > >
> > > I don't think from an end user perspective the information is very
> > > important in the changelog so did not created any ticket.
> > >
> > > If everyone thinks this is important for the user. I'm happy to create
> > one.
> > >
> > > In that area I don't think it makes sense either to create a bug in
> Jira
> > > for a non released feature. So if there is a new example and you find a
> > > bug. Go ahead and fix it. No need to create a new ticket. Use the one
> > > mentioning we are creating a new example.
> > >
> > >
> > >
> > > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a
> écrit :
> > >
> > >> Overlooked that, sorry.
> > >> I intended to concentrate on the documentation for contribution
> > workflow,
> > >> that's why I asked.
> > >> So no problem if Jean-Louis picks it up.
> > >> And: what about a JIRA ticket for that ... ? ;-)
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> Sent from:
> > >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>
> >
> >
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@apache.org>]

Hi folks,

The fix for testes below is already on bval master branch.
Just update bval to 2.0.1-SNAPSHOT and it will be fixed.

DuplicateConfigurationTest
XMLConfigurationTest
XMLConfiguredConstraintValidatorTest

Can we use SNAPSHOT for now or wait for the next bval release?


Em dom, 9 de dez de 2018 às 20:23, Roberto Cortez
<ra...@yahoo.com.invalid> escreveu:

> Agree on both.
>
> > On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > I only fixed the 2 imports for checkstyle
> >
> > I don't think from an end user perspective the information is very
> > important in the changelog so did not created any ticket.
> >
> > If everyone thinks this is important for the user. I'm happy to create
> one.
> >
> > In that area I don't think it makes sense either to create a bug in Jira
> > for a non released feature. So if there is a new example and you find a
> > bug. Go ahead and fix it. No need to create a new ticket. Use the one
> > mentioning we are creating a new example.
> >
> >
> >
> > Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a écrit :
> >
> >> Overlooked that, sorry.
> >> I intended to concentrate on the documentation for contribution
> workflow,
> >> that's why I asked.
> >> So no problem if Jean-Louis picks it up.
> >> And: what about a JIRA ticket for that ... ? ;-)
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>
>
>

-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Agree on both.

> On 9 Dec 2018, at 07:52, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> I only fixed the 2 imports for checkstyle
> 
> I don't think from an end user perspective the information is very
> important in the changelog so did not created any ticket.
> 
> If everyone thinks this is important for the user. I'm happy to create one.
> 
> In that area I don't think it makes sense either to create a bug in Jira
> for a non released feature. So if there is a new example and you find a
> bug. Go ahead and fix it. No need to create a new ticket. Use the one
> mentioning we are creating a new example.
> 
> 
> 
> Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a écrit :
> 
>> Overlooked that, sorry.
>> I intended to concentrate on the documentation for contribution workflow,
>> that's why I asked.
>> So no problem if Jean-Louis picks it up.
>> And: what about a JIRA ticket for that ... ? ;-)
>> 
>> 
>> 
>> 
>> 
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I only fixed the 2 imports for checkstyle

I don't think from an end user perspective the information is very
important in the changelog so did not created any ticket.

If everyone thinks this is important for the user. I'm happy to create one.

In that area I don't think it makes sense either to create a bug in Jira
for a non released feature. So if there is a new example and you find a
bug. Go ahead and fix it. No need to create a new ticket. Use the one
mentioning we are creating a new example.



Le sam. 8 déc. 2018 à 19:30, Frankie <ka...@gmx.de> a écrit :

> Overlooked that, sorry.
> I intended to concentrate on the documentation for contribution workflow,
> that's why I asked.
> So no problem if Jean-Louis picks it up.
> And: what about a JIRA ticket for that ... ? ;-)
>
>
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Re: Stabilize TomEE Build

[Frankie <ka...@gmx.de>]

Overlooked that, sorry.
I intended to concentrate on the documentation for contribution workflow,
that's why I asked.
So no problem if Jean-Louis picks it up.
And: what about a JIRA ticket for that ... ? ;-)





--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Actually I just cherry-picked this for both branches - seems to have merged
cleanly, so building and pushing.

Jon

On Thu, Dec 6, 2018 at 8:41 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> Hi Dani
>
> Do you want to have a go at backporting my changes to your PR? The SHAs
> you need are these ones: https://github.com/apache/tomee/pull/258/commits
>
> Jon
>
>
>
> On Thu, Dec 6, 2018 at 8:03 PM Daniel Cunha <da...@gmail.com> wrote:
>
>> Hi Jon,
>>
>> Thank you for your fix, it also need to be applied on branch 7.0.1 and on
>> 7.1.x I need update my PR with your changes [
>> https://github.com/apache/tomee/pull/236]
>>
>> Em qui, 6 de dez de 2018 às 13:58, Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> escreveu:
>>
>> > Filed a ticket for bval failures and will work on that next.
>> > https://issues.apache.org/jira/browse/TOMEE-2327
>> >
>> > Jon
>> >
>> > On Thu, Dec 6, 2018 at 3:31 PM Jonathan Gallimore <
>> > jonathan.gallimore@gmail.com> wrote:
>> >
>> > > Hopefully this will do the trick:
>> > https://github.com/apache/tomee/pull/258.
>> > > Full build currently running here.
>> > >
>> > > Jon
>> > >
>> > > On Thu, Dec 6, 2018 at 10:46 AM Jonathan Gallimore <
>> > > jonathan.gallimore@gmail.com> wrote:
>> > >
>> > >> I believe this is the root cause of these test failures:
>> > >>
>> > >> WARNING: Failed to invoke bootstrap:
>> > >> javax/persistence/spi/PersistenceUnitInfo
>> > >>
>> > >> Exception in thread "main" java.lang.NoClassDefFoundError:
>> > >> org/apache/commons/cli/ParseException
>> > >>
>> > >> at java.lang.Class.getDeclaredConstructors0(Native Method)
>> > >>
>> > >> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
>> > >>
>> > >> at java.lang.Class.getConstructor0(Class.java:3075)
>> > >>
>> > >> at java.lang.Class.getConstructor(Class.java:1825)
>> > >>
>> > >> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)
>> > >>
>> > >> Caused by: java.lang.ClassNotFoundException:
>> > >> org.apache.commons.cli.ParseException
>> > >>
>> > >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>> > >>
>> > >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>> > >>
>> > >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
>> > >>
>> > >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>> > >>
>> > >> ... 5 more
>> > >>
>> > >>
>> > >> and its been introduced in this PR:
>> > >> https://github.com/apache/tomee/pull/176 (I pulled the 8.0.0-M1 tag,
>> > >> where this was working, and applied this PR to it in my working copy,
>> > and
>> > >> it now fails).
>> > >>
>> > >>
>> > >> Digging in to see if I can fix it. Dani, any thoughts you have are
>> > >> appreciated.
>> > >>
>> > >>
>> > >> Jon
>> > >>
>> > >> On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
>> > >> jonathan.gallimore@gmail.com> wrote:
>> > >>
>> > >>> Looks like we have some new failures in the itest module:
>> > >>>
>> > >>> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot
>> lookup
>> > >>> '/CalculatorBeanR...
>> > >>>
>> > >>> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
>> > >>> lookup '/Calculator...
>> > >>>
>> > >>> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
>> > >>> '/CalculatorBeanRem...
>> > >>>
>> > >>> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
>> > >>> '/CalculatorBeanRemote'.
>> > >>>
>> > >>> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
>> > >>> lookup '/CalculatorB...
>> > >>>
>> > >>> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
>> > >>> Cannot lookup '/Cal...
>> > >>>
>> > >>>
>> > >>> I'll take a look. JIRA is:
>> > >>> https://issues.apache.org/jira/browse/TOMEE-2322.
>> > >>>
>> > >>>
>> > >>> Cheers
>> > >>>
>> > >>>
>> > >>> Jon
>> > >>>
>> > >>> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
>> > >>> jlmonteiro@tomitribe.com> wrote:
>> > >>>
>> > >>>> Oups, then I believe I need to apologize guys.
>> > >>>>
>> > >>>> I wanted to at least fix the 2 imports so we can get a build with
>> some
>> > >>>> results.
>> > >>>>
>> > >>>> --
>> > >>>> Jean-Louis Monteiro
>> > >>>> http://twitter.com/jlouismonteiro
>> > >>>> http://www.tomitribe.com
>> > >>>>
>> > >>>>
>> > >>>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
>> > >>>> jonathan.gallimore@gmail.com> wrote:
>> > >>>>
>> > >>>> > I appreciate that. Can I ask you be mindful that Frankie posted,
>> > and I
>> > >>>> > asked him if he wanted to have a go in my reply? We should give
>> him
>> > >>>> some
>> > >>>> > time to respond, before someone else picks it up. If Frankie
>> worked
>> > on
>> > >>>> > fixing those, and then found someone else had done the same work
>> > >>>> without a
>> > >>>> > JIRA, I suspect that would be pretty frustrating.
>> > >>>> >
>> > >>>> > Jon
>> > >>>> >
>> > >>>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
>> > >>>> > jlmonteiro@tomitribe.com> wrote:
>> > >>>> >
>> > >>>> > > I can help fixing some of those
>> > >>>> > >
>> > >>>> > > --
>> > >>>> > > Jean-Louis Monteiro
>> > >>>> > > http://twitter.com/jlouismonteiro
>> > >>>> > > http://www.tomitribe.com
>> > >>>> > >
>> > >>>> > >
>> > >>>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
>> > >>>> > > jonathan.gallimore@gmail.com> wrote:
>> > >>>> > >
>> > >>>> > > > Hi,
>> > >>>> > > >
>> > >>>> > > > Great question. The commands are:
>> > >>>> > > >
>> > >>>> > > > Checkstyle: mvn -Pstyle checkstyle:check
>> > >>>> > > > PMD: mvn -Pstyle pmd:check
>> > >>>> > > >
>> > >>>> > > > These are relatively quick to run - about a minute or so.
>> > >>>> > > >
>> > >>>> > > > Looks like we have 2 checkstyle violations in the build at
>> the
>> > >>>> moment:
>> > >>>> > > >
>> > >>>> > > >
>> > >>>> > >
>> > >>>> >
>> > >>>>
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > >>>> > > >
>> > >>>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
>> > >>>> > > >
>> > >>>> > > >
>> > >>>> > >
>> > >>>> >
>> > >>>>
>> >
>> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
>> > >>>> > > > ruleset.
>> > >>>> > > > [ERROR]
>> > src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
>> > >>>> > > > (imports) UnusedImports: Unused import -
>> > >>>> > > > org.apache.openejb.loader.SystemClassPath.
>> > >>>> > > > [ERROR]
>> > src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
>> > >>>> > > > (imports) UnusedImports: Unused import -
>> > >>>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
>> > >>>> > > >
>> > >>>> > > > Frankie, would you like to have a go at resolving these?
>> > >>>> > > >
>> > >>>> > > > Cheers
>> > >>>> > > >
>> > >>>> > > > Jon
>> > >>>> > > >
>> > >>>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <
>> kamin.feuer.2000@gmx.de
>> > >
>> > >>>> > wrote:
>> > >>>> > > >
>> > >>>> > > > > What can I do to already detect such problems when I work
>> on
>> > the
>> > >>>> > code?
>> > >>>> > > > > What is the difference on the build system? (additional
>> > >>>> checkstyle
>> > >>>> > > rules
>> > >>>> > > > > ...?
>> > >>>> > > > >
>> > >>>> > > > > Frankie
>> > >>>> > > > >
>> > >>>> > > > >
>> > >>>> > > > >
>> > >>>> > > > > --
>> > >>>> > > > > Sent from:
>> > >>>> > > > >
>> > >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> > >>>> > > > >
>> > >>>> > > >
>> > >>>> > >
>> > >>>> >
>> > >>>>
>> > >>>
>> >
>>
>>
>> --
>> Daniel "soro" Cunha
>> https://twitter.com/dvlc_
>>
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Hi Dani

Do you want to have a go at backporting my changes to your PR? The SHAs you
need are these ones: https://github.com/apache/tomee/pull/258/commits

Jon



On Thu, Dec 6, 2018 at 8:03 PM Daniel Cunha <da...@gmail.com> wrote:

> Hi Jon,
>
> Thank you for your fix, it also need to be applied on branch 7.0.1 and on
> 7.1.x I need update my PR with your changes [
> https://github.com/apache/tomee/pull/236]
>
> Em qui, 6 de dez de 2018 às 13:58, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> escreveu:
>
> > Filed a ticket for bval failures and will work on that next.
> > https://issues.apache.org/jira/browse/TOMEE-2327
> >
> > Jon
> >
> > On Thu, Dec 6, 2018 at 3:31 PM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> > > Hopefully this will do the trick:
> > https://github.com/apache/tomee/pull/258.
> > > Full build currently running here.
> > >
> > > Jon
> > >
> > > On Thu, Dec 6, 2018 at 10:46 AM Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> wrote:
> > >
> > >> I believe this is the root cause of these test failures:
> > >>
> > >> WARNING: Failed to invoke bootstrap:
> > >> javax/persistence/spi/PersistenceUnitInfo
> > >>
> > >> Exception in thread "main" java.lang.NoClassDefFoundError:
> > >> org/apache/commons/cli/ParseException
> > >>
> > >> at java.lang.Class.getDeclaredConstructors0(Native Method)
> > >>
> > >> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> > >>
> > >> at java.lang.Class.getConstructor0(Class.java:3075)
> > >>
> > >> at java.lang.Class.getConstructor(Class.java:1825)
> > >>
> > >> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)
> > >>
> > >> Caused by: java.lang.ClassNotFoundException:
> > >> org.apache.commons.cli.ParseException
> > >>
> > >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> > >>
> > >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> > >>
> > >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> > >>
> > >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> > >>
> > >> ... 5 more
> > >>
> > >>
> > >> and its been introduced in this PR:
> > >> https://github.com/apache/tomee/pull/176 (I pulled the 8.0.0-M1 tag,
> > >> where this was working, and applied this PR to it in my working copy,
> > and
> > >> it now fails).
> > >>
> > >>
> > >> Digging in to see if I can fix it. Dani, any thoughts you have are
> > >> appreciated.
> > >>
> > >>
> > >> Jon
> > >>
> > >> On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
> > >> jonathan.gallimore@gmail.com> wrote:
> > >>
> > >>> Looks like we have some new failures in the itest module:
> > >>>
> > >>> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot
> lookup
> > >>> '/CalculatorBeanR...
> > >>>
> > >>> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
> > >>> lookup '/Calculator...
> > >>>
> > >>> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
> > >>> '/CalculatorBeanRem...
> > >>>
> > >>> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
> > >>> '/CalculatorBeanRemote'.
> > >>>
> > >>> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
> > >>> lookup '/CalculatorB...
> > >>>
> > >>> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
> > >>> Cannot lookup '/Cal...
> > >>>
> > >>>
> > >>> I'll take a look. JIRA is:
> > >>> https://issues.apache.org/jira/browse/TOMEE-2322.
> > >>>
> > >>>
> > >>> Cheers
> > >>>
> > >>>
> > >>> Jon
> > >>>
> > >>> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
> > >>> jlmonteiro@tomitribe.com> wrote:
> > >>>
> > >>>> Oups, then I believe I need to apologize guys.
> > >>>>
> > >>>> I wanted to at least fix the 2 imports so we can get a build with
> some
> > >>>> results.
> > >>>>
> > >>>> --
> > >>>> Jean-Louis Monteiro
> > >>>> http://twitter.com/jlouismonteiro
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>
> > >>>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
> > >>>> jonathan.gallimore@gmail.com> wrote:
> > >>>>
> > >>>> > I appreciate that. Can I ask you be mindful that Frankie posted,
> > and I
> > >>>> > asked him if he wanted to have a go in my reply? We should give
> him
> > >>>> some
> > >>>> > time to respond, before someone else picks it up. If Frankie
> worked
> > on
> > >>>> > fixing those, and then found someone else had done the same work
> > >>>> without a
> > >>>> > JIRA, I suspect that would be pretty frustrating.
> > >>>> >
> > >>>> > Jon
> > >>>> >
> > >>>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
> > >>>> > jlmonteiro@tomitribe.com> wrote:
> > >>>> >
> > >>>> > > I can help fixing some of those
> > >>>> > >
> > >>>> > > --
> > >>>> > > Jean-Louis Monteiro
> > >>>> > > http://twitter.com/jlouismonteiro
> > >>>> > > http://www.tomitribe.com
> > >>>> > >
> > >>>> > >
> > >>>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
> > >>>> > > jonathan.gallimore@gmail.com> wrote:
> > >>>> > >
> > >>>> > > > Hi,
> > >>>> > > >
> > >>>> > > > Great question. The commands are:
> > >>>> > > >
> > >>>> > > > Checkstyle: mvn -Pstyle checkstyle:check
> > >>>> > > > PMD: mvn -Pstyle pmd:check
> > >>>> > > >
> > >>>> > > > These are relatively quick to run - about a minute or so.
> > >>>> > > >
> > >>>> > > > Looks like we have 2 checkstyle violations in the build at the
> > >>>> moment:
> > >>>> > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > >>>> > > >
> > >>>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
> > >>>> > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> >
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> > >>>> > > > ruleset.
> > >>>> > > > [ERROR]
> > src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> > >>>> > > > (imports) UnusedImports: Unused import -
> > >>>> > > > org.apache.openejb.loader.SystemClassPath.
> > >>>> > > > [ERROR]
> > src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> > >>>> > > > (imports) UnusedImports: Unused import -
> > >>>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
> > >>>> > > >
> > >>>> > > > Frankie, would you like to have a go at resolving these?
> > >>>> > > >
> > >>>> > > > Cheers
> > >>>> > > >
> > >>>> > > > Jon
> > >>>> > > >
> > >>>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <
> kamin.feuer.2000@gmx.de
> > >
> > >>>> > wrote:
> > >>>> > > >
> > >>>> > > > > What can I do to already detect such problems when I work on
> > the
> > >>>> > code?
> > >>>> > > > > What is the difference on the build system? (additional
> > >>>> checkstyle
> > >>>> > > rules
> > >>>> > > > > ...?
> > >>>> > > > >
> > >>>> > > > > Frankie
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > > > --
> > >>>> > > > > Sent from:
> > >>>> > > > >
> > >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >>>> > > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> > >>>
> >
>
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Hi Jon,

Thank you for your fix, it also need to be applied on branch 7.0.1 and on
7.1.x I need update my PR with your changes [
https://github.com/apache/tomee/pull/236]

Em qui, 6 de dez de 2018 às 13:58, Jonathan Gallimore <
jonathan.gallimore@gmail.com> escreveu:

> Filed a ticket for bval failures and will work on that next.
> https://issues.apache.org/jira/browse/TOMEE-2327
>
> Jon
>
> On Thu, Dec 6, 2018 at 3:31 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > Hopefully this will do the trick:
> https://github.com/apache/tomee/pull/258.
> > Full build currently running here.
> >
> > Jon
> >
> > On Thu, Dec 6, 2018 at 10:46 AM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> >> I believe this is the root cause of these test failures:
> >>
> >> WARNING: Failed to invoke bootstrap:
> >> javax/persistence/spi/PersistenceUnitInfo
> >>
> >> Exception in thread "main" java.lang.NoClassDefFoundError:
> >> org/apache/commons/cli/ParseException
> >>
> >> at java.lang.Class.getDeclaredConstructors0(Native Method)
> >>
> >> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
> >>
> >> at java.lang.Class.getConstructor0(Class.java:3075)
> >>
> >> at java.lang.Class.getConstructor(Class.java:1825)
> >>
> >> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)
> >>
> >> Caused by: java.lang.ClassNotFoundException:
> >> org.apache.commons.cli.ParseException
> >>
> >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> >>
> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> >>
> >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> >>
> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> >>
> >> ... 5 more
> >>
> >>
> >> and its been introduced in this PR:
> >> https://github.com/apache/tomee/pull/176 (I pulled the 8.0.0-M1 tag,
> >> where this was working, and applied this PR to it in my working copy,
> and
> >> it now fails).
> >>
> >>
> >> Digging in to see if I can fix it. Dani, any thoughts you have are
> >> appreciated.
> >>
> >>
> >> Jon
> >>
> >> On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
> >> jonathan.gallimore@gmail.com> wrote:
> >>
> >>> Looks like we have some new failures in the itest module:
> >>>
> >>> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot lookup
> >>> '/CalculatorBeanR...
> >>>
> >>> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
> >>> lookup '/Calculator...
> >>>
> >>> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
> >>> '/CalculatorBeanRem...
> >>>
> >>> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
> >>> '/CalculatorBeanRemote'.
> >>>
> >>> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
> >>> lookup '/CalculatorB...
> >>>
> >>> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
> >>> Cannot lookup '/Cal...
> >>>
> >>>
> >>> I'll take a look. JIRA is:
> >>> https://issues.apache.org/jira/browse/TOMEE-2322.
> >>>
> >>>
> >>> Cheers
> >>>
> >>>
> >>> Jon
> >>>
> >>> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com> wrote:
> >>>
> >>>> Oups, then I believe I need to apologize guys.
> >>>>
> >>>> I wanted to at least fix the 2 imports so we can get a build with some
> >>>> results.
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> wrote:
> >>>>
> >>>> > I appreciate that. Can I ask you be mindful that Frankie posted,
> and I
> >>>> > asked him if he wanted to have a go in my reply? We should give him
> >>>> some
> >>>> > time to respond, before someone else picks it up. If Frankie worked
> on
> >>>> > fixing those, and then found someone else had done the same work
> >>>> without a
> >>>> > JIRA, I suspect that would be pretty frustrating.
> >>>> >
> >>>> > Jon
> >>>> >
> >>>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
> >>>> > jlmonteiro@tomitribe.com> wrote:
> >>>> >
> >>>> > > I can help fixing some of those
> >>>> > >
> >>>> > > --
> >>>> > > Jean-Louis Monteiro
> >>>> > > http://twitter.com/jlouismonteiro
> >>>> > > http://www.tomitribe.com
> >>>> > >
> >>>> > >
> >>>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
> >>>> > > jonathan.gallimore@gmail.com> wrote:
> >>>> > >
> >>>> > > > Hi,
> >>>> > > >
> >>>> > > > Great question. The commands are:
> >>>> > > >
> >>>> > > > Checkstyle: mvn -Pstyle checkstyle:check
> >>>> > > > PMD: mvn -Pstyle pmd:check
> >>>> > > >
> >>>> > > > These are relatively quick to run - about a minute or so.
> >>>> > > >
> >>>> > > > Looks like we have 2 checkstyle violations in the build at the
> >>>> moment:
> >>>> > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >>>> > > >
> >>>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
> >>>> > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> >>>> > > > ruleset.
> >>>> > > > [ERROR]
> src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> >>>> > > > (imports) UnusedImports: Unused import -
> >>>> > > > org.apache.openejb.loader.SystemClassPath.
> >>>> > > > [ERROR]
> src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> >>>> > > > (imports) UnusedImports: Unused import -
> >>>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
> >>>> > > >
> >>>> > > > Frankie, would you like to have a go at resolving these?
> >>>> > > >
> >>>> > > > Cheers
> >>>> > > >
> >>>> > > > Jon
> >>>> > > >
> >>>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <kamin.feuer.2000@gmx.de
> >
> >>>> > wrote:
> >>>> > > >
> >>>> > > > > What can I do to already detect such problems when I work on
> the
> >>>> > code?
> >>>> > > > > What is the difference on the build system? (additional
> >>>> checkstyle
> >>>> > > rules
> >>>> > > > > ...?
> >>>> > > > >
> >>>> > > > > Frankie
> >>>> > > > >
> >>>> > > > >
> >>>> > > > >
> >>>> > > > > --
> >>>> > > > > Sent from:
> >>>> > > > >
> >>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >>>> > > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> >>>
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Filed a ticket for bval failures and will work on that next.
https://issues.apache.org/jira/browse/TOMEE-2327

Jon

On Thu, Dec 6, 2018 at 3:31 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> Hopefully this will do the trick: https://github.com/apache/tomee/pull/258.
> Full build currently running here.
>
> Jon
>
> On Thu, Dec 6, 2018 at 10:46 AM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> I believe this is the root cause of these test failures:
>>
>> WARNING: Failed to invoke bootstrap:
>> javax/persistence/spi/PersistenceUnitInfo
>>
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/apache/commons/cli/ParseException
>>
>> at java.lang.Class.getDeclaredConstructors0(Native Method)
>>
>> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
>>
>> at java.lang.Class.getConstructor0(Class.java:3075)
>>
>> at java.lang.Class.getConstructor(Class.java:1825)
>>
>> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)
>>
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.commons.cli.ParseException
>>
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>>
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>>
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
>>
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>
>> ... 5 more
>>
>>
>> and its been introduced in this PR:
>> https://github.com/apache/tomee/pull/176 (I pulled the 8.0.0-M1 tag,
>> where this was working, and applied this PR to it in my working copy, and
>> it now fails).
>>
>>
>> Digging in to see if I can fix it. Dani, any thoughts you have are
>> appreciated.
>>
>>
>> Jon
>>
>> On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>>
>>> Looks like we have some new failures in the itest module:
>>>
>>> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot lookup
>>> '/CalculatorBeanR...
>>>
>>> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
>>> lookup '/Calculator...
>>>
>>> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
>>> '/CalculatorBeanRem...
>>>
>>> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
>>> '/CalculatorBeanRemote'.
>>>
>>> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
>>> lookup '/CalculatorB...
>>>
>>> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
>>> Cannot lookup '/Cal...
>>>
>>>
>>> I'll take a look. JIRA is:
>>> https://issues.apache.org/jira/browse/TOMEE-2322.
>>>
>>>
>>> Cheers
>>>
>>>
>>> Jon
>>>
>>> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com> wrote:
>>>
>>>> Oups, then I believe I need to apologize guys.
>>>>
>>>> I wanted to at least fix the 2 imports so we can get a build with some
>>>> results.
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
>>>> jonathan.gallimore@gmail.com> wrote:
>>>>
>>>> > I appreciate that. Can I ask you be mindful that Frankie posted, and I
>>>> > asked him if he wanted to have a go in my reply? We should give him
>>>> some
>>>> > time to respond, before someone else picks it up. If Frankie worked on
>>>> > fixing those, and then found someone else had done the same work
>>>> without a
>>>> > JIRA, I suspect that would be pretty frustrating.
>>>> >
>>>> > Jon
>>>> >
>>>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
>>>> > jlmonteiro@tomitribe.com> wrote:
>>>> >
>>>> > > I can help fixing some of those
>>>> > >
>>>> > > --
>>>> > > Jean-Louis Monteiro
>>>> > > http://twitter.com/jlouismonteiro
>>>> > > http://www.tomitribe.com
>>>> > >
>>>> > >
>>>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
>>>> > > jonathan.gallimore@gmail.com> wrote:
>>>> > >
>>>> > > > Hi,
>>>> > > >
>>>> > > > Great question. The commands are:
>>>> > > >
>>>> > > > Checkstyle: mvn -Pstyle checkstyle:check
>>>> > > > PMD: mvn -Pstyle pmd:check
>>>> > > >
>>>> > > > These are relatively quick to run - about a minute or so.
>>>> > > >
>>>> > > > Looks like we have 2 checkstyle violations in the build at the
>>>> moment:
>>>> > > >
>>>> > > >
>>>> > >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>> > > >
>>>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
>>>> > > >
>>>> > > >
>>>> > >
>>>> >
>>>> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
>>>> > > > ruleset.
>>>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
>>>> > > > (imports) UnusedImports: Unused import -
>>>> > > > org.apache.openejb.loader.SystemClassPath.
>>>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
>>>> > > > (imports) UnusedImports: Unused import -
>>>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
>>>> > > >
>>>> > > > Frankie, would you like to have a go at resolving these?
>>>> > > >
>>>> > > > Cheers
>>>> > > >
>>>> > > > Jon
>>>> > > >
>>>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de>
>>>> > wrote:
>>>> > > >
>>>> > > > > What can I do to already detect such problems when I work on the
>>>> > code?
>>>> > > > > What is the difference on the build system? (additional
>>>> checkstyle
>>>> > > rules
>>>> > > > > ...?
>>>> > > > >
>>>> > > > > Frankie
>>>> > > > >
>>>> > > > >
>>>> > > > >
>>>> > > > > --
>>>> > > > > Sent from:
>>>> > > > >
>>>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>>> > > > >
>>>> > > >
>>>> > >
>>>> >
>>>>
>>>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Hopefully this will do the trick: https://github.com/apache/tomee/pull/258.
Full build currently running here.

Jon

On Thu, Dec 6, 2018 at 10:46 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I believe this is the root cause of these test failures:
>
> WARNING: Failed to invoke bootstrap:
> javax/persistence/spi/PersistenceUnitInfo
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/cli/ParseException
>
> at java.lang.Class.getDeclaredConstructors0(Native Method)
>
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
>
> at java.lang.Class.getConstructor0(Class.java:3075)
>
> at java.lang.Class.getConstructor(Class.java:1825)
>
> at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)
>
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.cli.ParseException
>
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
> ... 5 more
>
>
> and its been introduced in this PR:
> https://github.com/apache/tomee/pull/176 (I pulled the 8.0.0-M1 tag,
> where this was working, and applied this PR to it in my working copy, and
> it now fails).
>
>
> Digging in to see if I can fix it. Dani, any thoughts you have are
> appreciated.
>
>
> Jon
>
> On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> Looks like we have some new failures in the itest module:
>>
>> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot lookup
>> '/CalculatorBeanR...
>>
>> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
>> lookup '/Calculator...
>>
>> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
>> '/CalculatorBeanRem...
>>
>> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
>> '/CalculatorBeanRemote'.
>>
>> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
>> lookup '/CalculatorB...
>>
>> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
>> Cannot lookup '/Cal...
>>
>>
>> I'll take a look. JIRA is:
>> https://issues.apache.org/jira/browse/TOMEE-2322.
>>
>>
>> Cheers
>>
>>
>> Jon
>>
>> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> Oups, then I believe I need to apologize guys.
>>>
>>> I wanted to at least fix the 2 imports so we can get a build with some
>>> results.
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
>>> jonathan.gallimore@gmail.com> wrote:
>>>
>>> > I appreciate that. Can I ask you be mindful that Frankie posted, and I
>>> > asked him if he wanted to have a go in my reply? We should give him
>>> some
>>> > time to respond, before someone else picks it up. If Frankie worked on
>>> > fixing those, and then found someone else had done the same work
>>> without a
>>> > JIRA, I suspect that would be pretty frustrating.
>>> >
>>> > Jon
>>> >
>>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
>>> > jlmonteiro@tomitribe.com> wrote:
>>> >
>>> > > I can help fixing some of those
>>> > >
>>> > > --
>>> > > Jean-Louis Monteiro
>>> > > http://twitter.com/jlouismonteiro
>>> > > http://www.tomitribe.com
>>> > >
>>> > >
>>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
>>> > > jonathan.gallimore@gmail.com> wrote:
>>> > >
>>> > > > Hi,
>>> > > >
>>> > > > Great question. The commands are:
>>> > > >
>>> > > > Checkstyle: mvn -Pstyle checkstyle:check
>>> > > > PMD: mvn -Pstyle pmd:check
>>> > > >
>>> > > > These are relatively quick to run - about a minute or so.
>>> > > >
>>> > > > Looks like we have 2 checkstyle violations in the build at the
>>> moment:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>> > > >
>>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
>>> > > >
>>> > > >
>>> > >
>>> >
>>> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
>>> > > > ruleset.
>>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
>>> > > > (imports) UnusedImports: Unused import -
>>> > > > org.apache.openejb.loader.SystemClassPath.
>>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
>>> > > > (imports) UnusedImports: Unused import -
>>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
>>> > > >
>>> > > > Frankie, would you like to have a go at resolving these?
>>> > > >
>>> > > > Cheers
>>> > > >
>>> > > > Jon
>>> > > >
>>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de>
>>> > wrote:
>>> > > >
>>> > > > > What can I do to already detect such problems when I work on the
>>> > code?
>>> > > > > What is the difference on the build system? (additional
>>> checkstyle
>>> > > rules
>>> > > > > ...?
>>> > > > >
>>> > > > > Frankie
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > > Sent from:
>>> > > > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I believe this is the root cause of these test failures:

WARNING: Failed to invoke bootstrap:
javax/persistence/spi/PersistenceUnitInfo

Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/commons/cli/ParseException

at java.lang.Class.getDeclaredConstructors0(Native Method)

at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)

at java.lang.Class.getConstructor0(Class.java:3075)

at java.lang.Class.getConstructor(Class.java:1825)

at org.apache.openejb.cli.Bootstrap.main(Bootstrap.java:155)

Caused by: java.lang.ClassNotFoundException:
org.apache.commons.cli.ParseException

at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)

at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

... 5 more


and its been introduced in this PR: https://github.com/apache/tomee/pull/176
(I pulled the 8.0.0-M1 tag, where this was working, and applied this PR to
it in my working copy, and it now fails).


Digging in to see if I can fix it. Dani, any thoughts you have are
appreciated.


Jon

On Wed, Dec 5, 2018 at 9:44 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> Looks like we have some new failures in the itest module:
>
> [ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot lookup
> '/CalculatorBeanR...
>
> [ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot
> lookup '/Calculator...
>
> [ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
> '/CalculatorBeanRem...
>
> [ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
> '/CalculatorBeanRemote'.
>
> [ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot
> lookup '/CalculatorB...
>
> [ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming
> Cannot lookup '/Cal...
>
>
> I'll take a look. JIRA is:
> https://issues.apache.org/jira/browse/TOMEE-2322.
>
>
> Cheers
>
>
> Jon
>
> On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> Oups, then I believe I need to apologize guys.
>>
>> I wanted to at least fix the 2 imports so we can get a build with some
>> results.
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>>
>> > I appreciate that. Can I ask you be mindful that Frankie posted, and I
>> > asked him if he wanted to have a go in my reply? We should give him some
>> > time to respond, before someone else picks it up. If Frankie worked on
>> > fixing those, and then found someone else had done the same work
>> without a
>> > JIRA, I suspect that would be pretty frustrating.
>> >
>> > Jon
>> >
>> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
>> > jlmonteiro@tomitribe.com> wrote:
>> >
>> > > I can help fixing some of those
>> > >
>> > > --
>> > > Jean-Louis Monteiro
>> > > http://twitter.com/jlouismonteiro
>> > > http://www.tomitribe.com
>> > >
>> > >
>> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
>> > > jonathan.gallimore@gmail.com> wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > Great question. The commands are:
>> > > >
>> > > > Checkstyle: mvn -Pstyle checkstyle:check
>> > > > PMD: mvn -Pstyle pmd:check
>> > > >
>> > > > These are relatively quick to run - about a minute or so.
>> > > >
>> > > > Looks like we have 2 checkstyle violations in the build at the
>> moment:
>> > > >
>> > > >
>> > >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > > >
>> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
>> > > >
>> > > >
>> > >
>> >
>> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
>> > > > ruleset.
>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
>> > > > (imports) UnusedImports: Unused import -
>> > > > org.apache.openejb.loader.SystemClassPath.
>> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
>> > > > (imports) UnusedImports: Unused import -
>> > > > org.apache.openejb.loader.JarLocation.jarLocation.
>> > > >
>> > > > Frankie, would you like to have a go at resolving these?
>> > > >
>> > > > Cheers
>> > > >
>> > > > Jon
>> > > >
>> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de>
>> > wrote:
>> > > >
>> > > > > What can I do to already detect such problems when I work on the
>> > code?
>> > > > > What is the difference on the build system? (additional checkstyle
>> > > rules
>> > > > > ...?
>> > > > >
>> > > > > Frankie
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Sent from:
>> > > > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Looks like we have some new failures in the itest module:

[ERROR]   RandomConnectionStrategyTest.test:162 » Naming Cannot lookup
'/CalculatorBeanR...

[ERROR]   ReconnectDelayCaseInsensitiveTest.test:150 » Naming Cannot lookup
'/Calculator...

[ERROR]   ReconnectDelayListSelfTest.test:150 » Naming Cannot lookup
'/CalculatorBeanRem...

[ERROR]   ReconnectDelayTest.test:131 » Naming Cannot lookup
'/CalculatorBeanRemote'.

[ERROR]   RoundRobinConnectionStrategyTest.test:164 » Naming Cannot lookup
'/CalculatorB...

[ERROR]   StickyConnectionStrategyTest.test:146->invoke:225 » Naming Cannot
lookup '/Cal...


I'll take a look. JIRA is: https://issues.apache.org/jira/browse/TOMEE-2322.


Cheers


Jon

On Wed, Dec 5, 2018 at 12:39 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> Oups, then I believe I need to apologize guys.
>
> I wanted to at least fix the 2 imports so we can get a build with some
> results.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > I appreciate that. Can I ask you be mindful that Frankie posted, and I
> > asked him if he wanted to have a go in my reply? We should give him some
> > time to respond, before someone else picks it up. If Frankie worked on
> > fixing those, and then found someone else had done the same work without
> a
> > JIRA, I suspect that would be pretty frustrating.
> >
> > Jon
> >
> > On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> > > I can help fixing some of those
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > Great question. The commands are:
> > > >
> > > > Checkstyle: mvn -Pstyle checkstyle:check
> > > > PMD: mvn -Pstyle pmd:check
> > > >
> > > > These are relatively quick to run - about a minute or so.
> > > >
> > > > Looks like we have 2 checkstyle violations in the build at the
> moment:
> > > >
> > > >
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > > >
> > > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
> > > >
> > > >
> > >
> >
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> > > > ruleset.
> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> > > > (imports) UnusedImports: Unused import -
> > > > org.apache.openejb.loader.SystemClassPath.
> > > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> > > > (imports) UnusedImports: Unused import -
> > > > org.apache.openejb.loader.JarLocation.jarLocation.
> > > >
> > > > Frankie, would you like to have a go at resolving these?
> > > >
> > > > Cheers
> > > >
> > > > Jon
> > > >
> > > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de>
> > wrote:
> > > >
> > > > > What can I do to already detect such problems when I work on the
> > code?
> > > > > What is the difference on the build system? (additional checkstyle
> > > rules
> > > > > ...?
> > > > >
> > > > > Frankie
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from:
> > > > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > > >
> > > >
> > >
> >
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Oups, then I believe I need to apologize guys.

I wanted to at least fix the 2 imports so we can get a build with some
results.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 5, 2018 at 1:24 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I appreciate that. Can I ask you be mindful that Frankie posted, and I
> asked him if he wanted to have a go in my reply? We should give him some
> time to respond, before someone else picks it up. If Frankie worked on
> fixing those, and then found someone else had done the same work without a
> JIRA, I suspect that would be pretty frustrating.
>
> Jon
>
> On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > I can help fixing some of those
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Great question. The commands are:
> > >
> > > Checkstyle: mvn -Pstyle checkstyle:check
> > > PMD: mvn -Pstyle pmd:check
> > >
> > > These are relatively quick to run - about a minute or so.
> > >
> > > Looks like we have 2 checkstyle violations in the build at the moment:
> > >
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > >
> > > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
> > >
> > >
> >
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> > > ruleset.
> > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> > > (imports) UnusedImports: Unused import -
> > > org.apache.openejb.loader.SystemClassPath.
> > > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> > > (imports) UnusedImports: Unused import -
> > > org.apache.openejb.loader.JarLocation.jarLocation.
> > >
> > > Frankie, would you like to have a go at resolving these?
> > >
> > > Cheers
> > >
> > > Jon
> > >
> > > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de>
> wrote:
> > >
> > > > What can I do to already detect such problems when I work on the
> code?
> > > > What is the difference on the build system? (additional checkstyle
> > rules
> > > > ...?
> > > >
> > > > Frankie
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from:
> > > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > > >
> > >
> >
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I appreciate that. Can I ask you be mindful that Frankie posted, and I
asked him if he wanted to have a go in my reply? We should give him some
time to respond, before someone else picks it up. If Frankie worked on
fixing those, and then found someone else had done the same work without a
JIRA, I suspect that would be pretty frustrating.

Jon

On Wed, Dec 5, 2018 at 12:03 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> I can help fixing some of those
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > Hi,
> >
> > Great question. The commands are:
> >
> > Checkstyle: mvn -Pstyle checkstyle:check
> > PMD: mvn -Pstyle pmd:check
> >
> > These are relatively quick to run - about a minute or so.
> >
> > Looks like we have 2 checkstyle violations in the build at the moment:
> >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >
> > [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
> >
> >
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> > ruleset.
> > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> > (imports) UnusedImports: Unused import -
> > org.apache.openejb.loader.SystemClassPath.
> > [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> > (imports) UnusedImports: Unused import -
> > org.apache.openejb.loader.JarLocation.jarLocation.
> >
> > Frankie, would you like to have a go at resolving these?
> >
> > Cheers
> >
> > Jon
> >
> > On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de> wrote:
> >
> > > What can I do to already detect such problems when I work on the code?
> > > What is the difference on the build system? (additional checkstyle
> rules
> > > ...?
> > >
> > > Frankie
> > >
> > >
> > >
> > > --
> > > Sent from:
> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >
> >
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I can help fixing some of those

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Dec 5, 2018 at 11:40 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> Hi,
>
> Great question. The commands are:
>
> Checkstyle: mvn -Pstyle checkstyle:check
> PMD: mvn -Pstyle pmd:check
>
> These are relatively quick to run - about a minute or so.
>
> Looks like we have 2 checkstyle violations in the build at the moment:
>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>
> [INFO] There are 2 errors reported by Checkstyle 6.1.1 with
>
> /home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
> ruleset.
> [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
> (imports) UnusedImports: Unused import -
> org.apache.openejb.loader.SystemClassPath.
> [ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
> (imports) UnusedImports: Unused import -
> org.apache.openejb.loader.JarLocation.jarLocation.
>
> Frankie, would you like to have a go at resolving these?
>
> Cheers
>
> Jon
>
> On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de> wrote:
>
> > What can I do to already detect such problems when I work on the code?
> > What is the difference on the build system? (additional checkstyle rules
> > ...?
> >
> > Frankie
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Hi,

Great question. The commands are:

Checkstyle: mvn -Pstyle checkstyle:check
PMD: mvn -Pstyle pmd:check

These are relatively quick to run - about a minute or so.

Looks like we have 2 checkstyle violations in the build at the moment:
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio

[INFO] There are 2 errors reported by Checkstyle 6.1.1 with
/home/buildslave/slave/tomee-trunk-ubuntu-jvm8/build/src/main/style/checkstyle.xml
ruleset.
[ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[22:8]
(imports) UnusedImports: Unused import -
org.apache.openejb.loader.SystemClassPath.
[ERROR] src/main/java/org/apache/openejb/cli/Bootstrap.java[34:15]
(imports) UnusedImports: Unused import -
org.apache.openejb.loader.JarLocation.jarLocation.

Frankie, would you like to have a go at resolving these?

Cheers

Jon

On Wed, Dec 5, 2018 at 6:50 AM Frankie <ka...@gmx.de> wrote:

> What can I do to already detect such problems when I work on the code?
> What is the difference on the build system? (additional checkstyle rules
> ...?
>
> Frankie
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Re: Stabilize TomEE Build

[Frankie <ka...@gmx.de>]

What can I do to already detect such problems when I work on the code?
What is the difference on the build system? (additional checkstyle rules
...?

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

Looks like a CXF upgrade changed the API CXF is implementing. If we upgrade
the API on our MicroProfile module then we won't be 1.3 compliant.

But other solution is to downgrade CXF to match MP 1.3 which has
rest-client 1.0

I'd rather get TomEE 8 to be upgraded in regards to MP so we support MP
higher than 1.3

Thoughts


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 7, 2018 at 4:29 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Hi folks,
>
> Thank you for working on this.
>
> Were we able to determine the cause of all these issues? When we did the
> M1 release and even after that we had green builds, so it seems we did
> something that broke a lot of tests?
>
> Cheers,
> Roberto
>
> > On 7 Dec 2018, at 15:05, Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> >
> > The rest-client seems to be a version issue
> >
> > [ERROR]
> >
> testInvokesPostOperation(org.eclipse.microprofile.rest.client.tck.cditests.CDIInvokeWithRegisteredProvidersTest)
> > Time elapsed: 0.521 s  <<< FAILURE!
> > java.lang.NoSuchMethodError:
> >
> org.eclipse.microprofile.rest.client.RestClientBuilder.baseUri(Ljava/net/URI;)Lorg/eclipse/microprofile/rest/client/RestClientBuilder;
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Fri, Dec 7, 2018 at 3:56 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com>
> > wrote:
> >
> >> The Duplicate one is also BVal Jon.
> >> I'l looking at the rest-client part.
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Fri, Dec 7, 2018 at 2:55 PM Jean-Louis Monteiro <
> >> jlmonteiro@tomitribe.com> wrote:
> >>
> >>> JmsInjectionTests works locally
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Fri, Dec 7, 2018 at 11:52 AM Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com> wrote:
> >>>
> >>>> I have been digging and running tests locally.
> >>>> Here is the list of tests failures I have extracted.
> >>>>
> >>>> - JMSInjectionTest
> >>>> - CDIInvokeSimpleGetOperationTest
> >>>> - CDIInvokeWithRegisteredProviderTest
> >>>> - FeatureRegistrationTest
> >>>> - InvokeWithJsonProviderTest
> >>>> - DuplicateConfigurationTest
> >>>> - XMLConfigurationTest
> >>>> - XMLConfiguredConstraintValidatorTest
> >>>> - MoviesArquillianHtmlUnitTest
> >>>> - DeployInWebAppsDirectoryTest
> >>>> - LegacyServerTest
> >>>> - LegacyClientTest
> >>>> - (StickyConnection|RoundRobin|Random)StrategyTest
> >>>> - ReconnectDelayCaseInsensitiveTest
> >>>> - ReconnectDelayListSelfTest
> >>>> - ReconnectTest
> >>>>
> >>>> Anything else I missed?
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> wrote:
> >>>>
> >>>>> I've merged a few PRs in which appear to have kept the build in the
> same
> >>>>> state. I also fixed up the itest failures. I'll work on bval
> tomorrow. I
> >>>>> get failures with the MicroProfile REST client locally, so if someone
> >>>>> can
> >>>>> take a look at that, that would be great.
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Jon
> >>>>>
> >>>>> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
> >>>>> <ra...@yahoo.com.invalid>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi folks,
> >>>>>>
> >>>>>> It is great to see so many contributions and we hope to continue and
> >>>>> even
> >>>>>> increase the traffic.
> >>>>>>
> >>>>>> Now, this also comes with a few challenges. Our build has been red
> >>>>> for a
> >>>>>> while and I would like to get it green again:
> >>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> <
> >>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> >
> >>>>>>
> >>>>>> The latest build has some checkstyle violations and test failures:
> >>>>>>
> >>>>>>
> >>>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >>>>>> <
> >>>>>>
> >>>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> >>>>>> <
> >>>>>>
> >>>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> >>>>>>>
> >>>>>>
> >>>>>> It would be great if someone could pick these issues and fix them
> and
> >>>>> we
> >>>>>> should prioritize any build fixing PR above everything else.
> >>>>>>
> >>>>>> Also, when someone sends a PR, your work doesn’t end when it gets
> >>>>> merged.
> >>>>>> Running a full build takes almost 5 hours, so the committer most of
> >>>>> the
> >>>>>> times is not able to run the entire build to check your PR. I kindly
> >>>>> ask
> >>>>>> you to monitor the tomee build bot here:
> >>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> >>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your
> PR
> >>>>>> gets merged and if you uncover something wrong, please send a
> >>>>> corrective PR.
> >>>>>>
> >>>>>> I’ll be out the next couple of days, so I hope someone can pick this
> >>>>> up :)
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Roberto
> >>>>>
> >>>>
>
>

Re: Stabilize TomEE Build

[Roberto Cortez <ra...@yahoo.com.INVALID>]

Hi folks,

Thank you for working on this.

Were we able to determine the cause of all these issues? When we did the M1 release and even after that we had green builds, so it seems we did something that broke a lot of tests?

Cheers,
Roberto

> On 7 Dec 2018, at 15:05, Jean-Louis Monteiro <jl...@tomitribe.com> wrote:
> 
> The rest-client seems to be a version issue
> 
> [ERROR]
> testInvokesPostOperation(org.eclipse.microprofile.rest.client.tck.cditests.CDIInvokeWithRegisteredProvidersTest)
> Time elapsed: 0.521 s  <<< FAILURE!
> java.lang.NoSuchMethodError:
> org.eclipse.microprofile.rest.client.RestClientBuilder.baseUri(Ljava/net/URI;)Lorg/eclipse/microprofile/rest/client/RestClientBuilder;
> 
> 
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Fri, Dec 7, 2018 at 3:56 PM Jean-Louis Monteiro <jl...@tomitribe.com>
> wrote:
> 
>> The Duplicate one is also BVal Jon.
>> I'l looking at the rest-client part.
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>> 
>> 
>> On Fri, Dec 7, 2018 at 2:55 PM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>> 
>>> JmsInjectionTests works locally
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>> 
>>> 
>>> On Fri, Dec 7, 2018 at 11:52 AM Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com> wrote:
>>> 
>>>> I have been digging and running tests locally.
>>>> Here is the list of tests failures I have extracted.
>>>> 
>>>> - JMSInjectionTest
>>>> - CDIInvokeSimpleGetOperationTest
>>>> - CDIInvokeWithRegisteredProviderTest
>>>> - FeatureRegistrationTest
>>>> - InvokeWithJsonProviderTest
>>>> - DuplicateConfigurationTest
>>>> - XMLConfigurationTest
>>>> - XMLConfiguredConstraintValidatorTest
>>>> - MoviesArquillianHtmlUnitTest
>>>> - DeployInWebAppsDirectoryTest
>>>> - LegacyServerTest
>>>> - LegacyClientTest
>>>> - (StickyConnection|RoundRobin|Random)StrategyTest
>>>> - ReconnectDelayCaseInsensitiveTest
>>>> - ReconnectDelayListSelfTest
>>>> - ReconnectTest
>>>> 
>>>> Anything else I missed?
>>>> 
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>> 
>>>> 
>>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>>>> jonathan.gallimore@gmail.com> wrote:
>>>> 
>>>>> I've merged a few PRs in which appear to have kept the build in the same
>>>>> state. I also fixed up the itest failures. I'll work on bval tomorrow. I
>>>>> get failures with the MicroProfile REST client locally, so if someone
>>>>> can
>>>>> take a look at that, that would be great.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> Jon
>>>>> 
>>>>> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>>>>> <ra...@yahoo.com.invalid>
>>>>> wrote:
>>>>> 
>>>>>> Hi folks,
>>>>>> 
>>>>>> It is great to see so many contributions and we hope to continue and
>>>>> even
>>>>>> increase the traffic.
>>>>>> 
>>>>>> Now, this also comes with a few challenges. Our build has been red
>>>>> for a
>>>>>> while and I would like to get it green again:
>>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
>>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>>>>>> 
>>>>>> The latest build has some checkstyle violations and test failures:
>>>>>> 
>>>>>> 
>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>>>> <
>>>>>> 
>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>>>> <
>>>>>> 
>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>>>>> 
>>>>>> 
>>>>>> It would be great if someone could pick these issues and fix them and
>>>>> we
>>>>>> should prioritize any build fixing PR above everything else.
>>>>>> 
>>>>>> Also, when someone sends a PR, your work doesn’t end when it gets
>>>>> merged.
>>>>>> Running a full build takes almost 5 hours, so the committer most of
>>>>> the
>>>>>> times is not able to run the entire build to check your PR. I kindly
>>>>> ask
>>>>>> you to monitor the tomee build bot here:
>>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>>>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
>>>>>> gets merged and if you uncover something wrong, please send a
>>>>> corrective PR.
>>>>>> 
>>>>>> I’ll be out the next couple of days, so I hope someone can pick this
>>>>> up :)
>>>>>> 
>>>>>> Cheers,
>>>>>> Roberto
>>>>> 
>>>> 

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

The rest-client seems to be a version issue

[ERROR]
testInvokesPostOperation(org.eclipse.microprofile.rest.client.tck.cditests.CDIInvokeWithRegisteredProvidersTest)
Time elapsed: 0.521 s  <<< FAILURE!
java.lang.NoSuchMethodError:
org.eclipse.microprofile.rest.client.RestClientBuilder.baseUri(Ljava/net/URI;)Lorg/eclipse/microprofile/rest/client/RestClientBuilder;


--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 7, 2018 at 3:56 PM Jean-Louis Monteiro <jl...@tomitribe.com>
wrote:

> The Duplicate one is also BVal Jon.
> I'l looking at the rest-client part.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Dec 7, 2018 at 2:55 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> JmsInjectionTests works locally
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Fri, Dec 7, 2018 at 11:52 AM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> I have been digging and running tests locally.
>>> Here is the list of tests failures I have extracted.
>>>
>>> - JMSInjectionTest
>>> - CDIInvokeSimpleGetOperationTest
>>> - CDIInvokeWithRegisteredProviderTest
>>> - FeatureRegistrationTest
>>> - InvokeWithJsonProviderTest
>>> - DuplicateConfigurationTest
>>> - XMLConfigurationTest
>>> - XMLConfiguredConstraintValidatorTest
>>> - MoviesArquillianHtmlUnitTest
>>> - DeployInWebAppsDirectoryTest
>>> - LegacyServerTest
>>> - LegacyClientTest
>>> - (StickyConnection|RoundRobin|Random)StrategyTest
>>> - ReconnectDelayCaseInsensitiveTest
>>> - ReconnectDelayListSelfTest
>>> - ReconnectTest
>>>
>>> Anything else I missed?
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>>> jonathan.gallimore@gmail.com> wrote:
>>>
>>>> I've merged a few PRs in which appear to have kept the build in the same
>>>> state. I also fixed up the itest failures. I'll work on bval tomorrow. I
>>>> get failures with the MicroProfile REST client locally, so if someone
>>>> can
>>>> take a look at that, that would be great.
>>>>
>>>> Thanks
>>>>
>>>> Jon
>>>>
>>>> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>>>> <ra...@yahoo.com.invalid>
>>>> wrote:
>>>>
>>>> > Hi folks,
>>>> >
>>>> > It is great to see so many contributions and we hope to continue and
>>>> even
>>>> > increase the traffic.
>>>> >
>>>> > Now, this also comes with a few challenges. Our build has been red
>>>> for a
>>>> > while and I would like to get it green again:
>>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
>>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>>>> >
>>>> > The latest build has some checkstyle violations and test failures:
>>>> >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>> > <
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>> > >
>>>> >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>> > <
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>> > >
>>>> >
>>>> > It would be great if someone could pick these issues and fix them and
>>>> we
>>>> > should prioritize any build fixing PR above everything else.
>>>> >
>>>> > Also, when someone sends a PR, your work doesn’t end when it gets
>>>> merged.
>>>> > Running a full build takes almost 5 hours, so the committer most of
>>>> the
>>>> > times is not able to run the entire build to check your PR. I kindly
>>>> ask
>>>> > you to monitor the tomee build bot here:
>>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
>>>> > gets merged and if you uncover something wrong, please send a
>>>> corrective PR.
>>>> >
>>>> > I’ll be out the next couple of days, so I hope someone can pick this
>>>> up :)
>>>> >
>>>> > Cheers,
>>>> > Roberto
>>>>
>>>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

The Duplicate one is also BVal Jon.
I'l looking at the rest-client part.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 7, 2018 at 2:55 PM Jean-Louis Monteiro <jl...@tomitribe.com>
wrote:

> JmsInjectionTests works locally
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Fri, Dec 7, 2018 at 11:52 AM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> I have been digging and running tests locally.
>> Here is the list of tests failures I have extracted.
>>
>> - JMSInjectionTest
>> - CDIInvokeSimpleGetOperationTest
>> - CDIInvokeWithRegisteredProviderTest
>> - FeatureRegistrationTest
>> - InvokeWithJsonProviderTest
>> - DuplicateConfigurationTest
>> - XMLConfigurationTest
>> - XMLConfiguredConstraintValidatorTest
>> - MoviesArquillianHtmlUnitTest
>> - DeployInWebAppsDirectoryTest
>> - LegacyServerTest
>> - LegacyClientTest
>> - (StickyConnection|RoundRobin|Random)StrategyTest
>> - ReconnectDelayCaseInsensitiveTest
>> - ReconnectDelayListSelfTest
>> - ReconnectTest
>>
>> Anything else I missed?
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>>
>>> I've merged a few PRs in which appear to have kept the build in the same
>>> state. I also fixed up the itest failures. I'll work on bval tomorrow. I
>>> get failures with the MicroProfile REST client locally, so if someone can
>>> take a look at that, that would be great.
>>>
>>> Thanks
>>>
>>> Jon
>>>
>>> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>>> <ra...@yahoo.com.invalid>
>>> wrote:
>>>
>>> > Hi folks,
>>> >
>>> > It is great to see so many contributions and we hope to continue and
>>> even
>>> > increase the traffic.
>>> >
>>> > Now, this also comes with a few challenges. Our build has been red for
>>> a
>>> > while and I would like to get it green again:
>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>>> >
>>> > The latest build has some checkstyle violations and test failures:
>>> >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>> > <
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>> > >
>>> >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>> > <
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>> > >
>>> >
>>> > It would be great if someone could pick these issues and fix them and
>>> we
>>> > should prioritize any build fixing PR above everything else.
>>> >
>>> > Also, when someone sends a PR, your work doesn’t end when it gets
>>> merged.
>>> > Running a full build takes almost 5 hours, so the committer most of the
>>> > times is not able to run the entire build to check your PR. I kindly
>>> ask
>>> > you to monitor the tomee build bot here:
>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
>>> > gets merged and if you uncover something wrong, please send a
>>> corrective PR.
>>> >
>>> > I’ll be out the next couple of days, so I hope someone can pick this
>>> up :)
>>> >
>>> > Cheers,
>>> > Roberto
>>>
>>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

JmsInjectionTests works locally
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Fri, Dec 7, 2018 at 11:52 AM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> I have been digging and running tests locally.
> Here is the list of tests failures I have extracted.
>
> - JMSInjectionTest
> - CDIInvokeSimpleGetOperationTest
> - CDIInvokeWithRegisteredProviderTest
> - FeatureRegistrationTest
> - InvokeWithJsonProviderTest
> - DuplicateConfigurationTest
> - XMLConfigurationTest
> - XMLConfiguredConstraintValidatorTest
> - MoviesArquillianHtmlUnitTest
> - DeployInWebAppsDirectoryTest
> - LegacyServerTest
> - LegacyClientTest
> - (StickyConnection|RoundRobin|Random)StrategyTest
> - ReconnectDelayCaseInsensitiveTest
> - ReconnectDelayListSelfTest
> - ReconnectTest
>
> Anything else I missed?
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> I've merged a few PRs in which appear to have kept the build in the same
>> state. I also fixed up the itest failures. I'll work on bval tomorrow. I
>> get failures with the MicroProfile REST client locally, so if someone can
>> take a look at that, that would be great.
>>
>> Thanks
>>
>> Jon
>>
>> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>> <ra...@yahoo.com.invalid>
>> wrote:
>>
>> > Hi folks,
>> >
>> > It is great to see so many contributions and we hope to continue and
>> even
>> > increase the traffic.
>> >
>> > Now, this also comes with a few challenges. Our build has been red for a
>> > while and I would like to get it green again:
>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>> >
>> > The latest build has some checkstyle violations and test failures:
>> >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > <
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > >
>> >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>> > <
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>> > >
>> >
>> > It would be great if someone could pick these issues and fix them and we
>> > should prioritize any build fixing PR above everything else.
>> >
>> > Also, when someone sends a PR, your work doesn’t end when it gets
>> merged.
>> > Running a full build takes almost 5 hours, so the committer most of the
>> > times is not able to run the entire build to check your PR. I kindly ask
>> > you to monitor the tomee build bot here:
>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
>> > gets merged and if you uncover something wrong, please send a
>> corrective PR.
>> >
>> > I’ll be out the next couple of days, so I hope someone can pick this up
>> :)
>> >
>> > Cheers,
>> > Roberto
>>
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Ok Jon,

I'll work on these tests.

Thanks.

Em sex, 7 de dez de 2018 às 16:23, Jonathan Gallimore <
jonathan.gallimore@gmail.com> escreveu:

> Thanks Dani.
>
> That's right, and these two as well:
>
> XMLConfigurationTest
> - XMLConfiguredConstraintValidatorTest
>
> On Fri, 7 Dec 2018, 18:20 Daniel Cunha <danielsoro@gmail.com wrote:
>
> > Hey Jon,
> >
> > I can help with BVal tests.
> > If I get it is the BVal test related DuplicateConfigurationTest right?
> >
> >
> > Em sex, 7 de dez de 2018 às 14:03, Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> escreveu:
> >
> > > Filed a ticket: https://issues.apache.org/jira/browse/TOMEE-2330. We
> > could
> > > ignore the test in the meantime.
> > >
> > > Jon
> > >
> > > On Fri, Dec 7, 2018 at 4:36 PM Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> wrote:
> > >
> > > > I committed a fix for CustomOrmXmlTest. The failure in
> CmpMappingsTest
> > > > actually looks like a genuine error case that only affects
> > > > Plume/EclipseLink. I'm digging in.
> > > >
> > > > Does someone want to take the BVal tests off me? Not required, but if
> > > > someone is looking for something to do, I'm happy to hand those
> over, I
> > > > haven't made any real progress with them.
> > > >
> > > > Jon
> > > >
> > > > On Fri, Dec 7, 2018 at 11:08 AM Jonathan Gallimore <
> > > > jonathan.gallimore@gmail.com> wrote:
> > > >
> > > >> I see this also fails on
> > > >> buildbot:
> > > org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
> > > >> its a simple fix which I'll commit now.
> > > >>
> > > >> Jon
> > > >>
> > > >> On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
> > > >> jonathan.gallimore@gmail.com> wrote:
> > > >>
> > > >>> Hey Jean-Louis
> > > >>>
> > > >>> Thanks for the list!
> > > >>>
> > > >>> These ones _should_ be fixed (as of late yesterday)
> > > >>>
> > > >>> - LegacyServerTest
> > > >>> - LegacyClientTest
> > > >>> - (StickyConnection|RoundRobin|Random)StrategyTest
> > > >>> - ReconnectDelayCaseInsensitiveTest
> > > >>> - ReconnectDelayListSelfTest
> > > >>> - ReconnectTest
> > > >>>
> > > >>> Its possible you didn't have my changes.
> > > >>>
> > > >>> I'm currently looking at these two:
> > > >>>
> > > >>> - XMLConfigurationTest
> > > >>> - XMLConfiguredConstraintValidatorTest
> > > >>>
> > > >>> I also get a failure
> > > >>> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I
> > > wrote,
> > > >>> so I'll take a quick look at that.
> > > >>>
> > > >>> Cheers
> > > >>>
> > > >>> Jon
> > > >>>
> > > >>> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
> > > >>> jlmonteiro@tomitribe.com> wrote:
> > > >>>
> > > >>>> I have been digging and running tests locally.
> > > >>>> Here is the list of tests failures I have extracted.
> > > >>>>
> > > >>>> - JMSInjectionTest
> > > >>>> - CDIInvokeSimpleGetOperationTest
> > > >>>> - CDIInvokeWithRegisteredProviderTest
> > > >>>> - FeatureRegistrationTest
> > > >>>> - InvokeWithJsonProviderTest
> > > >>>> - DuplicateConfigurationTest
> > > >>>> - XMLConfigurationTest
> > > >>>> - XMLConfiguredConstraintValidatorTest
> > > >>>> - MoviesArquillianHtmlUnitTest
> > > >>>> - DeployInWebAppsDirectoryTest
> > > >>>> - LegacyServerTest
> > > >>>> - LegacyClientTest
> > > >>>> - (StickyConnection|RoundRobin|Random)StrategyTest
> > > >>>> - ReconnectDelayCaseInsensitiveTest
> > > >>>> - ReconnectDelayListSelfTest
> > > >>>> - ReconnectTest
> > > >>>>
> > > >>>> Anything else I missed?
> > > >>>>
> > > >>>> --
> > > >>>> Jean-Louis Monteiro
> > > >>>> http://twitter.com/jlouismonteiro
> > > >>>> http://www.tomitribe.com
> > > >>>>
> > > >>>>
> > > >>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> > > >>>> jonathan.gallimore@gmail.com> wrote:
> > > >>>>
> > > >>>> > I've merged a few PRs in which appear to have kept the build in
> > the
> > > >>>> same
> > > >>>> > state. I also fixed up the itest failures. I'll work on bval
> > > >>>> tomorrow. I
> > > >>>> > get failures with the MicroProfile REST client locally, so if
> > > someone
> > > >>>> can
> > > >>>> > take a look at that, that would be great.
> > > >>>> >
> > > >>>> > Thanks
> > > >>>> >
> > > >>>> > Jon
> > > >>>> >
> > > >>>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
> > > >>>> <radcortez@yahoo.com.invalid
> > > >>>> > >
> > > >>>> > wrote:
> > > >>>> >
> > > >>>> > > Hi folks,
> > > >>>> > >
> > > >>>> > > It is great to see so many contributions and we hope to
> continue
> > > >>>> and even
> > > >>>> > > increase the traffic.
> > > >>>> > >
> > > >>>> > > Now, this also comes with a few challenges. Our build has been
> > red
> > > >>>> for a
> > > >>>> > > while and I would like to get it green again:
> > > >>>> > >
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> > > >>>> <
> > > >>>> > >
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> > > >>>> >
> > > >>>> > >
> > > >>>> > > The latest build has some checkstyle violations and test
> > failures:
> > > >>>> > >
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > > >>>> > > <
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > > >>>> > > >
> > > >>>> > >
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > > >>>> > > <
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > > >>>> > > >
> > > >>>> > >
> > > >>>> > > It would be great if someone could pick these issues and fix
> > them
> > > >>>> and we
> > > >>>> > > should prioritize any build fixing PR above everything else.
> > > >>>> > >
> > > >>>> > > Also, when someone sends a PR, your work doesn’t end when it
> > gets
> > > >>>> merged.
> > > >>>> > > Running a full build takes almost 5 hours, so the committer
> most
> > > of
> > > >>>> the
> > > >>>> > > times is not able to run the entire build to check your PR. I
> > > >>>> kindly ask
> > > >>>> > > you to monitor the tomee build bot here:
> > > >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> > > >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after
> > > your
> > > >>>> PR
> > > >>>> > > gets merged and if you uncover something wrong, please send a
> > > >>>> corrective
> > > >>>> > PR.
> > > >>>> > >
> > > >>>> > > I’ll be out the next couple of days, so I hope someone can
> pick
> > > >>>> this up
> > > >>>> > :)
> > > >>>> > >
> > > >>>> > > Cheers,
> > > >>>> > > Roberto
> > > >>>> >
> > > >>>>
> > > >>>
> > >
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
> >
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Thanks Dani.

That's right, and these two as well:

XMLConfigurationTest
- XMLConfiguredConstraintValidatorTest

On Fri, 7 Dec 2018, 18:20 Daniel Cunha <danielsoro@gmail.com wrote:

> Hey Jon,
>
> I can help with BVal tests.
> If I get it is the BVal test related DuplicateConfigurationTest right?
>
>
> Em sex, 7 de dez de 2018 às 14:03, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> escreveu:
>
> > Filed a ticket: https://issues.apache.org/jira/browse/TOMEE-2330. We
> could
> > ignore the test in the meantime.
> >
> > Jon
> >
> > On Fri, Dec 7, 2018 at 4:36 PM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> > > I committed a fix for CustomOrmXmlTest. The failure in CmpMappingsTest
> > > actually looks like a genuine error case that only affects
> > > Plume/EclipseLink. I'm digging in.
> > >
> > > Does someone want to take the BVal tests off me? Not required, but if
> > > someone is looking for something to do, I'm happy to hand those over, I
> > > haven't made any real progress with them.
> > >
> > > Jon
> > >
> > > On Fri, Dec 7, 2018 at 11:08 AM Jonathan Gallimore <
> > > jonathan.gallimore@gmail.com> wrote:
> > >
> > >> I see this also fails on
> > >> buildbot:
> > org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
> > >> its a simple fix which I'll commit now.
> > >>
> > >> Jon
> > >>
> > >> On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
> > >> jonathan.gallimore@gmail.com> wrote:
> > >>
> > >>> Hey Jean-Louis
> > >>>
> > >>> Thanks for the list!
> > >>>
> > >>> These ones _should_ be fixed (as of late yesterday)
> > >>>
> > >>> - LegacyServerTest
> > >>> - LegacyClientTest
> > >>> - (StickyConnection|RoundRobin|Random)StrategyTest
> > >>> - ReconnectDelayCaseInsensitiveTest
> > >>> - ReconnectDelayListSelfTest
> > >>> - ReconnectTest
> > >>>
> > >>> Its possible you didn't have my changes.
> > >>>
> > >>> I'm currently looking at these two:
> > >>>
> > >>> - XMLConfigurationTest
> > >>> - XMLConfiguredConstraintValidatorTest
> > >>>
> > >>> I also get a failure
> > >>> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I
> > wrote,
> > >>> so I'll take a quick look at that.
> > >>>
> > >>> Cheers
> > >>>
> > >>> Jon
> > >>>
> > >>> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
> > >>> jlmonteiro@tomitribe.com> wrote:
> > >>>
> > >>>> I have been digging and running tests locally.
> > >>>> Here is the list of tests failures I have extracted.
> > >>>>
> > >>>> - JMSInjectionTest
> > >>>> - CDIInvokeSimpleGetOperationTest
> > >>>> - CDIInvokeWithRegisteredProviderTest
> > >>>> - FeatureRegistrationTest
> > >>>> - InvokeWithJsonProviderTest
> > >>>> - DuplicateConfigurationTest
> > >>>> - XMLConfigurationTest
> > >>>> - XMLConfiguredConstraintValidatorTest
> > >>>> - MoviesArquillianHtmlUnitTest
> > >>>> - DeployInWebAppsDirectoryTest
> > >>>> - LegacyServerTest
> > >>>> - LegacyClientTest
> > >>>> - (StickyConnection|RoundRobin|Random)StrategyTest
> > >>>> - ReconnectDelayCaseInsensitiveTest
> > >>>> - ReconnectDelayListSelfTest
> > >>>> - ReconnectTest
> > >>>>
> > >>>> Anything else I missed?
> > >>>>
> > >>>> --
> > >>>> Jean-Louis Monteiro
> > >>>> http://twitter.com/jlouismonteiro
> > >>>> http://www.tomitribe.com
> > >>>>
> > >>>>
> > >>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> > >>>> jonathan.gallimore@gmail.com> wrote:
> > >>>>
> > >>>> > I've merged a few PRs in which appear to have kept the build in
> the
> > >>>> same
> > >>>> > state. I also fixed up the itest failures. I'll work on bval
> > >>>> tomorrow. I
> > >>>> > get failures with the MicroProfile REST client locally, so if
> > someone
> > >>>> can
> > >>>> > take a look at that, that would be great.
> > >>>> >
> > >>>> > Thanks
> > >>>> >
> > >>>> > Jon
> > >>>> >
> > >>>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
> > >>>> <radcortez@yahoo.com.invalid
> > >>>> > >
> > >>>> > wrote:
> > >>>> >
> > >>>> > > Hi folks,
> > >>>> > >
> > >>>> > > It is great to see so many contributions and we hope to continue
> > >>>> and even
> > >>>> > > increase the traffic.
> > >>>> > >
> > >>>> > > Now, this also comes with a few challenges. Our build has been
> red
> > >>>> for a
> > >>>> > > while and I would like to get it green again:
> > >>>> > >
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> > >>>> <
> > >>>> > >
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> > >>>> >
> > >>>> > >
> > >>>> > > The latest build has some checkstyle violations and test
> failures:
> > >>>> > >
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > >>>> > > <
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > >>>> > > >
> > >>>> > >
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > >>>> > > <
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > >>>> > > >
> > >>>> > >
> > >>>> > > It would be great if someone could pick these issues and fix
> them
> > >>>> and we
> > >>>> > > should prioritize any build fixing PR above everything else.
> > >>>> > >
> > >>>> > > Also, when someone sends a PR, your work doesn’t end when it
> gets
> > >>>> merged.
> > >>>> > > Running a full build takes almost 5 hours, so the committer most
> > of
> > >>>> the
> > >>>> > > times is not able to run the entire build to check your PR. I
> > >>>> kindly ask
> > >>>> > > you to monitor the tomee build bot here:
> > >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> > >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after
> > your
> > >>>> PR
> > >>>> > > gets merged and if you uncover something wrong, please send a
> > >>>> corrective
> > >>>> > PR.
> > >>>> > >
> > >>>> > > I’ll be out the next couple of days, so I hope someone can pick
> > >>>> this up
> > >>>> > :)
> > >>>> > >
> > >>>> > > Cheers,
> > >>>> > > Roberto
> > >>>> >
> > >>>>
> > >>>
> >
>
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>

Re: Stabilize TomEE Build

[Daniel Cunha <da...@gmail.com>]

Hey Jon,

I can help with BVal tests.
If I get it is the BVal test related DuplicateConfigurationTest right?


Em sex, 7 de dez de 2018 às 14:03, Jonathan Gallimore <
jonathan.gallimore@gmail.com> escreveu:

> Filed a ticket: https://issues.apache.org/jira/browse/TOMEE-2330. We could
> ignore the test in the meantime.
>
> Jon
>
> On Fri, Dec 7, 2018 at 4:36 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > I committed a fix for CustomOrmXmlTest. The failure in CmpMappingsTest
> > actually looks like a genuine error case that only affects
> > Plume/EclipseLink. I'm digging in.
> >
> > Does someone want to take the BVal tests off me? Not required, but if
> > someone is looking for something to do, I'm happy to hand those over, I
> > haven't made any real progress with them.
> >
> > Jon
> >
> > On Fri, Dec 7, 2018 at 11:08 AM Jonathan Gallimore <
> > jonathan.gallimore@gmail.com> wrote:
> >
> >> I see this also fails on
> >> buildbot:
> org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
> >> its a simple fix which I'll commit now.
> >>
> >> Jon
> >>
> >> On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
> >> jonathan.gallimore@gmail.com> wrote:
> >>
> >>> Hey Jean-Louis
> >>>
> >>> Thanks for the list!
> >>>
> >>> These ones _should_ be fixed (as of late yesterday)
> >>>
> >>> - LegacyServerTest
> >>> - LegacyClientTest
> >>> - (StickyConnection|RoundRobin|Random)StrategyTest
> >>> - ReconnectDelayCaseInsensitiveTest
> >>> - ReconnectDelayListSelfTest
> >>> - ReconnectTest
> >>>
> >>> Its possible you didn't have my changes.
> >>>
> >>> I'm currently looking at these two:
> >>>
> >>> - XMLConfigurationTest
> >>> - XMLConfiguredConstraintValidatorTest
> >>>
> >>> I also get a failure
> >>> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I
> wrote,
> >>> so I'll take a quick look at that.
> >>>
> >>> Cheers
> >>>
> >>> Jon
> >>>
> >>> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
> >>> jlmonteiro@tomitribe.com> wrote:
> >>>
> >>>> I have been digging and running tests locally.
> >>>> Here is the list of tests failures I have extracted.
> >>>>
> >>>> - JMSInjectionTest
> >>>> - CDIInvokeSimpleGetOperationTest
> >>>> - CDIInvokeWithRegisteredProviderTest
> >>>> - FeatureRegistrationTest
> >>>> - InvokeWithJsonProviderTest
> >>>> - DuplicateConfigurationTest
> >>>> - XMLConfigurationTest
> >>>> - XMLConfiguredConstraintValidatorTest
> >>>> - MoviesArquillianHtmlUnitTest
> >>>> - DeployInWebAppsDirectoryTest
> >>>> - LegacyServerTest
> >>>> - LegacyClientTest
> >>>> - (StickyConnection|RoundRobin|Random)StrategyTest
> >>>> - ReconnectDelayCaseInsensitiveTest
> >>>> - ReconnectDelayListSelfTest
> >>>> - ReconnectTest
> >>>>
> >>>> Anything else I missed?
> >>>>
> >>>> --
> >>>> Jean-Louis Monteiro
> >>>> http://twitter.com/jlouismonteiro
> >>>> http://www.tomitribe.com
> >>>>
> >>>>
> >>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> >>>> jonathan.gallimore@gmail.com> wrote:
> >>>>
> >>>> > I've merged a few PRs in which appear to have kept the build in the
> >>>> same
> >>>> > state. I also fixed up the itest failures. I'll work on bval
> >>>> tomorrow. I
> >>>> > get failures with the MicroProfile REST client locally, so if
> someone
> >>>> can
> >>>> > take a look at that, that would be great.
> >>>> >
> >>>> > Thanks
> >>>> >
> >>>> > Jon
> >>>> >
> >>>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
> >>>> <radcortez@yahoo.com.invalid
> >>>> > >
> >>>> > wrote:
> >>>> >
> >>>> > > Hi folks,
> >>>> > >
> >>>> > > It is great to see so many contributions and we hope to continue
> >>>> and even
> >>>> > > increase the traffic.
> >>>> > >
> >>>> > > Now, this also comes with a few challenges. Our build has been red
> >>>> for a
> >>>> > > while and I would like to get it green again:
> >>>> > >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> >>>> <
> >>>> > >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
> >>>> >
> >>>> > >
> >>>> > > The latest build has some checkstyle violations and test failures:
> >>>> > >
> >>>> > >
> >>>> >
> >>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >>>> > > <
> >>>> > >
> >>>> >
> >>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >>>> > > >
> >>>> > >
> >>>> > >
> >>>> >
> >>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> >>>> > > <
> >>>> > >
> >>>> >
> >>>>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> >>>> > > >
> >>>> > >
> >>>> > > It would be great if someone could pick these issues and fix them
> >>>> and we
> >>>> > > should prioritize any build fixing PR above everything else.
> >>>> > >
> >>>> > > Also, when someone sends a PR, your work doesn’t end when it gets
> >>>> merged.
> >>>> > > Running a full build takes almost 5 hours, so the committer most
> of
> >>>> the
> >>>> > > times is not able to run the entire build to check your PR. I
> >>>> kindly ask
> >>>> > > you to monitor the tomee build bot here:
> >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> >>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after
> your
> >>>> PR
> >>>> > > gets merged and if you uncover something wrong, please send a
> >>>> corrective
> >>>> > PR.
> >>>> > >
> >>>> > > I’ll be out the next couple of days, so I hope someone can pick
> >>>> this up
> >>>> > :)
> >>>> > >
> >>>> > > Cheers,
> >>>> > > Roberto
> >>>> >
> >>>>
> >>>
>


-- 
Daniel "soro" Cunha
https://twitter.com/dvlc_

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Filed a ticket: https://issues.apache.org/jira/browse/TOMEE-2330. We could
ignore the test in the meantime.

Jon

On Fri, Dec 7, 2018 at 4:36 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I committed a fix for CustomOrmXmlTest. The failure in CmpMappingsTest
> actually looks like a genuine error case that only affects
> Plume/EclipseLink. I'm digging in.
>
> Does someone want to take the BVal tests off me? Not required, but if
> someone is looking for something to do, I'm happy to hand those over, I
> haven't made any real progress with them.
>
> Jon
>
> On Fri, Dec 7, 2018 at 11:08 AM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> I see this also fails on
>> buildbot: org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
>> its a simple fix which I'll commit now.
>>
>> Jon
>>
>> On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>>
>>> Hey Jean-Louis
>>>
>>> Thanks for the list!
>>>
>>> These ones _should_ be fixed (as of late yesterday)
>>>
>>> - LegacyServerTest
>>> - LegacyClientTest
>>> - (StickyConnection|RoundRobin|Random)StrategyTest
>>> - ReconnectDelayCaseInsensitiveTest
>>> - ReconnectDelayListSelfTest
>>> - ReconnectTest
>>>
>>> Its possible you didn't have my changes.
>>>
>>> I'm currently looking at these two:
>>>
>>> - XMLConfigurationTest
>>> - XMLConfiguredConstraintValidatorTest
>>>
>>> I also get a failure
>>> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I wrote,
>>> so I'll take a quick look at that.
>>>
>>> Cheers
>>>
>>> Jon
>>>
>>> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
>>> jlmonteiro@tomitribe.com> wrote:
>>>
>>>> I have been digging and running tests locally.
>>>> Here is the list of tests failures I have extracted.
>>>>
>>>> - JMSInjectionTest
>>>> - CDIInvokeSimpleGetOperationTest
>>>> - CDIInvokeWithRegisteredProviderTest
>>>> - FeatureRegistrationTest
>>>> - InvokeWithJsonProviderTest
>>>> - DuplicateConfigurationTest
>>>> - XMLConfigurationTest
>>>> - XMLConfiguredConstraintValidatorTest
>>>> - MoviesArquillianHtmlUnitTest
>>>> - DeployInWebAppsDirectoryTest
>>>> - LegacyServerTest
>>>> - LegacyClientTest
>>>> - (StickyConnection|RoundRobin|Random)StrategyTest
>>>> - ReconnectDelayCaseInsensitiveTest
>>>> - ReconnectDelayListSelfTest
>>>> - ReconnectTest
>>>>
>>>> Anything else I missed?
>>>>
>>>> --
>>>> Jean-Louis Monteiro
>>>> http://twitter.com/jlouismonteiro
>>>> http://www.tomitribe.com
>>>>
>>>>
>>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>>>> jonathan.gallimore@gmail.com> wrote:
>>>>
>>>> > I've merged a few PRs in which appear to have kept the build in the
>>>> same
>>>> > state. I also fixed up the itest failures. I'll work on bval
>>>> tomorrow. I
>>>> > get failures with the MicroProfile REST client locally, so if someone
>>>> can
>>>> > take a look at that, that would be great.
>>>> >
>>>> > Thanks
>>>> >
>>>> > Jon
>>>> >
>>>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>>>> <radcortez@yahoo.com.invalid
>>>> > >
>>>> > wrote:
>>>> >
>>>> > > Hi folks,
>>>> > >
>>>> > > It is great to see so many contributions and we hope to continue
>>>> and even
>>>> > > increase the traffic.
>>>> > >
>>>> > > Now, this also comes with a few challenges. Our build has been red
>>>> for a
>>>> > > while and I would like to get it green again:
>>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
>>>> <
>>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
>>>> >
>>>> > >
>>>> > > The latest build has some checkstyle violations and test failures:
>>>> > >
>>>> > >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>> > > <
>>>> > >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>>> > > >
>>>> > >
>>>> > >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>> > > <
>>>> > >
>>>> >
>>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>>> > > >
>>>> > >
>>>> > > It would be great if someone could pick these issues and fix them
>>>> and we
>>>> > > should prioritize any build fixing PR above everything else.
>>>> > >
>>>> > > Also, when someone sends a PR, your work doesn’t end when it gets
>>>> merged.
>>>> > > Running a full build takes almost 5 hours, so the committer most of
>>>> the
>>>> > > times is not able to run the entire build to check your PR. I
>>>> kindly ask
>>>> > > you to monitor the tomee build bot here:
>>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your
>>>> PR
>>>> > > gets merged and if you uncover something wrong, please send a
>>>> corrective
>>>> > PR.
>>>> > >
>>>> > > I’ll be out the next couple of days, so I hope someone can pick
>>>> this up
>>>> > :)
>>>> > >
>>>> > > Cheers,
>>>> > > Roberto
>>>> >
>>>>
>>>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I committed a fix for CustomOrmXmlTest. The failure in CmpMappingsTest
actually looks like a genuine error case that only affects
Plume/EclipseLink. I'm digging in.

Does someone want to take the BVal tests off me? Not required, but if
someone is looking for something to do, I'm happy to hand those over, I
haven't made any real progress with them.

Jon

On Fri, Dec 7, 2018 at 11:08 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I see this also fails on
> buildbot: org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
> its a simple fix which I'll commit now.
>
> Jon
>
> On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> Hey Jean-Louis
>>
>> Thanks for the list!
>>
>> These ones _should_ be fixed (as of late yesterday)
>>
>> - LegacyServerTest
>> - LegacyClientTest
>> - (StickyConnection|RoundRobin|Random)StrategyTest
>> - ReconnectDelayCaseInsensitiveTest
>> - ReconnectDelayListSelfTest
>> - ReconnectTest
>>
>> Its possible you didn't have my changes.
>>
>> I'm currently looking at these two:
>>
>> - XMLConfigurationTest
>> - XMLConfiguredConstraintValidatorTest
>>
>> I also get a failure
>> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I wrote,
>> so I'll take a quick look at that.
>>
>> Cheers
>>
>> Jon
>>
>> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> I have been digging and running tests locally.
>>> Here is the list of tests failures I have extracted.
>>>
>>> - JMSInjectionTest
>>> - CDIInvokeSimpleGetOperationTest
>>> - CDIInvokeWithRegisteredProviderTest
>>> - FeatureRegistrationTest
>>> - InvokeWithJsonProviderTest
>>> - DuplicateConfigurationTest
>>> - XMLConfigurationTest
>>> - XMLConfiguredConstraintValidatorTest
>>> - MoviesArquillianHtmlUnitTest
>>> - DeployInWebAppsDirectoryTest
>>> - LegacyServerTest
>>> - LegacyClientTest
>>> - (StickyConnection|RoundRobin|Random)StrategyTest
>>> - ReconnectDelayCaseInsensitiveTest
>>> - ReconnectDelayListSelfTest
>>> - ReconnectTest
>>>
>>> Anything else I missed?
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>>> jonathan.gallimore@gmail.com> wrote:
>>>
>>> > I've merged a few PRs in which appear to have kept the build in the
>>> same
>>> > state. I also fixed up the itest failures. I'll work on bval tomorrow.
>>> I
>>> > get failures with the MicroProfile REST client locally, so if someone
>>> can
>>> > take a look at that, that would be great.
>>> >
>>> > Thanks
>>> >
>>> > Jon
>>> >
>>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>>> <radcortez@yahoo.com.invalid
>>> > >
>>> > wrote:
>>> >
>>> > > Hi folks,
>>> > >
>>> > > It is great to see so many contributions and we hope to continue and
>>> even
>>> > > increase the traffic.
>>> > >
>>> > > Now, this also comes with a few challenges. Our build has been red
>>> for a
>>> > > while and I would like to get it green again:
>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35
>>> <
>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>>> > >
>>> > > The latest build has some checkstyle violations and test failures:
>>> > >
>>> > >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>> > > <
>>> > >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>>> > > >
>>> > >
>>> > >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>> > > <
>>> > >
>>> >
>>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>>> > > >
>>> > >
>>> > > It would be great if someone could pick these issues and fix them
>>> and we
>>> > > should prioritize any build fixing PR above everything else.
>>> > >
>>> > > Also, when someone sends a PR, your work doesn’t end when it gets
>>> merged.
>>> > > Running a full build takes almost 5 hours, so the committer most of
>>> the
>>> > > times is not able to run the entire build to check your PR. I kindly
>>> ask
>>> > > you to monitor the tomee build bot here:
>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your
>>> PR
>>> > > gets merged and if you uncover something wrong, please send a
>>> corrective
>>> > PR.
>>> > >
>>> > > I’ll be out the next couple of days, so I hope someone can pick this
>>> up
>>> > :)
>>> > >
>>> > > Cheers,
>>> > > Roberto
>>> >
>>>
>>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I see this also fails on
buildbot: org.apache.openejb.arquillian.tests.cmp.sample.CustomOrmXmlTest -
its a simple fix which I'll commit now.

Jon

On Fri, Dec 7, 2018 at 11:05 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> Hey Jean-Louis
>
> Thanks for the list!
>
> These ones _should_ be fixed (as of late yesterday)
>
> - LegacyServerTest
> - LegacyClientTest
> - (StickyConnection|RoundRobin|Random)StrategyTest
> - ReconnectDelayCaseInsensitiveTest
> - ReconnectDelayListSelfTest
> - ReconnectTest
>
> Its possible you didn't have my changes.
>
> I'm currently looking at these two:
>
> - XMLConfigurationTest
> - XMLConfiguredConstraintValidatorTest
>
> I also get a failure
> in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I wrote,
> so I'll take a quick look at that.
>
> Cheers
>
> Jon
>
> On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
>> I have been digging and running tests locally.
>> Here is the list of tests failures I have extracted.
>>
>> - JMSInjectionTest
>> - CDIInvokeSimpleGetOperationTest
>> - CDIInvokeWithRegisteredProviderTest
>> - FeatureRegistrationTest
>> - InvokeWithJsonProviderTest
>> - DuplicateConfigurationTest
>> - XMLConfigurationTest
>> - XMLConfiguredConstraintValidatorTest
>> - MoviesArquillianHtmlUnitTest
>> - DeployInWebAppsDirectoryTest
>> - LegacyServerTest
>> - LegacyClientTest
>> - (StickyConnection|RoundRobin|Random)StrategyTest
>> - ReconnectDelayCaseInsensitiveTest
>> - ReconnectDelayListSelfTest
>> - ReconnectTest
>>
>> Anything else I missed?
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
>> jonathan.gallimore@gmail.com> wrote:
>>
>> > I've merged a few PRs in which appear to have kept the build in the same
>> > state. I also fixed up the itest failures. I'll work on bval tomorrow. I
>> > get failures with the MicroProfile REST client locally, so if someone
>> can
>> > take a look at that, that would be great.
>> >
>> > Thanks
>> >
>> > Jon
>> >
>> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
>> <radcortez@yahoo.com.invalid
>> > >
>> > wrote:
>> >
>> > > Hi folks,
>> > >
>> > > It is great to see so many contributions and we hope to continue and
>> even
>> > > increase the traffic.
>> > >
>> > > Now, this also comes with a few challenges. Our build has been red
>> for a
>> > > while and I would like to get it green again:
>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>> > >
>> > > The latest build has some checkstyle violations and test failures:
>> > >
>> > >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > > <
>> > >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
>> > > >
>> > >
>> > >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>> > > <
>> > >
>> >
>> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
>> > > >
>> > >
>> > > It would be great if someone could pick these issues and fix them and
>> we
>> > > should prioritize any build fixing PR above everything else.
>> > >
>> > > Also, when someone sends a PR, your work doesn’t end when it gets
>> merged.
>> > > Running a full build takes almost 5 hours, so the committer most of
>> the
>> > > times is not able to run the entire build to check your PR. I kindly
>> ask
>> > > you to monitor the tomee build bot here:
>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
>> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
>> > > gets merged and if you uncover something wrong, please send a
>> corrective
>> > PR.
>> > >
>> > > I’ll be out the next couple of days, so I hope someone can pick this
>> up
>> > :)
>> > >
>> > > Cheers,
>> > > Roberto
>> >
>>
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

Hey Jean-Louis

Thanks for the list!

These ones _should_ be fixed (as of late yesterday)

- LegacyServerTest
- LegacyClientTest
- (StickyConnection|RoundRobin|Random)StrategyTest
- ReconnectDelayCaseInsensitiveTest
- ReconnectDelayListSelfTest
- ReconnectTest

Its possible you didn't have my changes.

I'm currently looking at these two:

- XMLConfigurationTest
- XMLConfiguredConstraintValidatorTest

I also get a failure
in  org.apache.openejb.arquillian.tests.cmp.CmpMappingTest, which I wrote,
so I'll take a quick look at that.

Cheers

Jon

On Fri, Dec 7, 2018 at 10:59 AM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:

> I have been digging and running tests locally.
> Here is the list of tests failures I have extracted.
>
> - JMSInjectionTest
> - CDIInvokeSimpleGetOperationTest
> - CDIInvokeWithRegisteredProviderTest
> - FeatureRegistrationTest
> - InvokeWithJsonProviderTest
> - DuplicateConfigurationTest
> - XMLConfigurationTest
> - XMLConfiguredConstraintValidatorTest
> - MoviesArquillianHtmlUnitTest
> - DeployInWebAppsDirectoryTest
> - LegacyServerTest
> - LegacyClientTest
> - (StickyConnection|RoundRobin|Random)StrategyTest
> - ReconnectDelayCaseInsensitiveTest
> - ReconnectDelayListSelfTest
> - ReconnectTest
>
> Anything else I missed?
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
> > I've merged a few PRs in which appear to have kept the build in the same
> > state. I also fixed up the itest failures. I'll work on bval tomorrow. I
> > get failures with the MicroProfile REST client locally, so if someone can
> > take a look at that, that would be great.
> >
> > Thanks
> >
> > Jon
> >
> > On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez
> <radcortez@yahoo.com.invalid
> > >
> > wrote:
> >
> > > Hi folks,
> > >
> > > It is great to see so many contributions and we hope to continue and
> even
> > > increase the traffic.
> > >
> > > Now, this also comes with a few challenges. Our build has been red for
> a
> > > while and I would like to get it green again:
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
> > >
> > > The latest build has some checkstyle violations and test failures:
> > >
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > > <
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > > >
> > >
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > > <
> > >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > > >
> > >
> > > It would be great if someone could pick these issues and fix them and
> we
> > > should prioritize any build fixing PR above everything else.
> > >
> > > Also, when someone sends a PR, your work doesn’t end when it gets
> merged.
> > > Running a full build takes almost 5 hours, so the committer most of the
> > > times is not able to run the entire build to check your PR. I kindly
> ask
> > > you to monitor the tomee build bot here:
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> > > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
> > > gets merged and if you uncover something wrong, please send a
> corrective
> > PR.
> > >
> > > I’ll be out the next couple of days, so I hope someone can pick this up
> > :)
> > >
> > > Cheers,
> > > Roberto
> >
>

Re: Stabilize TomEE Build

[Jean-Louis Monteiro <jl...@tomitribe.com>]

I have been digging and running tests locally.
Here is the list of tests failures I have extracted.

- JMSInjectionTest
- CDIInvokeSimpleGetOperationTest
- CDIInvokeWithRegisteredProviderTest
- FeatureRegistrationTest
- InvokeWithJsonProviderTest
- DuplicateConfigurationTest
- XMLConfigurationTest
- XMLConfiguredConstraintValidatorTest
- MoviesArquillianHtmlUnitTest
- DeployInWebAppsDirectoryTest
- LegacyServerTest
- LegacyClientTest
- (StickyConnection|RoundRobin|Random)StrategyTest
- ReconnectDelayCaseInsensitiveTest
- ReconnectDelayListSelfTest
- ReconnectTest

Anything else I missed?

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Thu, Dec 6, 2018 at 11:43 PM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:

> I've merged a few PRs in which appear to have kept the build in the same
> state. I also fixed up the itest failures. I'll work on bval tomorrow. I
> get failures with the MicroProfile REST client locally, so if someone can
> take a look at that, that would be great.
>
> Thanks
>
> Jon
>
> On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez <radcortez@yahoo.com.invalid
> >
> wrote:
>
> > Hi folks,
> >
> > It is great to see so many contributions and we hope to continue and even
> > increase the traffic.
> >
> > Now, this also comes with a few challenges. Our build has been red for a
> > while and I would like to get it green again:
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
> >
> > The latest build has some checkstyle violations and test failures:
> >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > <
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> > >
> >
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > <
> >
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> > >
> >
> > It would be great if someone could pick these issues and fix them and we
> > should prioritize any build fixing PR above everything else.
> >
> > Also, when someone sends a PR, your work doesn’t end when it gets merged.
> > Running a full build takes almost 5 hours, so the committer most of the
> > times is not able to run the entire build to check your PR. I kindly ask
> > you to monitor the tomee build bot here:
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
> > gets merged and if you uncover something wrong, please send a corrective
> PR.
> >
> > I’ll be out the next couple of days, so I hope someone can pick this up
> :)
> >
> > Cheers,
> > Roberto
>

Re: Stabilize TomEE Build

[Jonathan Gallimore <jo...@gmail.com>]

I've merged a few PRs in which appear to have kept the build in the same
state. I also fixed up the itest failures. I'll work on bval tomorrow. I
get failures with the MicroProfile REST client locally, so if someone can
take a look at that, that would be great.

Thanks

Jon

On Tue, Dec 4, 2018 at 10:25 PM Roberto Cortez <ra...@yahoo.com.invalid>
wrote:

> Hi folks,
>
> It is great to see so many contributions and we hope to continue and even
> increase the traffic.
>
> Now, this also comes with a few challenges. Our build has been red for a
> while and I would like to get it green again:
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35 <
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8?numbuilds=35>
>
> The latest build has some checkstyle violations and test failures:
>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> <
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/check-formatting/logs/stdio
> >
>
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> <
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/904/steps/test/logs/stdio
> >
>
> It would be great if someone could pick these issues and fix them and we
> should prioritize any build fixing PR above everything else.
>
> Also, when someone sends a PR, your work doesn’t end when it gets merged.
> Running a full build takes almost 5 hours, so the committer most of the
> times is not able to run the entire build to check your PR. I kindly ask
> you to monitor the tomee build bot here:
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 <
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8> after your PR
> gets merged and if you uncover something wrong, please send a corrective PR.
>
> I’ll be out the next couple of days, so I hope someone can pick this up :)
>
> Cheers,
> Roberto