Failed: apache/geode-native#2059 (rel/v1.9.1.RC1 - add53da)

2019-08-22 Thread Travis CI
Build Update for apache/geode-native - Build: #2059 Status: Failed Duration: 1 hr, 39 mins, and 48 secs Commit: add53da (rel/v1.9.1.RC1) Author: Dave Barnes Message: User Guide: Add a link to the official XSD declarative cache schema View the changeset:

[VOTE] Apache Geode 1.9.1 RC1

2019-08-22 Thread Owen Nichols
Hello Geode dev community, This is a release candidate for Apache Geode, version 1.9.1.RC1. Thanks to all the community members for their contributions to this release! Please do a review and give your feedback. The deadline is 3PM PST Tue, August 27 2019. Release notes can be found at:

Errored: apache/geode-examples#339 (rel/v1.9.1.RC1 - 4eb6b07)

2019-08-22 Thread Travis CI
Build Update for apache/geode-examples - Build: #339 Status: Errored Duration: 13 secs Commit: 4eb6b07 (rel/v1.9.1.RC1) Author: Owen Nichols Message: Upgraded version number for releasing 1.9.1 View the changeset:

Re: Use of Internal JDK API

2019-08-22 Thread Joris Melchior
Kudos! Enjoyed my first cleaned up build! On Thu, Aug 22, 2019 at 12:46 PM Jacob Barrett wrote: > Hey Team, > > I just merged the fix for GEODE-130, an oldie but goodie, regarding all > those annoying internal JDK API warnings when compiling. Please don’t be > that person who puts more internal

Re: Gradle daemon crashed in PR precheckin

2019-08-22 Thread Jacob Barrett
The jobs just launch heavy lifter linux instances to run Gradle so this is just a pretty good sized plain old linux host. Sounds like maybe there are too many integration tests running in parallel eating up more memory than before. This may cause the virtual memory manager to panic and start

Re: Gradle daemon crashed in PR precheckin

2019-08-22 Thread Kirk Lund
I have multiple PRs submitted from multiple branches, all rebased etc. They all fail and the gradle process dies. The failure message (when there is one) always says the same thing... Some sort of environment issue is causing DistributedTestOpenJDK11 to fail [1] and the Gradle daemon to die (on

Re: [DISCUSS] Improvements on client function execution API

2019-08-22 Thread Jacob Barrett
> On Aug 21, 2019, at 8:49 AM, Alberto Gomez wrote: > 2. Timeout in ResultCollector::getResult() and Execution::execute() blocking > > Regarding the timeout in the ResultCollector::getResult() method problem and > the blocking/non-blocking confusion for Execution::execute() two alternatives

Re: [DISCUSS] Improvements on client function execution API

2019-08-22 Thread Jacob Barrett
> On Aug 22, 2019, at 11:55 AM, Jacob Barrett wrote: >> On Aug 22, 2019, at 11:29 AM, Dan Smith wrote: >> I took a look at the C++ API. The C++ API also has a >> ResultCollector.getResult(timeout) method. Does that timeout do anything, >> given that execute(timeout) already waited for the

Re: [DISCUSS] Improvements on client function execution API

2019-08-22 Thread Jacob Barrett
> On Aug 22, 2019, at 11:29 AM, Dan Smith wrote: > I took a look at the C++ API. The C++ API also has a > ResultCollector.getResult(timeout) method. Does that timeout do anything, > given that execute(timeout) already waited for the given timeout? The C++ client will wait on getResult until

Fwd: [DISCUSS] Improvements on client function execution API

2019-08-22 Thread Dan Smith
For the two new execute() methods you are proposing, are you also suggesting that they be implemented on the server? I took a look at the C++ API. The C++ API also has a ResultCollector.getResult(timeout) method. Does that timeout do anything, given that execute(timeout) already waited for the

Re: Gradle daemon crashed in PR precheckin

2019-08-22 Thread Jacob Barrett
I wonder if the auto merge creates something funky. Try rebasing or merging your branch first then push. > On Aug 22, 2019, at 11:11 AM, Bruce Schuchardt wrote: > > Using --no-daemon doesn't stop it from launching a daemon. It just tells it > to shut down the daemon when the build is done. >

Re: Gradle daemon crashed in PR precheckin

2019-08-22 Thread Bruce Schuchardt
Using --no-daemon doesn't stop it from launching a daemon.  It just tells it to shut down the daemon when the build is done. On 8/22/19 11:05 AM, Michael Oleske wrote: Not sure what the exact issue in this particular case, but I suspect we might not want to run with the Gradle daemon in CI.

Re: Gradle daemon crashed in PR precheckin

2019-08-22 Thread Michael Oleske
Not sure what the exact issue in this particular case, but I suspect we might not want to run with the Gradle daemon in CI. The Gradle daemon is really meant to help local building (see https://docs.gradle.org/current/userguide/gradle_daemon.html). That link explicitly calls out that you may not

Gradle daemon crashed in PR precheckin

2019-08-22 Thread Kirk Lund
Can someone please look at https://concourse.apachegeode-ci.info/builds/88869 and help me determine what happened to the Gradle daemon? > Task :geode-assembly:distributedTest > Task :geode-core:distributedTest

Use of Internal JDK API

2019-08-22 Thread Jacob Barrett
Hey Team, I just merged the fix for GEODE-130, an oldie but goodie, regarding all those annoying internal JDK API warnings when compiling. Please don’t be that person who puts more internal JDK API’s into the product. If you must please do it in the new geode-unsafe module. You will find that

Re: Need help: Jetty dunit tests blocking creation of geode-log4j

2019-08-22 Thread Kirk Lund
So far Jens and I are unable to reproduce these test failures [1]. This does not appear to be a test or java code problem. Based on google searches [2] [3], the cause might be either: 1) the distributed test job is out of swap space when the Tomcat/Jetty tests run 2) the

Fixed: apache/geode-native#2056 (develop - 16c207f)

2019-08-22 Thread Travis CI
Build Update for apache/geode-native - Build: #2056 Status: Fixed Duration: 1 hr, 32 mins, and 18 secs Commit: 16c207f (develop) Author: Alberto Gomez Message: GEODE-7113: Fix Rat error due to missing header in packer/windows/install-doxygen.ps1 (#512) View

Odg: geode-native ipv6

2019-08-22 Thread Mario Ivanac
Thanks for detailed answer. Šalje: Jacob Barrett Poslano: 22. kolovoza 2019. 6:56 Prima: dev@geode.apache.org Predmet: Re: geode-native ipv6 You might start by updating the framework’s Cluster class accept a hostname that would be used for both Locator and

Re: Rat check reporting error in travis-ci for geode-native

2019-08-22 Thread Alberto Gomez
I created the following PR to fix the Rat error. https://github.com/apache/geode-native/pull/512 Could someone review it and merge it if correct? Thanks, -Alberto G. On 21/8/19 23:59, Dan Smith wrote: > Hi Helena, > > I think the problem is that rat is currently broken on geode-native >

Re: [DISCUSS] Improvements on client function execution API

2019-08-22 Thread Alberto Gomez
Hi, Please, see my answers below. - Alberto On 21/8/19 20:30, Anilkumar Gingade wrote: > Just to be clear between java and native-client api: > > - Read timeout in function execution Java client API - This is to change > the java client behavior Yes > > And following are the native client