Re: Looking for geode-core dunit using 5 dunit VMs

[Barry Oglesby]

All of the WAN dunit tests use more than 5 VMS, but I'm not sure you want
those. Those are anything extending WANTestBase. I also see
LocatorDUnitTest testMultipleLocatorsRestartingAtSameTime does as well.

Thanks,
Barry Oglesby


On Thu, Oct 5, 2017 at 10:05 AM, Kirk Lund  wrote:

> I need help looking for a geode-core dunit test that is using 5 dunit VMs
> instead of 4. I want to review that test and then decide what to do with
> the DistributedTest framework tests that might run after it (the tests that
> verify that dunit itself is ok).
>
> This test is doing something like this:
>
> Host.getHost(0).getVM(4) <-- this is zero-based so it would cause dunit to
> create a 5th VM
>
> Thanks,
> Kirk
>

Re: Looking for geode-core dunit using 5 dunit VMs

[Kirk Lund]

I found them (or some of them):

1) LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTime() <- uses 5
VMs in addition to controller & locator
2)
LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTimeWithMissingServers()
<- uses 5 VMs in addition to controller & locator
3)
PreferSerializedHARegionQueueTest.copyingHARegionQueueShouldNotThrowException()
<- uses 7 VMs in addition to controller & locator

I'll change the dunit infrastructure tests to get rid of any expectation of
4 default VMs since those tests may run after the above tests.

Thanks,
Kirk

On Thu, Oct 5, 2017 at 10:05 AM, Kirk Lund  wrote:

> I need help looking for a geode-core dunit test that is using 5 dunit VMs
> instead of 4. I want to review that test and then decide what to do with
> the DistributedTest framework tests that might run after it (the tests that
> verify that dunit itself is ok).
>
> This test is doing something like this:
>
> Host.getHost(0).getVM(4) <-- this is zero-based so it would cause dunit to
> create a 5th VM
>
> Thanks,
> Kirk
>

Looking for geode-core dunit using 5 dunit VMs

[Kirk Lund]

I need help looking for a geode-core dunit test that is using 5 dunit VMs
instead of 4. I want to review that test and then decide what to do with
the DistributedTest framework tests that might run after it (the tests that
verify that dunit itself is ok).

This test is doing something like this:

Host.getHost(0).getVM(4) <-- this is zero-based so it would cause dunit to
create a 5th VM

Thanks,
Kirk