LoggingDependenciesTest is also an archunit test in geode-core. I'm going to move LoggingDependenciesTest to integrationTest -- testing the direction of dependency between two geode modules seems to fit the definition of "integration".
On Thu, Nov 21, 2019 at 12:09 PM Dan Smith <dsm...@pivotal.io> wrote: > We've disabled this test for now, so you shouldn't get an OOME with the > latest develop. > > -Dan > > On Wed, Nov 20, 2019, 4:55 PM Michael Oleske <mole...@pivotal.io> wrote: > > > I've hit the same error as Kirk. My lazy solution was to just rerun > > `./gradlew build` cause that would pass on the second time. > > > > -michael > > > > On Wed, Nov 20, 2019 at 4:53 PM Dan Smith <dsm...@pivotal.io> wrote: > > > > > We recently added this test. It passes for me, but I will look into it. > > It > > > is scanning classes, so that may be your oome. > > > > > > On Wed, Nov 20, 2019, 4:00 PM Kirk Lund <kl...@apache.org> wrote: > > > > > > > Any ideas why DistributionArchUnitTest would run OutOfMemoryError > when > > > > doing a "./gradlew build"? > > > > > > > > I think we should move any unit tests that run OutOfMemoryError out > of > > > unit > > > > tests (to integration tests maybe?). > > > > > > > > > Task :geode:geode-core:test > > > > Heap dump file created [957877145 bytes in 17.227 secs] > > > > > > > > org.apache.geode.distributed.internal.DistributionArchUnitTest > > > > > classMethod FAILED > > > > java.lang.OutOfMemoryError: GC overhead limit exceeded > > > > > > > > 6991 tests completed, 1 failed, 12 skipped > > > > > > > > > >
