Vince just told me that we can't use Docker in Windows. So that's one
downside.
On Thu, Aug 24, 2017 at 7:27 AM, Darrel Schneider
wrote:
> I like the sound of #1:
> 1) use Docker for AcceptanceTest and IntegrationTest targets?
>
> Does anyone know of a downside to running these tests in docker?
I like the sound of #1:
1) use Docker for AcceptanceTest and IntegrationTest targets?
Does anyone know of a downside to running these tests in docker?
On Wed, Aug 23, 2017 at 12:06 PM, Jared Stewart wrote:
> I think we just need to have AcceptanceTest (and possibly IntegrationTest)
> run inside
I think we just need to have AcceptanceTest (and possibly IntegrationTest) run
inside Docker like DistributedTest already does.
- Jared.
> On Aug 23, 2017, at 11:32 AM, Anilkumar Gingade wrote:
>
>>> 1) use Docker for AcceptanceTest and IntegrationTest targets?
> To be clear, the failing tests
>> 1) use Docker for AcceptanceTest and IntegrationTest targets?
To be clear, the failing tests are only in Acceptance Test and Integration
Tests? And distributed tests are not seeing this issue as they are running
in docker nowIf moving docker address this issue, my vote is for moving
docker;
The following nightly build failures are tests that are testing default
ports which are failing because the port is not available.
Should we:
1) use Docker for AcceptanceTest and IntegrationTest targets?
2) not test default ports?
3) use a hacky System property to force Geode to think that some
