Re: Remaining test failures
I know you worked on it and as I mentioned there is quite a significant
learning curve in that area. If you want to trade. I'm more than happy with
it.
There is the timeout issue and the interceptor issue to look at in order to
be passing everything and be green everywhere.
Only thing that I can probably also help is the OpenTracing support[
helping Zlotan out.
Le mer. 19 oct. 2022, 20:57, David Blevins a
écrit :
> > On Oct 19, 2022, at 3:38 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > The build is now fully green. All jobs green from quick to full with
> > examples, TCK, itests, and arquillian.
>
> That is truly amazing!! Really needed that good news :)
>
> > 12 remaining platform TCK now, 1 interceptor issue on EJB, 9 JAXRS issues
> > and 2 WebSocket timeout issues.
> >
> > Trying to put my head into JAXRS again. Last time I wasn't successful in
> > understanding all the stack, the specification and CXF. Hopefully my
> brain
> > is in a better shape.
>
> If you want to toss me the JAX-RS issues and focus on the others, I'm
> happy to trade. My MP JWT work is done, the build is now passing,
> conversation with infra on build resources is started, so I'm free and
> looking for the next thing.
>
>
> -David
>
> >
> > On Tue, Oct 18, 2022 at 10:33 PM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> >> Everything is green but the full build with the following
> >>
> >>> [INFO] *--- maven-failsafe-plugin:2.20:integration-test (default) @
> apache-tomee ---
> >>> *[WARNING] file.encoding cannot be set as system property, use
> -Dfile.encoding=... instead[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]
> >>>
> >>> Uses a password cipher implementation to encrypt/decrypt a value.
> >>> -c,--cipherSpecifies 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:
> 3.959 s - in org.apache.tomee.TomEECliIT
> >>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
> >>> Oct 18, 2022 1:58:53 PM org.apache.openejb.client.EventLogger log
> >>> INFO: RemoteInitialContextCreated{providerUri=
> http://localhost:33621/tomee/ejb}[ERROR] Tests run: 1, Failures: 0,
> Errors: 1, Skipped: 0, Time elapsed: 300.028 s <<< FAILURE! - in
> org.apache.tomee.RemoteTomEEEJBContainerIT[ERROR]
> run(org.apache.tomee.RemoteTomEEEJBContainerIT) Time elapsed: 300.028 s
> <<< ERROR!org.junit.runners.model.TestTimedOutException: test timed out
> after 30 milliseconds
> >>> at
> app//org.apache.tomee.RemoteTomEEEJBContainerIT.run(RemoteTomEEEJBContainerIT.java:96)
> >>>
> >>>
> >> I stopped it and triggered a new one to see. Not sure why this one would
> >> start to get stuck.
> >>
> >>
> >>
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Tue, Oct 18, 2022 at 7:55 PM David Blevins
> >> wrote:
> >>
> >>> Yep. Also going to ignore for now -- looks like my YourKit license is
> >>> expired.
> >>>
> >>> Not sure why MyFaces took 105 seconds to do its thing. Really looking
> >>> forward to creating a TomEE 10 dist that has no front-end tech like
> JSF,
> >>> JSTL, JSP, etc. Should start up way faster.
> >>>
> >>>
> >>> --
> >>> David Blevins
> >>> http://twitter.com/dblevins
> >>> http://www.tomitribe.com
> >>>
> On Oct 18, 2022, at 7:40 AM, Jean-Louis Monteiro <
> >>> jlmonte...@tomitribe.com> wrote:
>
> Yes I came to the same conclusion when I look at the logs even though
> I
> >>> did
> not open MyFaces or even try to understand.
> I remembered you saying it was 12 years old machines, so I was like,
> >>> let's
> be ok with it and increase the timeout a bit to wait until the server
> starts.
>
> As a quick and dirty fix it should work. We have other fixes to apply,
> >>> but
> we need 9 to be final and released. We can address more issues and do
> >>> more
> cleanup in 10 when catching up with Jakarta EE 10
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 4:36 PM David Blevins <
> david.blev...@gmail.com>
> wrote:
>
> > Thanks, Jean-Louis.
> >
> > I was just picking through the log output of one of the startup times
> >>> that
> > went over 1 minute. The only gap in log output is here, during the
> >>> MyF
Re: Remaining test failures
> On Oct 19, 2022, at 3:38 AM, Jean-Louis Monteiro
> wrote:
>
> The build is now fully green. All jobs green from quick to full with
> examples, TCK, itests, and arquillian.
That is truly amazing!! Really needed that good news :)
> 12 remaining platform TCK now, 1 interceptor issue on EJB, 9 JAXRS issues
> and 2 WebSocket timeout issues.
>
> Trying to put my head into JAXRS again. Last time I wasn't successful in
> understanding all the stack, the specification and CXF. Hopefully my brain
> is in a better shape.
If you want to toss me the JAX-RS issues and focus on the others, I'm happy to
trade. My MP JWT work is done, the build is now passing, conversation with
infra on build resources is started, so I'm free and looking for the next thing.
-David
>
> On Tue, Oct 18, 2022 at 10:33 PM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
>> Everything is green but the full build with the following
>>
>>> [INFO] *--- maven-failsafe-plugin:2.20:integration-test (default) @
>>> apache-tomee ---
>>> *[WARNING] file.encoding cannot be set as system property, use
>>> -Dfile.encoding=... instead[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]
>>>
>>> Uses a password cipher implementation to encrypt/decrypt a value.
>>> -c,--cipherSpecifies 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:
>>> 3.959 s - in org.apache.tomee.TomEECliIT
>>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
>>> Oct 18, 2022 1:58:53 PM org.apache.openejb.client.EventLogger log
>>> INFO:
>>> RemoteInitialContextCreated{providerUri=http://localhost:33621/tomee/ejb}[ERROR]
>>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 300.028 s
>>> <<< FAILURE! - in org.apache.tomee.RemoteTomEEEJBContainerIT[ERROR]
>>> run(org.apache.tomee.RemoteTomEEEJBContainerIT) Time elapsed: 300.028 s
>>> <<< ERROR!org.junit.runners.model.TestTimedOutException: test timed out
>>> after 30 milliseconds
>>> at
>>> app//org.apache.tomee.RemoteTomEEEJBContainerIT.run(RemoteTomEEEJBContainerIT.java:96)
>>>
>>>
>> I stopped it and triggered a new one to see. Not sure why this one would
>> start to get stuck.
>>
>>
>>
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Tue, Oct 18, 2022 at 7:55 PM David Blevins
>> wrote:
>>
>>> Yep. Also going to ignore for now -- looks like my YourKit license is
>>> expired.
>>>
>>> Not sure why MyFaces took 105 seconds to do its thing. Really looking
>>> forward to creating a TomEE 10 dist that has no front-end tech like JSF,
>>> JSTL, JSP, etc. Should start up way faster.
>>>
>>>
>>> --
>>> David Blevins
>>> http://twitter.com/dblevins
>>> http://www.tomitribe.com
>>>
On Oct 18, 2022, at 7:40 AM, Jean-Louis Monteiro <
>>> jlmonte...@tomitribe.com> wrote:
Yes I came to the same conclusion when I look at the logs even though I
>>> did
not open MyFaces or even try to understand.
I remembered you saying it was 12 years old machines, so I was like,
>>> let's
be ok with it and increase the timeout a bit to wait until the server
starts.
As a quick and dirty fix it should work. We have other fixes to apply,
>>> but
we need 9 to be final and released. We can address more issues and do
>>> more
cleanup in 10 when catching up with Jakarta EE 10
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 4:36 PM David Blevins
wrote:
> Thanks, Jean-Louis.
>
> I was just picking through the log output of one of the startup times
>>> that
> went over 1 minute. The only gap in log output is here, during the
>>> MyFaces
> startup.
>
> -
>
>>> https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
>
> That accounts for basically 45 seconds of the startup. I've got
>>> MyFaces
> code up and am digging through to see what I can find.
>
> The longer timeout should work to fix the test, just curious what the
>>> heck
> could take so long!
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>> On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com>
Re: Remaining test failures
The build is now fully green. All jobs green from quick to full with
examples, TCK, itests, and arquillian.
12 remaining platform TCK now, 1 interceptor issue on EJB, 9 JAXRS issues
and 2 WebSocket timeout issues.
Trying to put my head into JAXRS again. Last time I wasn't successful in
understanding all the stack, the specification and CXF. Hopefully my brain
is in a better shape.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 10:33 PM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> Everything is green but the full build with the following
>
>> [INFO] *--- maven-failsafe-plugin:2.20:integration-test (default) @
>> apache-tomee ---
>> *[WARNING] file.encoding cannot be set as system property, use
>> -Dfile.encoding=... instead[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]
>>
>> Uses a password cipher implementation to encrypt/decrypt a value.
>> -c,--cipherSpecifies 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: 3.959
>> s - in org.apache.tomee.TomEECliIT
>> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
>> Oct 18, 2022 1:58:53 PM org.apache.openejb.client.EventLogger log
>> INFO:
>> RemoteInitialContextCreated{providerUri=http://localhost:33621/tomee/ejb}[ERROR]
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 300.028 s
>> <<< FAILURE! - in org.apache.tomee.RemoteTomEEEJBContainerIT[ERROR]
>> run(org.apache.tomee.RemoteTomEEEJBContainerIT) Time elapsed: 300.028 s
>> <<< ERROR!org.junit.runners.model.TestTimedOutException: test timed out
>> after 30 milliseconds
>> at
>> app//org.apache.tomee.RemoteTomEEEJBContainerIT.run(RemoteTomEEEJBContainerIT.java:96)
>>
>>
> I stopped it and triggered a new one to see. Not sure why this one would
> start to get stuck.
>
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 7:55 PM David Blevins
> wrote:
>
>> Yep. Also going to ignore for now -- looks like my YourKit license is
>> expired.
>>
>> Not sure why MyFaces took 105 seconds to do its thing. Really looking
>> forward to creating a TomEE 10 dist that has no front-end tech like JSF,
>> JSTL, JSP, etc. Should start up way faster.
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>> > On Oct 18, 2022, at 7:40 AM, Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>> >
>> > Yes I came to the same conclusion when I look at the logs even though I
>> did
>> > not open MyFaces or even try to understand.
>> > I remembered you saying it was 12 years old machines, so I was like,
>> let's
>> > be ok with it and increase the timeout a bit to wait until the server
>> > starts.
>> >
>> > As a quick and dirty fix it should work. We have other fixes to apply,
>> but
>> > we need 9 to be final and released. We can address more issues and do
>> more
>> > cleanup in 10 when catching up with Jakarta EE 10
>> > --
>> > Jean-Louis Monteiro
>> > http://twitter.com/jlouismonteiro
>> > http://www.tomitribe.com
>> >
>> >
>> > On Tue, Oct 18, 2022 at 4:36 PM David Blevins
>> > wrote:
>> >
>> >> Thanks, Jean-Louis.
>> >>
>> >> I was just picking through the log output of one of the startup times
>> that
>> >> went over 1 minute. The only gap in log output is here, during the
>> MyFaces
>> >> startup.
>> >>
>> >> -
>> >>
>> https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
>> >>
>> >> That accounts for basically 45 seconds of the startup. I've got
>> MyFaces
>> >> code up and am digging through to see what I can find.
>> >>
>> >> The longer timeout should work to fix the test, just curious what the
>> heck
>> >> could take so long!
>> >>
>> >>
>> >> --
>> >> David Blevins
>> >> http://twitter.com/dblevins
>> >> http://www.tomitribe.com
>> >>
>> >>> On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro <
>> >> jlmonte...@tomitribe.com> wrote:
>> >>>
>> >>> Quick and deploy full green
>> >>> arquillian green
>> >>> examples green
>> >>> tck green
>> >>>
>> >>> just pushed a fix for itests which is the last failure
>> >>> --
>> >>> Jean-Louis Monteiro
>> >>> http://twitter.com/jlouismonteiro
>> >>> http://www.tomitribe.com
>> >>>
>> >>>
>> >>> On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
>> >>> jlmonte...@tomitribe.com> wrote:
>>
Re: Remaining test failures
Everything is green but the full build with the following
> [INFO] *--- maven-failsafe-plugin:2.20:integration-test (default) @
> apache-tomee ---
> *[WARNING] file.encoding cannot be set as system property, use
> -Dfile.encoding=... instead[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]
>
> Uses a password cipher implementation to encrypt/decrypt a value.
> -c,--cipherSpecifies 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: 3.959
> s - in org.apache.tomee.TomEECliIT
> [INFO] Running org.apache.tomee.RemoteTomEEEJBContainerIT
> Oct 18, 2022 1:58:53 PM org.apache.openejb.client.EventLogger log
> INFO:
> RemoteInitialContextCreated{providerUri=http://localhost:33621/tomee/ejb}[ERROR]
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 300.028 s
> <<< FAILURE! - in org.apache.tomee.RemoteTomEEEJBContainerIT[ERROR]
> run(org.apache.tomee.RemoteTomEEEJBContainerIT) Time elapsed: 300.028 s <<<
> ERROR!org.junit.runners.model.TestTimedOutException: test timed out after
> 30 milliseconds
> at
> app//org.apache.tomee.RemoteTomEEEJBContainerIT.run(RemoteTomEEEJBContainerIT.java:96)
>
>
I stopped it and triggered a new one to see. Not sure why this one would
start to get stuck.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 7:55 PM David Blevins
wrote:
> Yep. Also going to ignore for now -- looks like my YourKit license is
> expired.
>
> Not sure why MyFaces took 105 seconds to do its thing. Really looking
> forward to creating a TomEE 10 dist that has no front-end tech like JSF,
> JSTL, JSP, etc. Should start up way faster.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Oct 18, 2022, at 7:40 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > Yes I came to the same conclusion when I look at the logs even though I
> did
> > not open MyFaces or even try to understand.
> > I remembered you saying it was 12 years old machines, so I was like,
> let's
> > be ok with it and increase the timeout a bit to wait until the server
> > starts.
> >
> > As a quick and dirty fix it should work. We have other fixes to apply,
> but
> > we need 9 to be final and released. We can address more issues and do
> more
> > cleanup in 10 when catching up with Jakarta EE 10
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, Oct 18, 2022 at 4:36 PM David Blevins
> > wrote:
> >
> >> Thanks, Jean-Louis.
> >>
> >> I was just picking through the log output of one of the startup times
> that
> >> went over 1 minute. The only gap in log output is here, during the
> MyFaces
> >> startup.
> >>
> >> -
> >>
> https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
> >>
> >> That accounts for basically 45 seconds of the startup. I've got MyFaces
> >> code up and am digging through to see what I can find.
> >>
> >> The longer timeout should work to fix the test, just curious what the
> heck
> >> could take so long!
> >>
> >>
> >> --
> >> David Blevins
> >> http://twitter.com/dblevins
> >> http://www.tomitribe.com
> >>
> >>> On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro <
> >> jlmonte...@tomitribe.com> wrote:
> >>>
> >>> Quick and deploy full green
> >>> arquillian green
> >>> examples green
> >>> tck green
> >>>
> >>> just pushed a fix for itests which is the last failure
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
> >>> jlmonte...@tomitribe.com> wrote:
> >>>
> Hi,
>
> I just pushed a fix for MTOM. Geronimo Activation does not support
> octetstream DataHandler so I added Sun provider. We can maybe go and
> add
> the support in Geronimo so we don't need Sun.
>
> Aside from some instabilities, we should be in better shape.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
> > I found the commit this started failing in through a git bisect.
> >>
> >> - FullPoolFailoverTest.testConnectionPoolTimeout -
> >> 8c0819090de1
Re: Remaining test failures
Yep. Also going to ignore for now -- looks like my YourKit license is expired.
Not sure why MyFaces took 105 seconds to do its thing. Really looking forward
to creating a TomEE 10 dist that has no front-end tech like JSF, JSTL, JSP,
etc. Should start up way faster.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Oct 18, 2022, at 7:40 AM, Jean-Louis Monteiro
> wrote:
>
> Yes I came to the same conclusion when I look at the logs even though I did
> not open MyFaces or even try to understand.
> I remembered you saying it was 12 years old machines, so I was like, let's
> be ok with it and increase the timeout a bit to wait until the server
> starts.
>
> As a quick and dirty fix it should work. We have other fixes to apply, but
> we need 9 to be final and released. We can address more issues and do more
> cleanup in 10 when catching up with Jakarta EE 10
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 4:36 PM David Blevins
> wrote:
>
>> Thanks, Jean-Louis.
>>
>> I was just picking through the log output of one of the startup times that
>> went over 1 minute. The only gap in log output is here, during the MyFaces
>> startup.
>>
>> -
>> https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
>>
>> That accounts for basically 45 seconds of the startup. I've got MyFaces
>> code up and am digging through to see what I can find.
>>
>> The longer timeout should work to fix the test, just curious what the heck
>> could take so long!
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>>> On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>>>
>>> Quick and deploy full green
>>> arquillian green
>>> examples green
>>> tck green
>>>
>>> just pushed a fix for itests which is the last failure
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
>>> jlmonte...@tomitribe.com> wrote:
>>>
Hi,
I just pushed a fix for MTOM. Geronimo Activation does not support
octetstream DataHandler so I added Sun provider. We can maybe go and add
the support in Geronimo so we don't need Sun.
Aside from some instabilities, we should be in better shape.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> I found the commit this started failing in through a git bisect.
>>
>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>> 8c0819090de18bf6c645812e88eae3202b557f83
>
>
> Also dug into this one, it seems to be related to a comment that I
>> yanked
> in the pom.xml when I was setting up activemq to use a random port.
>> Looks
> like setting
>
> openejb.home>${project.build.directory}/test-classes
>
>
> Makes the test fail. I don't know why at the minute. It was commented
>> out
> so I did it again without knowing why.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Oct 10, 2022 at 4:52 PM David Blevins >>
> wrote:
>
>> I've been working on the test failures in the main build. We're down
>> to
>> about 7 from our usual 14-17.
>>
>> This test doesn't fail for me. Is anyone else able to reproduce it?
>>
>> - MDBWithWildcardTest
>>
>> I found the commit this started failing in through a git bisect.
>>
>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>> 8c0819090de18bf6c645812e88eae3202b557f83
>>
>> I've been running git bisects trying to find the cause of the
>> examples/mtom test, but a few hours into that and still nothing
>> concussive
>> as too many of the interim steps have build failures that don't really
>> allow for running those tests and determining if the commit is good
>> or bad.
>>
>> Flying home in a bit, but hope to continue running git bisects
>> tomorrow.
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>>
>>
>>
smime.p7s
Description: S/MIME cryptographic signature
Re: Remaining test failures
Yes I came to the same conclusion when I look at the logs even though I did
not open MyFaces or even try to understand.
I remembered you saying it was 12 years old machines, so I was like, let's
be ok with it and increase the timeout a bit to wait until the server
starts.
As a quick and dirty fix it should work. We have other fixes to apply, but
we need 9 to be final and released. We can address more issues and do more
cleanup in 10 when catching up with Jakarta EE 10
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 4:36 PM David Blevins
wrote:
> Thanks, Jean-Louis.
>
> I was just picking through the log output of one of the startup times that
> went over 1 minute. The only gap in log output is here, during the MyFaces
> startup.
>
> -
> https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
>
> That accounts for basically 45 seconds of the startup. I've got MyFaces
> code up and am digging through to see what I can find.
>
> The longer timeout should work to fix the test, just curious what the heck
> could take so long!
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
> > On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
> >
> > Quick and deploy full green
> > arquillian green
> > examples green
> > tck green
> >
> > just pushed a fix for itests which is the last failure
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> >> Hi,
> >>
> >> I just pushed a fix for MTOM. Geronimo Activation does not support
> >> octetstream DataHandler so I added Sun provider. We can maybe go and add
> >> the support in Geronimo so we don't need Sun.
> >>
> >> Aside from some instabilities, we should be in better shape.
> >> --
> >> Jean-Louis Monteiro
> >> http://twitter.com/jlouismonteiro
> >> http://www.tomitribe.com
> >>
> >>
> >> On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
> >> jlmonte...@tomitribe.com> wrote:
> >>
> >>> I found the commit this started failing in through a git bisect.
>
> - FullPoolFailoverTest.testConnectionPoolTimeout -
> 8c0819090de18bf6c645812e88eae3202b557f83
> >>>
> >>>
> >>> Also dug into this one, it seems to be related to a comment that I
> yanked
> >>> in the pom.xml when I was setting up activemq to use a random port.
> Looks
> >>> like setting
> >>>
> >>> openejb.home>${project.build.directory}/test-classes
> >>>
> >>>
> >>> Makes the test fail. I don't know why at the minute. It was commented
> out
> >>> so I did it again without knowing why.
> >>> --
> >>> Jean-Louis Monteiro
> >>> http://twitter.com/jlouismonteiro
> >>> http://www.tomitribe.com
> >>>
> >>>
> >>> On Mon, Oct 10, 2022 at 4:52 PM David Blevins >
> >>> wrote:
> >>>
> I've been working on the test failures in the main build. We're down
> to
> about 7 from our usual 14-17.
>
> This test doesn't fail for me. Is anyone else able to reproduce it?
>
> - MDBWithWildcardTest
>
> I found the commit this started failing in through a git bisect.
>
> - FullPoolFailoverTest.testConnectionPoolTimeout -
> 8c0819090de18bf6c645812e88eae3202b557f83
>
> I've been running git bisects trying to find the cause of the
> examples/mtom test, but a few hours into that and still nothing
> concussive
> as too many of the interim steps have build failures that don't really
> allow for running those tests and determining if the commit is good
> or bad.
>
> Flying home in a bit, but hope to continue running git bisects
> tomorrow.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>
>
>
Re: Remaining test failures
Thanks, Jean-Louis.
I was just picking through the log output of one of the startup times that went
over 1 minute. The only gap in log output is here, during the MyFaces startup.
-
https://gist.github.com/dblevins/201aafb0f507728a03489ab9dc8a1b02#file-encryptionalgorithmstest-long-startup-log-L102-L103
That accounts for basically 45 seconds of the startup. I've got MyFaces code
up and am digging through to see what I can find.
The longer timeout should work to fix the test, just curious what the heck
could take so long!
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
> On Oct 18, 2022, at 7:18 AM, Jean-Louis Monteiro
> wrote:
>
> Quick and deploy full green
> arquillian green
> examples green
> tck green
>
> just pushed a fix for itests which is the last failure
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
>> Hi,
>>
>> I just pushed a fix for MTOM. Geronimo Activation does not support
>> octetstream DataHandler so I added Sun provider. We can maybe go and add
>> the support in Geronimo so we don't need Sun.
>>
>> Aside from some instabilities, we should be in better shape.
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
>> jlmonte...@tomitribe.com> wrote:
>>
>>> I found the commit this started failing in through a git bisect.
- FullPoolFailoverTest.testConnectionPoolTimeout -
8c0819090de18bf6c645812e88eae3202b557f83
>>>
>>>
>>> Also dug into this one, it seems to be related to a comment that I yanked
>>> in the pom.xml when I was setting up activemq to use a random port. Looks
>>> like setting
>>>
>>> openejb.home>${project.build.directory}/test-classes
>>>
>>>
>>> Makes the test fail. I don't know why at the minute. It was commented out
>>> so I did it again without knowing why.
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Mon, Oct 10, 2022 at 4:52 PM David Blevins
>>> wrote:
>>>
I've been working on the test failures in the main build. We're down to
about 7 from our usual 14-17.
This test doesn't fail for me. Is anyone else able to reproduce it?
- MDBWithWildcardTest
I found the commit this started failing in through a git bisect.
- FullPoolFailoverTest.testConnectionPoolTimeout -
8c0819090de18bf6c645812e88eae3202b557f83
I've been running git bisects trying to find the cause of the
examples/mtom test, but a few hours into that and still nothing concussive
as too many of the interim steps have build failures that don't really
allow for running those tests and determining if the commit is good or bad.
Flying home in a bit, but hope to continue running git bisects tomorrow.
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
smime.p7s
Description: S/MIME cryptographic signature
Re: Remaining test failures
Quick and deploy full green
arquillian green
examples green
tck green
just pushed a fix for itests which is the last failure
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 11:37 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> Hi,
>
> I just pushed a fix for MTOM. Geronimo Activation does not support
> octetstream DataHandler so I added Sun provider. We can maybe go and add
> the support in Geronimo so we don't need Sun.
>
> Aside from some instabilities, we should be in better shape.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
> jlmonte...@tomitribe.com> wrote:
>
>> I found the commit this started failing in through a git bisect.
>>>
>>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>>> 8c0819090de18bf6c645812e88eae3202b557f83
>>
>>
>> Also dug into this one, it seems to be related to a comment that I yanked
>> in the pom.xml when I was setting up activemq to use a random port. Looks
>> like setting
>>
>> openejb.home>${project.build.directory}/test-classes
>>
>>
>> Makes the test fail. I don't know why at the minute. It was commented out
>> so I did it again without knowing why.
>> --
>> Jean-Louis Monteiro
>> http://twitter.com/jlouismonteiro
>> http://www.tomitribe.com
>>
>>
>> On Mon, Oct 10, 2022 at 4:52 PM David Blevins
>> wrote:
>>
>>> I've been working on the test failures in the main build. We're down to
>>> about 7 from our usual 14-17.
>>>
>>> This test doesn't fail for me. Is anyone else able to reproduce it?
>>>
>>> - MDBWithWildcardTest
>>>
>>> I found the commit this started failing in through a git bisect.
>>>
>>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>>> 8c0819090de18bf6c645812e88eae3202b557f83
>>>
>>> I've been running git bisects trying to find the cause of the
>>> examples/mtom test, but a few hours into that and still nothing concussive
>>> as too many of the interim steps have build failures that don't really
>>> allow for running those tests and determining if the commit is good or bad.
>>>
>>> Flying home in a bit, but hope to continue running git bisects tomorrow.
>>>
>>>
>>> --
>>> David Blevins
>>> http://twitter.com/dblevins
>>> http://www.tomitribe.com
>>>
>>>
Re: Remaining test failures
Hi,
I just pushed a fix for MTOM. Geronimo Activation does not support
octetstream DataHandler so I added Sun provider. We can maybe go and add
the support in Geronimo so we don't need Sun.
Aside from some instabilities, we should be in better shape.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Oct 18, 2022 at 7:02 AM Jean-Louis Monteiro <
jlmonte...@tomitribe.com> wrote:
> I found the commit this started failing in through a git bisect.
>>
>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>> 8c0819090de18bf6c645812e88eae3202b557f83
>
>
> Also dug into this one, it seems to be related to a comment that I yanked
> in the pom.xml when I was setting up activemq to use a random port. Looks
> like setting
>
> openejb.home>${project.build.directory}/test-classes
>
>
> Makes the test fail. I don't know why at the minute. It was commented out
> so I did it again without knowing why.
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Mon, Oct 10, 2022 at 4:52 PM David Blevins
> wrote:
>
>> I've been working on the test failures in the main build. We're down to
>> about 7 from our usual 14-17.
>>
>> This test doesn't fail for me. Is anyone else able to reproduce it?
>>
>> - MDBWithWildcardTest
>>
>> I found the commit this started failing in through a git bisect.
>>
>> - FullPoolFailoverTest.testConnectionPoolTimeout -
>> 8c0819090de18bf6c645812e88eae3202b557f83
>>
>> I've been running git bisects trying to find the cause of the
>> examples/mtom test, but a few hours into that and still nothing concussive
>> as too many of the interim steps have build failures that don't really
>> allow for running those tests and determining if the commit is good or bad.
>>
>> Flying home in a bit, but hope to continue running git bisects tomorrow.
>>
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>>
Re: Remaining test failures
>
> I found the commit this started failing in through a git bisect.
>
> - FullPoolFailoverTest.testConnectionPoolTimeout -
> 8c0819090de18bf6c645812e88eae3202b557f83
Also dug into this one, it seems to be related to a comment that I yanked
in the pom.xml when I was setting up activemq to use a random port. Looks
like setting
openejb.home>${project.build.directory}/test-classes
Makes the test fail. I don't know why at the minute. It was commented out
so I did it again without knowing why.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Mon, Oct 10, 2022 at 4:52 PM David Blevins
wrote:
> I've been working on the test failures in the main build. We're down to
> about 7 from our usual 14-17.
>
> This test doesn't fail for me. Is anyone else able to reproduce it?
>
> - MDBWithWildcardTest
>
> I found the commit this started failing in through a git bisect.
>
> - FullPoolFailoverTest.testConnectionPoolTimeout -
> 8c0819090de18bf6c645812e88eae3202b557f83
>
> I've been running git bisects trying to find the cause of the
> examples/mtom test, but a few hours into that and still nothing concussive
> as too many of the interim steps have build failures that don't really
> allow for running those tests and determining if the commit is good or bad.
>
> Flying home in a bit, but hope to continue running git bisects tomorrow.
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>
Re: Remaining test failures
I pushed a fix for it. Let's see what happens -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Tue, Oct 11, 2022 at 12:06 PM Jean-Louis Monteiro < jlmonte...@tomitribe.com> wrote: > Richard asked for help on a BVal failure for TomEE 8 and I realised, we > had a failure on TomEE 9. So I was looking at the BVal failure on my side > but it does not fail alone on my side. It only fails when running part of > the entire TCK. So maybe a state. > > Did not test yet the other failures. > > I just ran MDBWithWildcardTest but so far it does not fail either. > So I ran it with the full arquillian JMS tests module. And I can reproduce > locally > > [INFO] Results: > [INFO] > [ERROR] Errors: > [ERROR] MDBWithWildcardTest » Deployment Unable to deploy > [INFO] > [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 1 > > I'll have a look quickly if you want > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Mon, Oct 10, 2022 at 4:52 PM David Blevins > wrote: > >> I've been working on the test failures in the main build. We're down to >> about 7 from our usual 14-17. >> >> This test doesn't fail for me. Is anyone else able to reproduce it? >> >> - MDBWithWildcardTest >> >> I found the commit this started failing in through a git bisect. >> >> - FullPoolFailoverTest.testConnectionPoolTimeout - >> 8c0819090de18bf6c645812e88eae3202b557f83 >> >> I've been running git bisects trying to find the cause of the >> examples/mtom test, but a few hours into that and still nothing concussive >> as too many of the interim steps have build failures that don't really >> allow for running those tests and determining if the commit is good or bad. >> >> Flying home in a bit, but hope to continue running git bisects tomorrow. >> >> >> -- >> David Blevins >> http://twitter.com/dblevins >> http://www.tomitribe.com >> >>
Re: Remaining test failures
Richard asked for help on a BVal failure for TomEE 8 and I realised, we had a failure on TomEE 9. So I was looking at the BVal failure on my side but it does not fail alone on my side. It only fails when running part of the entire TCK. So maybe a state. Did not test yet the other failures. I just ran MDBWithWildcardTest but so far it does not fail either. So I ran it with the full arquillian JMS tests module. And I can reproduce locally [INFO] Results: [INFO] [ERROR] Errors: [ERROR] MDBWithWildcardTest » Deployment Unable to deploy [INFO] [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 1 I'll have a look quickly if you want -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Oct 10, 2022 at 4:52 PM David Blevins wrote: > I've been working on the test failures in the main build. We're down to > about 7 from our usual 14-17. > > This test doesn't fail for me. Is anyone else able to reproduce it? > > - MDBWithWildcardTest > > I found the commit this started failing in through a git bisect. > > - FullPoolFailoverTest.testConnectionPoolTimeout - > 8c0819090de18bf6c645812e88eae3202b557f83 > > I've been running git bisects trying to find the cause of the > examples/mtom test, but a few hours into that and still nothing concussive > as too many of the interim steps have build failures that don't really > allow for running those tests and determining if the commit is good or bad. > > Flying home in a bit, but hope to continue running git bisects tomorrow. > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com > >
