Re: Last call on 1.2.0 (and fixing test failures)

Q team found a bug today during a gfsh bug hunt that needs to be fixed: GEODE-2943. Lynn may have also found another data consistency bug, but I don't have the bug number yet. I also need to learn how to build the docs so I can review Karen's pull request. Any help would be very much appreciated.

Re: Last call on 1.2.0 (and fixing test failures)

FixedPRSinglehopDUnitTest. testMetadataInClientWithFixedPartitions seems like a problem that could cause lots of tests to fail intermittently. It looks like a race with the cluster config service starting up async in the locator. I added this failure to GEODE-2238. On Tue, May 16, 2017 at 3:17

Re: Last call on 1.2.0 (and fixing test failures)

The fix for GEODE-2915 is on the develop branch. Le 5/16/2017 à 10:10 AM, Anthony Baker a écrit : On May 14, 2017, at 6:47 PM, Anthony Baker wrote: Hi everyone, Our last release was v1.1.1 in March. We have made a lot of great progress on the develop branch with over 250

Re: Last call on 1.2.0 (and fixing test failures)

> On May 16, 2017, at 10:10 AM, Anthony Baker wrote: > > > The last Jenkins run shows these failures: > > org.apache.geode.management.internal.cli.commands.ShowDeadlockDUnitTest.testDistributedDeadlockWithFunction >

Re: Last call on 1.2.0 (and fixing test failures)

I committed a fix for the two ShowDealockDUnitTest failures yesterday, and they are now passing in Jenkins. > On May 16, 2017, at 10:10 AM, Anthony Baker wrote: > > >> On May 14, 2017, at 6:47 PM, Anthony Baker wrote: >> >> Hi everyone, >> >> Our last

Re: Last call on 1.2.0 (and fixing test failures)

> On May 14, 2017, at 6:47 PM, Anthony Baker wrote: > > Hi everyone, > > Our last release was v1.1.1 in March. We have made a lot of great progress > on the develop branch with over 250 issues fixed. It would be great to get > those changes into a release. What’s left

Re: Last call on 1.2.0 (and fixing test failures)

I will be checking in rolling-upgrade testing against 1.1.1 with my fix for GEODE-2915 Le 5/15/2017 à 5:07 PM, Lynn Hughes-Godfrey a écrit : We need to ensure we have backward compatibility and rolling upgrade capability/testing with geode 1.1. -l- On Mon, May 15, 2017 at 4:09 PM, Jason

Re: Last call on 1.2.0 (and fixing test failures)

We need to ensure we have backward compatibility and rolling upgrade capability/testing with geode 1.1. -l- On Mon, May 15, 2017 at 4:09 PM, Jason Huynh wrote: > GEODE-2900 has been checked into develop > > On Mon, May 15, 2017 at 3:47 PM Bruce Schuchardt

Re: Last call on 1.2.0 (and fixing test failures)

GEODE-2900 has been checked into develop On Mon, May 15, 2017 at 3:47 PM Bruce Schuchardt wrote: > Yes, GEODE-2915 needs to be fixed for 1.2.0 > > Le 5/15/2017 à 11:59 AM, Lynn Hughes-Godfrey a écrit : > > GEODE-2915: Messages rejected due to unknown "vmkind" > > > > > >

Re: Last call on 1.2.0 (and fixing test failures)

Yes, GEODE-2915 needs to be fixed for 1.2.0 Le 5/15/2017 à 11:59 AM, Lynn Hughes-Godfrey a écrit : GEODE-2915: Messages rejected due to unknown "vmkind" On Mon, May 15, 2017 at 11:26 AM, Jason Huynh wrote: GEODE-2900 would be nice to get in for Lucene integration. I

Re: Last call on 1.2.0 (and fixing test failures)

The fix for GEODE-2912 is under test & review. I had to make changes to it today to clear up some problems in Version.java and add a Version.GEODE_120. Le 5/15/2017 à 3:33 PM, Jared Stewart a écrit : GEODE-2912 is checked in on develop now. On May 15, 2017, at 11:59 AM, Lynn Hughes-Godfrey

Re: Last call on 1.2.0 (and fixing test failures)

GEODE-2912 is checked in on develop now. > On May 15, 2017, at 11:59 AM, Lynn Hughes-Godfrey > wrote: > > GEODE-2915: Messages rejected due to unknown "vmkind" > > > > On Mon, May 15, 2017 at 11:26 AM, Jason Huynh wrote: > >> GEODE-2900 would

Re: Last call on 1.2.0 (and fixing test failures)

GEODE-2915: Messages rejected due to unknown "vmkind" On Mon, May 15, 2017 at 11:26 AM, Jason Huynh wrote: > GEODE-2900 would be nice to get in for Lucene integration. I hope to get > it checked in today > > On Mon, May 15, 2017 at 10:24 AM Swapnil Bawaskar

Re: Last call on 1.2.0 (and fixing test failures)

GEODE-2900 would be nice to get in for Lucene integration. I hope to get it checked in today On Mon, May 15, 2017 at 10:24 AM Swapnil Bawaskar wrote: > I think we should also wait for GEODE-2836 > > On Mon, May 15, 2017 at 8:58 AM Karen Miller wrote:

Re: Last call on 1.2.0 (and fixing test failures)

I think it would be nice to include GEODE-2912 (Real hot deploy of Functions via gfsh) with this release, time permitting. This would be a nice QoL improvement for users along with the already-completed GEODE-2290. > On May 15, 2017, at 8:58 AM, Karen Miller wrote: > >

Re: Last call on 1.2.0 (and fixing test failures)

I think we should also wait for GEODE-2836 On Mon, May 15, 2017 at 8:58 AM Karen Miller wrote: > Let's finish GEODE-2913, the documentation for improvements made to the > Lucene integration and include it with the 1.2.0 release! > > > On Sun, May 14, 2017 at 6:47 PM, Anthony

Re: Last call on 1.2.0 (and fixing test failures)

Let's finish GEODE-2913, the documentation for improvements made to the Lucene integration and include it with the 1.2.0 release! On Sun, May 14, 2017 at 6:47 PM, Anthony Baker wrote: > Hi everyone, > > Our last release was v1.1.1 in March. We have made a lot of great >

Last call on 1.2.0 (and fixing test failures)

Hi everyone, Our last release was v1.1.1 in March. We have made a lot of great progress on the develop branch with over 250 issues fixed. It would be great to get those changes into a release. What’s left before we are ready to release 1.2.0? Note that we need a clean test run before