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

2018-07-02 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/91

Build failed in Jenkins: Geode-nightly #1245

2018-07-02 Thread Apache Jenkins Server
See Changes: [github] GEODE-5352: testLocalDataContextWithColocation will now wait for result [karensmolermiller] GEODE-5350: User Guide: Specifying that 'statistics-enabled' parameter ---

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

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

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

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

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

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

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

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

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

2018-07-02 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/125

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

2018-07-02 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #966 was successful. --- Scheduled 2425 tests in total. https://build.spring.io/browse/SGF-NAG-966/ -- This

Re: Rat failure

2018-07-02 Thread Anthony Baker
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 belongs in the source tree. Anthony > On Jul 2, 2018, at 1:33 PM, Patrick Rhomberg wrote: > > We already have a rather extensive list

Re: Rat failure

2018-07-02 Thread Patrick Rhomberg
We already have a rather extensive list of excludes in gradle/rat.spotless. Another "*.rendered" could be added. On Mon, Jul 2, 2018 at 1:05 PM, Anthony Baker wrote: > The GEODE_USER_DIR on jenkins is set to the workspace so it’s leaving > behind a notification file that causes rat to fail. > >

Re: Requesting Pipeline Permissions

2018-07-02 Thread Patrick Rhomberg
I was under the impression that to actually deploy a pipeline, either as a new pipeline or an update to the existing ci/pipelines, would require additional permissions against the Concourse framework. If I am mistaken, apologies. I suppose one could modify the existing pipeline job scripts to

Re: Rat failure

2018-07-02 Thread Anthony Baker
The GEODE_USER_DIR on jenkins is set to the workspace so it’s leaving behind a notification file that causes rat to fail. Anthony > On Jul 2, 2018, at 9:13 AM, Kirk Lund wrote: > > Here's the rat failure on develop. I'm not sure what to make of it or what > changed... > > Unapproved licenses

Re: Requesting Pipeline Permissions

2018-07-02 Thread Alexander Murmann
Hi Patrick, The pipeline definition is in ci/pipelines. is that what you are looking for or do you need access to push pipeline changes? On Mon, Jul 2, 2018 at 12:08 PM, Patrick Rhomberg wrote: > Hello all. > > I'm currently investigating the state of our FlakyTest consumption, > believing th

Requesting Pipeline Permissions

2018-07-02 Thread Patrick Rhomberg
Hello all. I'm currently investigating the state of our FlakyTest consumption, believing that a lot of these markers are no longer accurate and that the annotated tests deserve promotion to the actual test jobs. [1] So as not to prematurely reintroduce flaky tests to the main body of the pipe

Re: trying to implement SSL configuration

2018-07-02 Thread Udo Kohlmeyer
Hi there Liron, Given that if you set a connection per thread, and by that I assume you mean that you set the min size on the thread pool to 0, you will incur the overhead of SSL negotiation EVERY time you create a connection. Now I'm not sure what your thread pool configuration is, I'm only

Rat failure

2018-07-02 Thread Kirk Lund
Here's the rat failure on develop. I'm not sure what to make of it or what changed... Unapproved licenses: /home/jenkins/jenkins-slave/workspace/Geode-nightly/notifications/4.8/release-features.rendered

Re: trying to implement SSL configuration

2018-07-02 Thread Anthony Baker
Why did you change the number of threads to 0 (and which setting did you change)? AFAIK this is not a requirement. Anthony > On Jul 1, 2018, at 10:29 PM, Liron Ben Ari wrote: > > Hi again... > After some functional test on the SSL configuration, we saw degradation of > 300% on performance!!