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/439
Re: [VOTE] Apache Geode 1.5.0 RC1
-1 I filed GEODE-4913 based on scripts I have that create 2 clusters connected by a WAN gateway on my local machine. *Problem*: we are opening a cache-server on default port (40404) irrespective of the fact that one is explicitly specified in cache.xml. *symptoms*: users who start more than one Geode server on the same “box” and use cache.xml to specify port would get bind exceptions when they start the second server. *workaround*: 1. specify `--disable-default-server` on the `start server` command while still specifying port in cache.xml. 2. specify port on the `start server` command itself and remove any references to port from cache.xml. The problem will break a lot of existing scripts and, though we have a workaround, it will cause headaches for many when they encounter it. On Wed, Mar 21, 2018 at 2:52 PM, Dan Smith wrote: > +1 > > Run geode-release-check. Verified no MD5 files in the distribution. > > -Dan > > On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker wrote: > > > +1 > > > > - verified signatures and checksums > > - checked source release for binaries > > - basic gfsh testing > > - ran all the examples > > > > Anthony > > > > > On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar > > wrote: > > > > > > This is the first release candidate for Apache Geode, version 1.5.0. > > > Thanks to all the community members for their contributions to this > > > release! > > > > > > *** Please download, test and vote by Friday, March 23, 1500 hrs > > > US Pacific. *** > > > > > > It fixes 234 issues. release notes can be found at: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12318420&version=12342395 > > > > > > Note that we are voting upon the source tags: rel/v1.5.0.RC1 > > > https://github.com/apache/geode/tree/rel/v1.5.0.RC1 > > > https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 > > > > > > Commit ID: > > > 4ef51dacd79ff69336fb024f3d4b07271e90 (geode) > > > 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) > > > > > > Source and binary files: > > > https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachegeode-1038 > > > > > > > > > Geode's KEYS file containing PGP keys we use to sign the release: > > > https://github.com/apache/geode/blob/develop/KEYS > > > > > > Release Signed with Key: pub 4096R/18F902DB 2016-04-07 > > > Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB > > > > >
Re: [VOTE] Apache Geode 1.5.0 RC1
Thanks for catching this Diane. I agree; we shouldn't break something that used to work. Anthony On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote: -1 I filed GEODE-4913 based on scripts I have that create 2 clusters connected by a WAN gateway on my local machine. *Problem*: we are opening a cache-server on default port (40404) irrespective of the fact that one is explicitly specified in cache.xml. *symptoms*: users who start more than one Geode server on the same “box” and use cache.xml to specify port would get bind exceptions when they start the second server. *workaround*: 1. specify `--disable-default-server` on the `start server` command while still specifying port in cache.xml. 2. specify port on the `start server` command itself and remove any references to port from cache.xml. The problem will break a lot of existing scripts and, though we have a workaround, it will cause headaches for many when they encounter it. On Wed, Mar 21, 2018 at 2:52 PM, Dan Smith wrote: +1 Run geode-release-check. Verified no MD5 files in the distribution. -Dan On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker wrote: +1 - verified signatures and checksums - checked source release for binaries - basic gfsh testing - ran all the examples Anthony On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar wrote: This is the first release candidate for Apache Geode, version 1.5.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Friday, March 23, 1500 hrs US Pacific. *** It fixes 234 issues. release notes can be found at: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12318420&version=12342395 Note that we are voting upon the source tags: rel/v1.5.0.RC1 https://github.com/apache/geode/tree/rel/v1.5.0.RC1 https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 Commit ID: 4ef51dacd79ff69336fb024f3d4b07271e90 (geode) 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) Source and binary files: https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachegeode-1038 Geode's KEYS file containing PGP keys we use to sign the release: https://github.com/apache/geode/blob/develop/KEYS Release Signed with Key: pub 4096R/18F902DB 2016-04-07 Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
Re: [VOTE] Apache Geode 1.5.0 RC1
The same could be said of GEODE-4787. On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker wrote: > Thanks for catching this Diane. I agree; we shouldn't break something that > used to work. > > Anthony > > > On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote: > > -1 > I filed GEODE-4913 based on scripts I have that create 2 clusters connected > by a WAN gateway on my local machine. > *Problem*: we are opening a cache-server on default port (40404) > irrespective of the fact that one is explicitly specified in cache.xml. > *symptoms*: users who start more than one Geode server on the same “box” > and use cache.xml to specify port would get bind exceptions when they start > the second server. > *workaround*: > 1. specify `--disable-default-server` on the `start server` command > while still specifying port in cache.xml. > 2. specify port on the `start server` command itself and remove any > references to port from cache.xml. > > The problem will break a lot of existing scripts and, though we have a > workaround, it will cause headaches for many when they encounter it. > > On Wed, Mar 21, 2018 at 2:52 PM, Dan Smith wrote: > > +1 > > Run geode-release-check. Verified no MD5 files in the distribution. > > -Dan > > On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker wrote: > > +1 > > - verified signatures and checksums > - checked source release for binaries > - basic gfsh testing > - ran all the examples > > Anthony > > On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar > > wrote: > > > This is the first release candidate for Apache Geode, version 1.5.0. > Thanks to all the community members for their contributions to this > release! > > *** Please download, test and vote by Friday, March 23, 1500 hrs > US Pacific. *** > > It fixes 234 issues. release notes can be found at: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12318420&version=12342395 > > > Note that we are voting upon the source tags: rel/v1.5.0.RC1 > https://github.com/apache/geode/tree/rel/v1.5.0.RC1 > https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 > > Commit ID: > 4ef51dacd79ff69336fb024f3d4b07271e90 (geode) > 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) > > Source and binary files: > https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachegeode-1038 > > > Geode's KEYS file containing PGP keys we use to sign the release: > https://github.com/apache/geode/blob/develop/KEYS > > Release Signed with Key: pub 4096R/18F902DB 2016-04-07 > Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB > -- -John john.blum10101 (skype)
Re: [VOTE] Apache Geode 1.5.0 RC1
-1 Due to the regression in functionality. GEODE-4913 @John, I agree, GEODE-4787 should be addressed with priority. --Udo On 3/23/18 15:04, John Blum wrote: The same could be said of GEODE-4787. On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker wrote: Thanks for catching this Diane. I agree; we shouldn't break something that used to work. Anthony On Mar 23, 2018, at 11:27 AM, Diane Hardman wrote: -1 I filed GEODE-4913 based on scripts I have that create 2 clusters connected by a WAN gateway on my local machine. *Problem*: we are opening a cache-server on default port (40404) irrespective of the fact that one is explicitly specified in cache.xml. *symptoms*: users who start more than one Geode server on the same “box” and use cache.xml to specify port would get bind exceptions when they start the second server. *workaround*: 1. specify `--disable-default-server` on the `start server` command while still specifying port in cache.xml. 2. specify port on the `start server` command itself and remove any references to port from cache.xml. The problem will break a lot of existing scripts and, though we have a workaround, it will cause headaches for many when they encounter it. On Wed, Mar 21, 2018 at 2:52 PM, Dan Smith wrote: +1 Run geode-release-check. Verified no MD5 files in the distribution. -Dan On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker wrote: +1 - verified signatures and checksums - checked source release for binaries - basic gfsh testing - ran all the examples Anthony On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar wrote: This is the first release candidate for Apache Geode, version 1.5.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Friday, March 23, 1500 hrs US Pacific. *** It fixes 234 issues. release notes can be found at: https://issues.apache.org/jira/secure/ReleaseNote.jspa? projectId=12318420&version=12342395 Note that we are voting upon the source tags: rel/v1.5.0.RC1 https://github.com/apache/geode/tree/rel/v1.5.0.RC1 https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 Commit ID: 4ef51dacd79ff69336fb024f3d4b07271e90 (geode) 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) Source and binary files: https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 Maven staging repo: https://repository.apache.org/content/repositories/orgapachegeode-1038 Geode's KEYS file containing PGP keys we use to sign the release: https://github.com/apache/geode/blob/develop/KEYS Release Signed with Key: pub 4096R/18F902DB 2016-04-07 Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #865 was SUCCESSFUL (with 2381 tests). Change made by John Blum.
--- Spring Data GemFire > Nightly-ApacheGeode > #865 was successful. --- Scheduled with changes by John Blum. 2383 tests in total. https://build.spring.io/browse/SGF-NAG-865/ -- Code Changes -- John Blum (735740ae8905e0901c09da8c3689734c02731700): >DATAGEODE-91 - Impossible to define event filter for AsyncEventQueue. John Blum (8bfb2ec1eb3eb91be8fa987fb57e2c19b6ded9ca): >DATAGEODE-90 - Remove all git merge conflict tags in SDG source code Javadoc. -- This message is automatically generated by Atlassian Bamboo
Re: [VOTE] Apache Geode 1.5.0 RC1
This vote is now cancelled. Based on the comments, I will cut a new RC when we have fixes for GEODE-4913 and GEODE-4787. On Fri, Mar 23, 2018 at 3:11 PM Udo Kohlmeyer wrote: > -1 Due to the regression in functionality. GEODE-4913 > > @John, I agree, GEODE-4787 should be addressed with priority. > > --Udo > On 3/23/18 15:04, John Blum wrote: > > The same could be said of GEODE-4787. > > > > On Fri, Mar 23, 2018 at 2:58 PM, Anthony Baker > wrote: > > > >> Thanks for catching this Diane. I agree; we shouldn't break something > that > >> used to work. > >> > >> Anthony > >> > >> > >> On Mar 23, 2018, at 11:27 AM, Diane Hardman > wrote: > >> > >> -1 > >> I filed GEODE-4913 based on scripts I have that create 2 clusters > connected > >> by a WAN gateway on my local machine. > >> *Problem*: we are opening a cache-server on default port (40404) > >> irrespective of the fact that one is explicitly specified in cache.xml. > >> *symptoms*: users who start more than one Geode server on the same “box” > >> and use cache.xml to specify port would get bind exceptions when they > start > >> the second server. > >> *workaround*: > >>1. specify `--disable-default-server` on the `start server` command > >> while still specifying port in cache.xml. > >>2. specify port on the `start server` command itself and remove any > >> references to port from cache.xml. > >> > >> The problem will break a lot of existing scripts and, though we have a > >> workaround, it will cause headaches for many when they encounter it. > >> > >> On Wed, Mar 21, 2018 at 2:52 PM, Dan Smith wrote: > >> > >> +1 > >> > >> Run geode-release-check. Verified no MD5 files in the distribution. > >> > >> -Dan > >> > >> On Wed, Mar 21, 2018 at 11:57 AM, Anthony Baker > wrote: > >> > >> +1 > >> > >> - verified signatures and checksums > >> - checked source release for binaries > >> - basic gfsh testing > >> - ran all the examples > >> > >> Anthony > >> > >> On Mar 20, 2018, at 3:09 PM, Swapnil Bawaskar > >> > >> wrote: > >> > >> > >> This is the first release candidate for Apache Geode, version 1.5.0. > >> Thanks to all the community members for their contributions to this > >> release! > >> > >> *** Please download, test and vote by Friday, March 23, 1500 hrs > >> US Pacific. *** > >> > >> It fixes 234 issues. release notes can be found at: > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? > >> > >> projectId=12318420&version=12342395 > >> > >> > >> Note that we are voting upon the source tags: rel/v1.5.0.RC1 > >> https://github.com/apache/geode/tree/rel/v1.5.0.RC1 > >> https://github.com/apache/geode-examples/tree/rel/v1.5.0.RC1 > >> > >> Commit ID: > >> 4ef51dacd79ff69336fb024f3d4b07271e90 (geode) > >> 4941f05c86d928949fbcdb3fb12295ccecc219eb (geode-examples) > >> > >> Source and binary files: > >> https://dist.apache.org/repos/dist/dev/geode/1.5.0.RC1 > >> > >> Maven staging repo: > >> https://repository.apache.org/content/repositories/orgapachegeode-1038 > >> > >> > >> Geode's KEYS file containing PGP keys we use to sign the release: > >> https://github.com/apache/geode/blob/develop/KEYS > >> > >> Release Signed with Key: pub 4096R/18F902DB 2016-04-07 > >> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB > >> > > > > > >
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/348
