Geode tests completed in pipeline with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/47

Build failed in Jenkins: Geode-nightly-flaky #192

See Changes: [dschneider] GEODE-4091: add ThreadFactory for evictor [github] GEODE-4083: fix infinite loop caused by thread race changing version [dschneider] GEODE-4099: change warning to debug [github] GEO

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #767 was SUCCESSFUL (with 2264 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #767 was successful. --- Scheduled 2266 tests in total. https://build.spring.io/browse/SGF-NAG-767/ -- This

Build failed in Jenkins: Geode-nightly #1044

See Changes: [dschneider] GEODE-4091: add ThreadFactory for evictor [github] GEODE-4083: fix infinite loop caused by thread race changing version [dschneider] GEODE-4099: change warning to debug [github] GEODE-37

Geode tests completed in pipeline with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/33

Re: Debugging intermittent dunit failures

This is even better than I hoped for. +1 to make the change. I already approved the PR. On Fri, Dec 15, 2017 at 7:50 AM, Jens Deppe wrote: > Using forkEvery=1, my distributedTest run took 3h5m which is maybe 10 > minutes slower than the random sampling I did of other tests and > distributedTest

Fwd: [jira] [Commented] (GEODE-4061) Adding coordinator in list member command output

Any one vl merge this pull request? Thanks Dinesh -- Forwarded message -- From: "ASF GitHub Bot (JIRA)" Date: 14-Dec-2017 9:45 pm Subject: [jira] [Commented] (GEODE-4061) Adding coordinator in list member command output To: Cc: > [ https://issues.apache.org/jira/browse/GEOD

Re: how to get a good commit comment when using gitbox to merge a pull request

On the pull request web UI, I usually just use "Squash and Merge" which will give me a chance to revise the commit messages. On Thu, Dec 14, 2017 at 11:15 AM, Darrel Schneider wrote: > I noticed that the git log message for a pull request I just merged was > lacking what I expected it to pick up

Re: Debugging intermittent dunit failures

Using forkEvery=1, my distributedTest run took 3h5m which is maybe 10 minutes slower than the random sampling I did of other tests and distributedTestCore took 2h35m which is on par with others. I'd say that it's worth switching to forkEvery=1 as it will most likely provide more consistency for te