I agree with this. We should have a default state that reflects an “out of
the box” configuration, and if tests expects a different configuration, it
should manage that within the context of the test.
-Sean
On Tue, Mar 13, 2018 at 10:04 AM Kirk Lund wrote:
> I want to propose using the default
+1 agreement with Kirk and Sean.
Any non default configuration should probably have it's own set of tests.
I can understand some exploratory work where someone might want to run the
whole precheckin with a non default value to help identify areas that they
may have missed or are unexpectedly affec
+0.5 I think we can turn this off (back to the default) now since the
AnalyzeSerializables tests for other modules have been created. These
tests ensure that serializable objects are properly white-listed or
excluded and are able to be serialized/deserialized.
Excluded classes are not tested
Thank you for all the comments/suggestions. I've updated the wiki page with
more details and scope of this api.
https://cwiki.apache.org/confluence/display/GEODE/Public+API+for+Cluster+Configuration
Thanks!
On Wed, Mar 14, 2018 at 11:57 AM, John Blum wrote:
> *> @Jake, I vaguely remember that
---
Spring Data GemFire > Nightly-ApacheGeode > #857 was successful.
---
Scheduled
2381 tests in total.
https://build.spring.io/browse/SGF-NAG-857/
--
This
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/285
