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 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</openejb.home> > >>> > >>> > >>> 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 <david.blev...@gmail.com > > > >>> 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 > >>>> > >>>> > >
