+1 to a single source of member wait calls.
We already have a standard set of await methods for DUnit member VMs,
located in the MemberVM class, and delegated to that class from the
MemberStarterRule. I have a PR outstanding [1] that improves those
methods, too.
For those awaits that are common
I recommend keeping this Awaitility with default timeout separate from any
Rules or MemberVM. I want to be able to use Awaitility in integration tests
and distributed tests that don't use MemberVM or the StarterRules. So from
that POV, I'd prefer the GeodeAwaitility that Dan proposes.
On Thu, Jul
I typically use 2 MINUTES as the timeout for everything I've worked on in
integration or distributed tests. I believe that whatever the underlying
async action is will still complete well under 2 MINUTES even if a long GC
pause occurs during that window of time. 5 MINUTES is probably longer than
we
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/151
=
The build job for Apache Geode version 1.8.0-build.1121 has failed.
Build artifacts are available at:
http://files.apachegeode-ci.info/builds/1.8.0-build.1121/geode-build-artifacts-1.8.0-build.1121.
---
Spring Data GemFire > Nightly-ApacheGeode > #976 was successful.
---
Scheduled
2425 tests in total.
https://build.spring.io/browse/SGF-NAG-976/
--
This
