Re: Reviewing our JIRA's

2018-04-26 Thread Lynn Hughes-Godfrey
Modifying your filter to look at jiras that haven't been updated in a year (vs. created in the past year) ... there are 114 to review. That probably means there were updates for 34 of those when they reproduced in CI, etc, so we wouldn't want to close those. Looking specifically at GEODE-552 ...

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

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

Re: [VOTE] Apache Geode 1.6.0 RC1

2018-04-26 Thread Michael Stolz
Yeah, looks like a copy and paste issue that caused the link to get wrapped to a new line. Sorry. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the GemFire book here. On Thu,

Re: [VOTE] Apache Geode 1.6.0 RC1

2018-04-26 Thread Diane Hardman
Here is the correct link to the Release notes: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.6.0 On Thu, Apr 26, 2018 at 2:13 PM, Diane Hardman wrote: > The link to the Release notes seems to be incorrect. > > > > On Thu, Apr 26, 2018 at

Re: [VOTE] Apache Geode 1.6.0 RC1

2018-04-26 Thread Diane Hardman
The link to the Release notes seems to be incorrect. On Thu, Apr 26, 2018 at 11:05 AM, Mike Stolz wrote: > This is the first release candidate for Apache Geode, version 1.6.0. > Thanks to all the community members for their contributions to this > release! > > *** Please

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

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

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

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

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

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

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

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

Re: Reviewing our JIRA's

2018-04-26 Thread Galen O'Sullivan
I'm for it. Less noise is a good thing, and I don't think they're likely to get prioritized anyways. If we close as WONTFIX or similar, we can always look back for them later if we want. On 4/26/18 10:39 AM, Anthony Baker wrote: Thanks Lynn! As I first step I’d like to focus on issues

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

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

[VOTE] Apache Geode 1.6.0 RC1

2018-04-26 Thread Mike Stolz
This is the first release candidate for Apache Geode, version 1.6.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Monday, April 30, 1500 hrs US Pacific. *** It fixes 157 issues. Release notes can be found at:

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

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

Re: Reviewing our JIRA's

2018-04-26 Thread Anthony Baker
Thanks Lynn! As I first step I’d like to focus on issues labeled as ‘CI’. There are 220 open issues and 148 [1] of those have been open for > 1 year. If I look at the metrics jobs [2, 3, 4] I see a clear mismatch between failures that are currently relevant and our JIRA backlog. That is, a