You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Travis CI <bu...@travis-ci.org> on 2016/03/11 22:25:21 UTC
Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Build Update for apache/incubator-geode
-------------------------------------
Build: #116
Status: Broken
Duration: 16 minutes and 7 seconds
Commit: 2fd9cc6 (feature/GEODE-1050)
Author: Kirk Lund
Message: Remove comments about case methods which only applies to hydra dunit
View the changeset: https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
View the full build log and details: https://travis-ci.org/apache/incubator-geode/builds/115418416
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
Travis CI is a free service provided to open source projects, which unlike
Jenkins is available for external (to Pivotal) contributors.
In any case, I have disabled Travis on all feature branches. Also disabled
for asf-site branch, since it contains our static website.
On Mon, Mar 14, 2016 at 2:39 PM, Kirk Lund <kl...@pivotal.io> wrote:
> I'm already using Jenkins to run check on my feature branches, so I don't
> really get any value from Travis. If it uses AWS or other $ resource, then
> I would suggest not running it automatically on feature branches. Perhaps
> there could be a way to manually initiate it rather than automatically
> running it for all feature branches?
>
> -Kirk
>
>
> On Mon, Mar 14, 2016 at 10:11 AM, Swapnil Bawaskar <sb...@pivotal.io>
> wrote:
>
> > Well, Travis runs build (./gradlew check) on pull requests as well as all
> > branches. Do we want to skip running travis on all feature branches?
> >
> > On Mon, Mar 14, 2016 at 9:00 AM, Anthony Baker <ab...@pivotal.io>
> wrote:
> >
> > > Ah, thanks for pointing that out Kirk, I missed the branch.
> > >
> > > I think this is setup so we get test coverage on pull requests.
> > >
> > > Anthony
> > >
> > > > On Mar 14, 2016, at 8:55 AM, Kirk Lund <kl...@pivotal.io> wrote:
> > > >
> > > > That branch isn't quite ready to merge to develop, but I did add a
> > > category
> > > > to that test on Friday.
> > > >
> > > > Is there some reason we're running Travis against feature branches
> that
> > > are
> > > > under active development?
> > > >
> > > > I commit/push in-progress work to facilitate testing on both my Mac
> and
> > > > Linux.
> > > >
> > > > -Kirk
> > > >
> > > > On Monday, March 14, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> > > >
> > > >> :geode-core:checkMissedTestsThe test
> > >
> >
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> > > does not include a junit category.
> > > >> org.gradle.api.GradleException: The test
> > >
> >
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> > > does not include a junit category.
> > > >>
> > > >> On Mar 11, 2016, at 1:25 PM, Travis CI <builds@travis-ci.org
> > > >> <javascript:_e(%7B%7D,'cvml','builds@travis-ci.org');>> wrote:
> > > >>
> > > >> Build Update for apache/incubator-geode
> > > >> -------------------------------------
> > > >>
> > > >> Build: #116
> > > >> Status: Broken
> > > >>
> > > >> Duration: 16 minutes and 7 seconds
> > > >> Commit: 2fd9cc6 (feature/GEODE-1050)
> > > >> Author: Kirk Lund
> > > >> Message: Remove comments about case methods which only applies to
> > hydra
> > > >> dunit
> > > >>
> > > >> View the changeset:
> > > >>
> > >
> >
> https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
> > > >>
> > > >> View the full build log and details:
> > > >> https://travis-ci.org/apache/incubator-geode/builds/115418416
> > > >>
> > > >> --
> > > >>
> > > >> You can configure recipients for build notifications in your
> > .travis.yml
> > > >> file. See https://docs.travis-ci.com/user/notifications
> > > >>
> > > >>
> > > >>
> > >
> > >
> >
>
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Kirk Lund <kl...@pivotal.io>.
I'm already using Jenkins to run check on my feature branches, so I don't
really get any value from Travis. If it uses AWS or other $ resource, then
I would suggest not running it automatically on feature branches. Perhaps
there could be a way to manually initiate it rather than automatically
running it for all feature branches?
-Kirk
On Mon, Mar 14, 2016 at 10:11 AM, Swapnil Bawaskar <sb...@pivotal.io>
wrote:
> Well, Travis runs build (./gradlew check) on pull requests as well as all
> branches. Do we want to skip running travis on all feature branches?
>
> On Mon, Mar 14, 2016 at 9:00 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > Ah, thanks for pointing that out Kirk, I missed the branch.
> >
> > I think this is setup so we get test coverage on pull requests.
> >
> > Anthony
> >
> > > On Mar 14, 2016, at 8:55 AM, Kirk Lund <kl...@pivotal.io> wrote:
> > >
> > > That branch isn't quite ready to merge to develop, but I did add a
> > category
> > > to that test on Friday.
> > >
> > > Is there some reason we're running Travis against feature branches that
> > are
> > > under active development?
> > >
> > > I commit/push in-progress work to facilitate testing on both my Mac and
> > > Linux.
> > >
> > > -Kirk
> > >
> > > On Monday, March 14, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> > >
> > >> :geode-core:checkMissedTestsThe test
> >
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> > does not include a junit category.
> > >> org.gradle.api.GradleException: The test
> >
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> > does not include a junit category.
> > >>
> > >> On Mar 11, 2016, at 1:25 PM, Travis CI <builds@travis-ci.org
> > >> <javascript:_e(%7B%7D,'cvml','builds@travis-ci.org');>> wrote:
> > >>
> > >> Build Update for apache/incubator-geode
> > >> -------------------------------------
> > >>
> > >> Build: #116
> > >> Status: Broken
> > >>
> > >> Duration: 16 minutes and 7 seconds
> > >> Commit: 2fd9cc6 (feature/GEODE-1050)
> > >> Author: Kirk Lund
> > >> Message: Remove comments about case methods which only applies to
> hydra
> > >> dunit
> > >>
> > >> View the changeset:
> > >>
> >
> https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
> > >>
> > >> View the full build log and details:
> > >> https://travis-ci.org/apache/incubator-geode/builds/115418416
> > >>
> > >> --
> > >>
> > >> You can configure recipients for build notifications in your
> .travis.yml
> > >> file. See https://docs.travis-ci.com/user/notifications
> > >>
> > >>
> > >>
> >
> >
>
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
Well, Travis runs build (./gradlew check) on pull requests as well as all
branches. Do we want to skip running travis on all feature branches?
On Mon, Mar 14, 2016 at 9:00 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Ah, thanks for pointing that out Kirk, I missed the branch.
>
> I think this is setup so we get test coverage on pull requests.
>
> Anthony
>
> > On Mar 14, 2016, at 8:55 AM, Kirk Lund <kl...@pivotal.io> wrote:
> >
> > That branch isn't quite ready to merge to develop, but I did add a
> category
> > to that test on Friday.
> >
> > Is there some reason we're running Travis against feature branches that
> are
> > under active development?
> >
> > I commit/push in-progress work to facilitate testing on both my Mac and
> > Linux.
> >
> > -Kirk
> >
> > On Monday, March 14, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> >
> >> :geode-core:checkMissedTestsThe test
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> does not include a junit category.
> >> org.gradle.api.GradleException: The test
> com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync
> does not include a junit category.
> >>
> >> On Mar 11, 2016, at 1:25 PM, Travis CI <builds@travis-ci.org
> >> <javascript:_e(%7B%7D,'cvml','builds@travis-ci.org');>> wrote:
> >>
> >> Build Update for apache/incubator-geode
> >> -------------------------------------
> >>
> >> Build: #116
> >> Status: Broken
> >>
> >> Duration: 16 minutes and 7 seconds
> >> Commit: 2fd9cc6 (feature/GEODE-1050)
> >> Author: Kirk Lund
> >> Message: Remove comments about case methods which only applies to hydra
> >> dunit
> >>
> >> View the changeset:
> >>
> https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
> >>
> >> View the full build log and details:
> >> https://travis-ci.org/apache/incubator-geode/builds/115418416
> >>
> >> --
> >>
> >> You can configure recipients for build notifications in your .travis.yml
> >> file. See https://docs.travis-ci.com/user/notifications
> >>
> >>
> >>
>
>
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Anthony Baker <ab...@pivotal.io>.
Ah, thanks for pointing that out Kirk, I missed the branch.
I think this is setup so we get test coverage on pull requests.
Anthony
> On Mar 14, 2016, at 8:55 AM, Kirk Lund <kl...@pivotal.io> wrote:
>
> That branch isn't quite ready to merge to develop, but I did add a category
> to that test on Friday.
>
> Is there some reason we're running Travis against feature branches that are
> under active development?
>
> I commit/push in-progress work to facilitate testing on both my Mac and
> Linux.
>
> -Kirk
>
> On Monday, March 14, 2016, Anthony Baker <ab...@pivotal.io> wrote:
>
>> :geode-core:checkMissedTestsThe test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
>> org.gradle.api.GradleException: The test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
>>
>> On Mar 11, 2016, at 1:25 PM, Travis CI <builds@travis-ci.org
>> <javascript:_e(%7B%7D,'cvml','builds@travis-ci.org');>> wrote:
>>
>> Build Update for apache/incubator-geode
>> -------------------------------------
>>
>> Build: #116
>> Status: Broken
>>
>> Duration: 16 minutes and 7 seconds
>> Commit: 2fd9cc6 (feature/GEODE-1050)
>> Author: Kirk Lund
>> Message: Remove comments about case methods which only applies to hydra
>> dunit
>>
>> View the changeset:
>> https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
>>
>> View the full build log and details:
>> https://travis-ci.org/apache/incubator-geode/builds/115418416
>>
>> --
>>
>> You can configure recipients for build notifications in your .travis.yml
>> file. See https://docs.travis-ci.com/user/notifications
>>
>>
>>
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Kirk Lund <kl...@pivotal.io>.
That branch isn't quite ready to merge to develop, but I did add a category
to that test on Friday.
Is there some reason we're running Travis against feature branches that are
under active development?
I commit/push in-progress work to facilitate testing on both my Mac and
Linux.
-Kirk
On Monday, March 14, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> :geode-core:checkMissedTestsThe test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
> org.gradle.api.GradleException: The test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
>
> On Mar 11, 2016, at 1:25 PM, Travis CI <builds@travis-ci.org
> <javascript:_e(%7B%7D,'cvml','builds@travis-ci.org');>> wrote:
>
> Build Update for apache/incubator-geode
> -------------------------------------
>
> Build: #116
> Status: Broken
>
> Duration: 16 minutes and 7 seconds
> Commit: 2fd9cc6 (feature/GEODE-1050)
> Author: Kirk Lund
> Message: Remove comments about case methods which only applies to hydra
> dunit
>
> View the changeset:
> https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
>
> View the full build log and details:
> https://travis-ci.org/apache/incubator-geode/builds/115418416
>
> --
>
> You can configure recipients for build notifications in your .travis.yml
> file. See https://docs.travis-ci.com/user/notifications
>
>
>
Re: Broken: apache/incubator-geode#116 (feature/GEODE-1050 - 2fd9cc6)
Posted by Anthony Baker <ab...@pivotal.io>.
:geode-core:checkMissedTestsThe test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
<>org.gradle.api.GradleException: The test com.gemstone.gemfire.test.dunit.internal.tests.JUnit4BasicDUnitTest.testInvokeLambdaAsync does not include a junit category.
<>
> On Mar 11, 2016, at 1:25 PM, Travis CI <bu...@travis-ci.org> wrote:
>
> Build Update for apache/incubator-geode
> -------------------------------------
>
> Build: #116
> Status: Broken
>
> Duration: 16 minutes and 7 seconds
> Commit: 2fd9cc6 (feature/GEODE-1050)
> Author: Kirk Lund
> Message: Remove comments about case methods which only applies to hydra dunit
>
> View the changeset: https://github.com/apache/incubator-geode/compare/3543e224c719...2fd9cc687cea
>
> View the full build log and details: https://travis-ci.org/apache/incubator-geode/builds/115418416
>
> --
>
> You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
>