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/102

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

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

Re: Requesting to be added to Geode dev list

Thanks Udo! I am now subscribed to the dev list so seems like I'll be good to go after being added to the JIRA (unless I missed some important step in there). ~Helena On Fri, Jul 6, 2018 at 2:14 PM, Udo Kohlmeyer wrote: > Hi there Helena, > > To subscribe to the dev list, please follow the

concourse excitement

We're having some unintended instability in the geode concourse at the moment, the concourse atc vm is being recreated so some DNS may need to be updated once everything settles down. For the moment however, geode concourse is going to be inaccessible for a bit. My apologies, it did not seem like

Re: Requesting to be added to Geode dev list

Hi there Helena, To subscribe to the dev list, please follow the steps indicated. Someone, with relevant karma, will be in touch shortly to add you to the JIRA project. --Udo On 7/6/18 14:00, Helena Bales wrote: Hello, I would like to be added to the Geode dev list and get access to

Requesting to be added to Geode dev list

Hello, I would like to be added to the Geode dev list and get access to JIRA. I am working on a GEODE ticket and would like to be able to assign it and ask for reviews on my pull request and such. My Jira username is balesh2. Thank you, Helena Bales

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

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

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/136

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

+1 for fixing immediately. Since Dan is already trying to shake out more brittleness this seems to be the right time to get rid of the flaky label. Let's just treat all test the same and fix them. On Fri, Jul 6, 2018 at 9:31 AM, Kirk Lund wrote: > I should add that I'm only in favor of

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

I should add that I'm only in favor of deleting the category if we have a new policy of any failure means we have to fix the test and/or product code. Even if you think that failure is in a test that you or your team is not responsible for. That's no excuse to ignore a failure in your private

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

The pattern I’ve seen in lots of other organizations: When a few tests intermittently give different answers, people attribute the intermittence to the tests, quickly lose trust in the entire suite, and increasingly discount failures. If we’re going to attend to every failure in the larger

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

+1 go ahead and delete FlakyTest category but please NEVER go back to marking flaky tests with @Ignore or renaming JUnit 3 test methods -- in my opinion that was infinitely worse. The category was meant to be a quarantine for FIXING not for IGNORING. On Fri, Jul 6, 2018 at 7:26 AM, Anthony Baker

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/137

Jenkins build is back to normal : Geode-nightly #1250

See

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/136

Re: Rat failure

I gave up trying to configure Jenkins and added the exclusion. Anthony > On Jul 2, 2018, at 1:36 PM, Anthony Baker wrote: > > We could but it feels wrong :-) > > The rat excludes list files that we decided are ok to include in the source > tree. I don’t think the gradle notification file

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/133

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/134

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

Check [1] to see what ‘flaky’ tests have failed recently. Anthony [1] https://concourse.apachegeode-ci.info/teams/main/pipelines/develop-metrics/jobs/GeodeFlakyTestMetrics/builds/51

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

+1 for removing flaky category and fix as failure occurs. On Thu, Jul 5, 2018 at 8:21 PM Dan Smith wrote: > 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