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

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

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

Re: [Discussion] Improving Spotless to be Even More Beautiful

+1 to all of the above. Will Spotless also reorder imports according to our canonical ordering? On Mon, Mar 19, 2018 at 4:17 PM, Sai Boorlagadda wrote: > +1 > > On Mon, Mar 19, 2018 at 4:03 PM, Kirk Lund wrote: > > > +1 > > > > On Mon, Mar 19, 2018

Re: [Discussion] Improving Spotless to be Even More Beautiful

+1 On Mon, Mar 19, 2018 at 4:03 PM, Kirk Lund wrote: > +1 > > On Mon, Mar 19, 2018 at 2:51 PM, Patrick Rhomberg > wrote: > > > Hello all! > > > > I'm making another pass at patching up some of our smellier broken > > windows, to mix metaphors. To that

Re: [Discussion] Improving Spotless to be Even More Beautiful

+1 On Mon, Mar 19, 2018 at 2:51 PM, Patrick Rhomberg wrote: > Hello all! > > I'm making another pass at patching up some of our smellier broken > windows, to mix metaphors. To that end, there are a few things I'd like to > add to spotless to more closely enforce

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

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

Re: [Discussion] Improving Spotless to be Even More Beautiful

+1 to all of the above On Mon, Mar 19, 2018 at 2:51 PM, Patrick Rhomberg wrote: > Hello all! > > I'm making another pass at patching up some of our smellier broken > windows, to mix metaphors. To that end, there are a few things I'd like to > add to spotless to more

[Discussion] Improving Spotless to be Even More Beautiful

Hello all! I'm making another pass at patching up some of our smellier broken windows, to mix metaphors. To that end, there are a few things I'd like to add to spotless to more closely enforce adherence to our own style guide. I'd like to do the following to our spotless: - Bump spotless to

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

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

Re: [Proposal] Gfsh Command Feature Flag Annotation

I kind of like @Disabled instead. Sarge > On 19 Mar, 2018, at 11:58, Udo Kohlmeyer wrote: > > I wonder if this proposal could not be extended to the greater GEODE product. > As this feature flagging is also relevant to other parts of the system and > should maybe be

Re: [Proposal] Gfsh Command Feature Flag Annotation

I wonder if this proposal could not be extended to the greater GEODE product. As this feature flagging is also relevant to other parts of the system and should maybe be consistently applied to all areas. Thoughts? On 3/19/18 11:46, Patrick Rhomberg wrote: Hello, All I am interested in

[Proposal] Gfsh Command Feature Flag Annotation

Hello, All I am interested in extending annotation functionality on our gfsh commands, particularly with respect to feature-flagging commands that are mutually-reliant or not yet feature complete. Please review the proposal [1] at your convenience. Imagination is Change. ~Patrick Rhomberg

Re: Disabling DistributedRestoreSystemPropertiesTest for now

Thanks Jens! I was searching for the cause on Friday but couldn't find it. Looks like any static usage of ClusterStartupRule ends up launching DUnit VMs. Gradle JUnit class loads (but does not instantiate) *Test.java. The tests that have public static ClusterStartupRules result in