Broken: jinmeiliao/geode#292 (recreateCache - 4079d3e)

[Travis CI]

Build Update for jinmeiliao/geode
-

Build: #292
Status: Broken

Duration: 16 minutes and 43 seconds
Commit: 4079d3e (recreateCache)
Author: Jinmei Liao
Message: GEODE-4893: add test to make sure the callbacks will be loaded 
correctly

View the changeset: 
https://github.com/jinmeiliao/geode/compare/d2a942e8e502^...4079d3eb22d3

View the full build log and details: 
https://travis-ci.org/jinmeiliao/geode/builds/361888952?utm_source=email_medium=notification

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications







This email was sent to dev@geode.apache.org (mailto:dev@geode.apache.org)
unsubscribe from this list 
(http://clicks.travis-ci.com/track/unsub.php?u=14313403=5632e0dff89a4b9abf502cb13f80b845.J7HZbFy6S8dTlH7tD%2B7uJ8FM8HM%3D=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Ddev%2540geode.apache.org)

Geode unit tests 'develop/DistributedTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/247

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

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/381

Re: [DISCUSS]: Tests requiring external services

[Sean Goller]

I'm actually fine with putting it in AcceptanceTest for now.

Ideally I'd like to see something like JDBC connection strings that could
be passed in as properties via the command-line, and if they're not present
the relevant tests don't get run. That way the entity running the tests can
decide the best way to enable those tests.

On Tue, Apr 3, 2018 at 4:11 PM, Jens Deppe  wrote:

> I'm in favor of using docker for test isolation. We already have an
> 'AcceptanceTest' category which you might consider using instead of
> creating yet another category.
>
> --Jens
>
> On Tue, Apr 3, 2018 at 2:02 PM, Nick Reich  wrote:
>
> > Team,
> >
> > As part of validating the new JDBC connector for Geode, we have a need
> for
> > tests that involving connecting to specific databases (like MySQL and
> > Postgres) to validate proper function with those databases. Since these
> > tests require connecting to outside services, unlike existing Geode
> tests,
> > we are seeking suggestions on how to best incorporate such tests into
> > Geode. The approach we have taken so far is to utilize Docker (and Docker
> > Compose) to take care of spinning up our external services for the
> duration
> > of the tests. This, however requires that Docker and Docker Compose be
> > installed on any machine that the tests are run on. Additionally, the
> > Concourse pipeline for validating develop is incompatible with use of
> > Docker for distributed tests, due to the way they are already being run
> > within Docker containers of their own (it seems possible to make it work,
> > but would add overhead to all tests and would be a challenge to
> implement).
> >
> > To address these issues, we are considering having these tests run under
> a
> > new task, such as "serviceTest" (instead of IntegrationTest or
> > distributedTest). That way, developers could run all other tests normally
> > on their machines, only requiring Docker and Docker Compose if they wish
> to
> > run these specific tests. This would also allow them to be their own task
> > in Concourse, eliminating the issues that plague integrating these tests
> > there.
> >
> > Are there other ideas on how to manage these tests or concerns with the
> > proposed approach?
> >
>

Re: [DISCUSS]: Tests requiring external services

[Jens Deppe]

I'm in favor of using docker for test isolation. We already have an
'AcceptanceTest' category which you might consider using instead of
creating yet another category.

--Jens

On Tue, Apr 3, 2018 at 2:02 PM, Nick Reich  wrote:

> Team,
>
> As part of validating the new JDBC connector for Geode, we have a need for
> tests that involving connecting to specific databases (like MySQL and
> Postgres) to validate proper function with those databases. Since these
> tests require connecting to outside services, unlike existing Geode tests,
> we are seeking suggestions on how to best incorporate such tests into
> Geode. The approach we have taken so far is to utilize Docker (and Docker
> Compose) to take care of spinning up our external services for the duration
> of the tests. This, however requires that Docker and Docker Compose be
> installed on any machine that the tests are run on. Additionally, the
> Concourse pipeline for validating develop is incompatible with use of
> Docker for distributed tests, due to the way they are already being run
> within Docker containers of their own (it seems possible to make it work,
> but would add overhead to all tests and would be a challenge to implement).
>
> To address these issues, we are considering having these tests run under a
> new task, such as "serviceTest" (instead of IntegrationTest or
> distributedTest). That way, developers could run all other tests normally
> on their machines, only requiring Docker and Docker Compose if they wish to
> run these specific tests. This would also allow them to be their own task
> in Concourse, eliminating the issues that plague integrating these tests
> there.
>
> Are there other ideas on how to manage these tests or concerns with the
> proposed approach?
>

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

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #876 was successful.
---
Scheduled
2386 tests in total.

https://build.spring.io/browse/SGF-NAG-876/





--
This message is automatically generated by Atlassian Bamboo

[DISCUSS]: Tests requiring external services

[Nick Reich]

Team,

As part of validating the new JDBC connector for Geode, we have a need for
tests that involving connecting to specific databases (like MySQL and
Postgres) to validate proper function with those databases. Since these
tests require connecting to outside services, unlike existing Geode tests,
we are seeking suggestions on how to best incorporate such tests into
Geode. The approach we have taken so far is to utilize Docker (and Docker
Compose) to take care of spinning up our external services for the duration
of the tests. This, however requires that Docker and Docker Compose be
installed on any machine that the tests are run on. Additionally, the
Concourse pipeline for validating develop is incompatible with use of
Docker for distributed tests, due to the way they are already being run
within Docker containers of their own (it seems possible to make it work,
but would add overhead to all tests and would be a challenge to implement).

To address these issues, we are considering having these tests run under a
new task, such as "serviceTest" (instead of IntegrationTest or
distributedTest). That way, developers could run all other tests normally
on their machines, only requiring Docker and Docker Compose if they wish to
run these specific tests. This would also allow them to be their own task
in Concourse, eliminating the issues that plague integrating these tests
there.

Are there other ideas on how to manage these tests or concerns with the
proposed approach?