Hi Anthony-

My apologies for the continued test failures on nightly.  I have not had a
chance get this build back in good working order yet, but I assure you
the "primary"
SDG build for Apache Geode <https://build.spring.io/browse/SGF-HEAD3> [1]
is alive and well (stable).

I suspect these failures are remnant from the Spring Bamboo CI (Groovy)
upgrade sometime ago, which caused unexplained Gradle (Groovy) build script
failures for all *Spring,* Gradle-based project builds. In fact, this build
was disabled for several months (until I just recently enabled it again)
 due to this Groovy/Gradle problem, which has since then been corrected.

Technically, all 11 test failures are failing because certain client/server
integration tests cannot fork the GemFire Server, most likely due to system
resource conflicts (e.g. port allocation, or something), possibly because
some GemFire Serve processes lingered after the Bamboo changes, I am not
sure.

I plan on doing 2 things...

1. Is have the infra team clean up any lingering processes from the SDG
build.

2. Ensure that all client/server resource allocations are properly
randomized (starting with these test failures).

Look for some resolution soon.

Thanks,
John


[1] https://build.spring.io/browse/SGF-HEAD3


On Tue, Jan 31, 2017 at 7:30 AM, Anthony Baker <aba...@pivotal.io> wrote:

> Anyone know why these 11 tests are failing? Was there a behavior change in
> Geode that caused this?  The last successful build was on 1/16.
>
> Anthony
>
>
> > Begin forwarded message:
> >
> > From: Spring CI <c...@spring.io>
> > Subject: [Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #455
> has FAILED (11 tests failed, no failures were new)
> > Date: January 30, 2017 at 2:51:39 PM PST
> > To: d...@geode.incubator.apache.org
> > Reply-To: dev@geode.apache.org
> >
> >
> > -----------------------------------------------------------------------
> > Spring Data GemFire > Nightly-ApacheGeode > #455 failed.
> > -----------------------------------------------------------------------
> > Scheduled
> > 11/1666 tests failed, no failures were new.
> >
> > https://build.spring.io/browse/SGF-NAG-455/
> >
> > ---------------------
> > Currently Responsible
> > ---------------------
> >
> > John Blum
> >
> >
> >
> > --------------
> > Failing Jobs
> > --------------
> >  - Default Job (Default Stage): 11 of 1666 tests failed.
> >
> >
> >
> >
> > --------------
> > Tests
> > --------------
> > Existing Test Failures (11)
> >   - ClientSubRegionTest: Org.springframework.data.gemfire.client.
> client sub region test
> >   - GemFireDataSourceTest: Org.springframework.data.gemfire.client. gem
> fire data source test
> >   - GemFireDataSourceWithLocalRegionTest: 
> > Org.springframework.data.gemfire.client.
> gem fire data source with local region test
> >   - ContinuousQueryListenerContainerNamespaceTest:
> Org.springframework.data.gemfire.config.xml. continuous query listener
> container namespace test
> >   - ClientCacheFunctionExecutionWithPdxIntegrationTest:
> Org.springframework.data.gemfire.function. client cache function
> execution with pdx integration test
> >   - FunctionExecutionTests: 
> > Org.springframework.data.gemfire.function.execution.
> function execution tests
> >   - FunctionIntegrationTests: 
> > Org.springframework.data.gemfire.function.execution.
> function integration tests
> >   - GemfireFunctionTemplateTests: 
> > Org.springframework.data.gemfire.function.execution.
> gemfire function template tests
> >   - ListenerContainerTests: Org.springframework.data.gemfire.listener.
> listener container tests
> >   - ContainerXmlSetupTest: 
> > Org.springframework.data.gemfire.listener.adapter.
> container xml setup test
> >   - RepositoryClientRegionTests: 
> > Org.springframework.data.gemfire.repository.config.
> repository client region tests
> >
> > --
> > This message is automatically generated by Atlassian Bamboo
>
>


-- 
-John
john.blum10101 (skype)

Reply via email to