Build failed in Jenkins: Geode-nightly #1239

See -- [...truncated 49.58 KB...] > Task :geode-connectors:spotlessJava > Task :geode-connectors:spotlessJavaCheck > Task :geode-connectors:spotlessCheck > Task :geode-connectors:test > Task

Fwd: Build failed in Jenkins: Geode-nightly #1238

I cleaned up the workspace which should resolve the rat failure. Gradle 4.8 leaves a file behind on first use. Anthony > Begin forwarded message: > > From: Apache Jenkins Server > Subject: Build failed in Jenkins: Geode-nightly #1238 > Date: June 27, 2018 at 9:36:17 PM PDT > To: dev@geode.ap

Build failed in Jenkins: Geode-nightly #1238

See Changes: [github] GEODE-5346: Fix race in LauncherLifecycleCommandsDUnitTest (#2080) [bschuchardt] GEODE-1198 CI Failure: DistributedSystemDUnitTest.testConflictingUDPPort

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #961 was SUCCESSFUL (with 2423 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #961 was successful. --- Scheduled 2425 tests in total. https://build.spring.io/browse/SGF-NAG-961/ -- This

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/83

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

Don't forget to add "acceptanceTest/" On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett wrote: > I'd like to suggest that we refactor our current test source set, which > contains both unit, integration and distributed tests, into distinct source > sets, test, integrationTest, distributedTest. Thes

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

The two main ways to organize tests are hierarchies (such as packages or file folders) and tagging (such as tagging). Each supports different purposes for selecting tests to run. Hierarchies are good for stable, mutually exclusive purposes. Unit, Distributed, Integration, and Acceptance seem li

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

what about "testUtilities" instead of "commonTest"? On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett wrote: > I'd like to suggest that we refactor our current test source set, which > contains both unit, integration and distributed tests, into distinct source > sets, test, integrationTest, distrib