Build for version 1.8.0-build.1094 of Apache Geode failed.

= The build job for Apache Geode version 1.8.0-build.1094 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.8.0-build.1094/geode-build-artifacts-1.8.0-build.1094.

Build for version 1.8.0-build.1095 of Apache Geode failed.

= The build job for Apache Geode version 1.8.0-build.1095 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.8.0-build.1095/geode-build-artifacts-1.8.0-build.1095.

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

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

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

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

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

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

Re: PR integration with concourse

After a bit of discussion with ASF INFRA, we can now start adding GitHub ‘checks’ to PR’s. This is awesome because it makes it easier for new and existing contributors to verify that their changes are good and ready to be merged. When you submit a PR, the ‘pr-develop’ pipeline [1] will trigg

Concourse instability

We're experiencing a minor amount of instability relating to filled up disks on workers, along with massive job execution. We're recreating workers so for the next hour or so things may not be working optimally. Thank you for your patience. -Sean.

Re: Concourse instability

I think we're firing on all cylinders again. I'll be monitoring it for the rest of the day for issues. On Thu, Jul 5, 2018 at 11:39 AM Sean Goller wrote: > We're experiencing a minor amount of instability relating to filled up > disks on workers, along with massive job execution. We're recreatin

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

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

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

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

[DISCUSS] Run DistributedTest more frequently

We seem to keep hitting intermittent failures in DistributedTest in our concourse pipeline. I'd like to increase the frequency that DistributedTest runs in order to shake out more flaky tests. With concourse we should be able to trigger this job on a timer so that it is running continuously. What

Re: [DISCUSS] Run DistributedTest more frequently

Sounds like a great idea. I particularly like running it on CI a bunch because it should identify flaky tests and flaky product issues, but also might find problematic interactions with how we run on CI. On Thu, Jul 5, 2018 at 4:40 PM, Dan Smith wrote: > We seem to keep hitting intermittent fa

Re: [DISCUSS] Run DistributedTest more frequently

What do you think about making a separate pipeline for this? Anthony > On Jul 5, 2018, at 4:50 PM, Alexander Murmann wrote: > > Sounds like a great idea. > > I particularly like running it on CI a bunch because it should identify > flaky tests and flaky product issues, but also might find pro

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

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

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

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

Re: [DISCUSS] Run DistributedTest more frequently

A separate pipeline would work too. Maybe we could even create multiple DistributedTest jobs to run in parallel that way We'd want to create some metrics jobs for that separate pipeline for sure. -Dan On Thu, Jul 5, 2018 at 4:53 PM, Anthony Baker wrote: > What do you think about making a se

[DISCUSS] When is a test not flaky anymore?

Hi everyone! Dan Smith started a discussion about shaking out more flaky DUnit tests. That's a great effort and I am happy it's happening. As a corollary to that conversation I wonder what the criteria should be for a test to not be considered flaky any longer and have the category removed. In g

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

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

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

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

Re: [DISCUSS] When is a test not flaky anymore?

Hi Alexander and all, > On Jul 5, 2018, at 5:11 PM, Alexander Murmann wrote: > > Hi everyone! > > Dan Smith started a discussion about shaking out more flaky DUnit tests. > That's a great effort and I am happy it's happening. > > As a corollary to that conversation I wonder what the criteria s

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

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

Re: [DISCUSS] When is a test not flaky anymore?

Honestly I've never liked the flaky category. What it means is that at some point in the past, we decided to put off tracking down and fixing a failure and now we're left with a bug number and a description and that's it. I think we will be better off if we just get rid of the flaky category entir

Build failed in Jenkins: Geode-nightly #1248

See Changes: [github] GEODE-5212: Ensure that paths on Windows don't end up with spaces [github] GEODE-5373: Adjust timing for [jdeppe] Fix test which is using a hijacked domain [jdeppe] Don't send email on failu