> > 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 > >