You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geode.apache.org by Dan Smith <ds...@pivotal.io> on 2018/10/17 22:10:47 UTC

StressNewTest issues

Hi all,

It looks like some recent changes caused the StressNewTest job in the PR
checks to not use docker to run the tests. This means you may see failures
such as a DiskAccessExceptions due to concurrent modification of files, or
just "Could not start dunit VMS" until GEODE-5893 is fixed.

-Dan

Re: StressNewTest issues

Posted by Galen O'Sullivan <go...@pivotal.io>.

Thanks for keeping us updated and fixing this, Dan!

Galen

On Wed, Oct 17, 2018 at 3:48 PM Dan Smith <ds...@pivotal.io> wrote:

> Should be fixed now, if you rebase/merge on the latest develop.
>
> -Dan
>
>
> On Wed, Oct 17, 2018 at 3:10 PM Dan Smith <ds...@pivotal.io> wrote:
>
> > Hi all,
> >
> > It looks like some recent changes caused the StressNewTest job in the PR
> > checks to not use docker to run the tests. This means you may see
> failures
> > such as a DiskAccessExceptions due to concurrent modification of files,
> or
> > just "Could not start dunit VMS" until GEODE-5893 is fixed.
> >
> > -Dan
> >
>

Re: StressNewTest issues

Posted by Dan Smith <ds...@pivotal.io>.

Should be fixed now, if you rebase/merge on the latest develop.

-Dan


On Wed, Oct 17, 2018 at 3:10 PM Dan Smith <ds...@pivotal.io> wrote:

> Hi all,
>
> It looks like some recent changes caused the StressNewTest job in the PR
> checks to not use docker to run the tests. This means you may see failures
> such as a DiskAccessExceptions due to concurrent modification of files, or
> just "Could not start dunit VMS" until GEODE-5893 is fixed.
>
> -Dan
>