Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

2018-06-04 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/39

Geode unit tests completed in 'develop/UITests' with non-zero exit code

2018-06-04 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/58

Re: PR #1868: new ThreadMonitoring feature

2018-06-04 Thread Udo Kohlmeyer
Some great points Bruce!! I believe this whole thread Monitoring feature needs to have the scope expanded... I mean.. We would either require compensatory events to rollback ANYTHING that the thread had been doing until the point it was killed. When it was proposed, I understood it as a mech

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

2018-06-04 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #938 was successful. --- Scheduled 2408 tests in total. https://build.spring.io/browse/SGF-NAG-938/ -- This

Re: PR #1868: new ThreadMonitoring feature

2018-06-04 Thread Bruce Schuchardt
This looks like a dangerous change that is putting a fixed time limit on execution of arbitrary jobs with no real check to see if threads are stuck or not.  If a thread is doing some heavy lifting it could be killed with Thread.stop() in the middle of its work. Think initial image transfer, for

Re: PR #1868: new ThreadMonitoring feature

2018-06-04 Thread Bruce Schuchardt
This seems like a really bad idea.  It's using the long-deprecated Thread.stop() to kill executor threads that take too long to execute.  It has no idea what state the thread is in when it kills it.  It could be doing disk I/O or writing to shared memory. On 6/4/18 9:50 AM, Kirk Lund wrote:

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

2018-06-04 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/53

PR #1868: new ThreadMonitoring feature

2018-06-04 Thread Kirk Lund
Can a couple more folks please review PR #1868? My review feedback pertained only to using dependency injection instead of a singleton or static getter and Yossi has updated the code as I requested. My review doesn't really address the usefulness of the feature or the impact on features that were

Geode unit tests completed in 'develop/UITests' with non-zero exit code

2018-06-04 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/53

Geode unit tests 'develop/DistributedTest' took too long to execute

2018-06-04 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/36