You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/07/05 14:20:58 UTC
Build failed in Jenkins: Geode-nightly #520
See <https://builds.apache.org/job/Geode-nightly/520/>
------------------------------------------
[...truncated 537 lines...]
:geode-web:javadocJar
:geode-web:sourcesJar
:geode-web:war
:geode-web:signArchives SKIPPED
:geode-web-api:jar
:geode-web-api:javadoc
:geode-web-api:javadocJar
:geode-web-api:sourcesJar
:geode-web-api:war
:geode-web-api:signArchives SKIPPED
:geode-assembly:distTar
:geode-assembly:distZip
:geode-assembly:writeBuildInfo
:geode-assembly:srcDistTar
:geode-assembly:srcDistZip
:geode-assembly:signArchives SKIPPED
:geode-assembly:assemble
:geode-assembly:compileTestJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-assembly:processTestResources
:geode-assembly:testClasses
:geode-assembly:checkMissedTests
:geode-assembly:installDist
:geode-assembly:test
:geode-assembly:check
:geode-assembly:build
:geode-assembly:distributedTest
:geode-assembly:flakyTest
:geode-assembly:integrationTest
:geode-common:assemble
:geode-common:compileTestJava
:geode-common:processTestResources UP-TO-DATE
:geode-common:testClasses
:geode-common:checkMissedTests
:geode-common:test
:geode-common:check
:geode-common:build
:geode-common:distributedTest
:geode-common:flakyTest
:geode-common:integrationTest
:geode-core:assemble
:geode-core:checkMissedTests
:geode-core:test
:geode-core:check
:geode-core:build
:geode-core:distributedTest
:geode-core:flakyTest
:geode-core:integrationTest
com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest > testHistoryFileIsCreated FAILED
org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but was:<[// [failed] ]connect --fake-param...>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest > testHistoryFileDoesNotContainPasswords FAILED
org.junit.ComparisonFailure: expected:<[// [failed] ]connect --password=*...> but was:<[]connect --password=*...>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
3188 tests completed, 2 failed, 148 skipped
:geode-core:integrationTest FAILED
:geode-cq:assemble
:geode-cq:compileTestJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-cq:processTestResources
:geode-cq:testClasses
:geode-cq:checkMissedTests
:geode-cq:test
:geode-cq:check
:geode-cq:build
:geode-cq:distributedTest
:geode-cq:flakyTest
:geode-cq:integrationTest
:geode-json:assemble
:geode-json:compileTestJava UP-TO-DATE
:geode-json:processTestResources UP-TO-DATE
:geode-json:testClasses UP-TO-DATE
:geode-json:checkMissedTests UP-TO-DATE
:geode-json:test UP-TO-DATE
:geode-json:check
:geode-json:build
:geode-json:distributedTest UP-TO-DATE
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: <https://builds.apache.org/job/Geode-nightly/ws/geode-pulse/src/test/java/com/vmware/gemfire/tools/pulse/tests/PulseAbstractTest.java> uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:jar
:geode-rebalancer:javadoc
:geode-rebalancer:javadocJar
:geode-rebalancer:sourcesJar
:geode-rebalancer:signArchives SKIPPED
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan:compileTestJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web:compileTestJavaNote: <https://builds.apache.org/job/Geode-nightly/ws/geode-web/src/test/java/com/gemstone/gemfire/management/internal/cli/commands/DataCommandsOverHttpDistributedTest.java> uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-web:processTestResources UP-TO-DATE
:geode-web:testClasses
:geode-web:checkMissedTests
:geode-web:test
:geode-web:check
:geode-web:build
:geode-web:distributedTest
:geode-web:flakyTest
:geode-web:integrationTest
:geode-web-api:assemble
:geode-web-api:compileTestJava UP-TO-DATE
:geode-web-api:processTestResources UP-TO-DATE
:geode-web-api:testClasses UP-TO-DATE
:geode-web-api:checkMissedTests UP-TO-DATE
:geode-web-api:test UP-TO-DATE
:geode-web-api:check
:geode-web-api:build
:geode-web-api:distributedTest UP-TO-DATE
:geode-web-api:flakyTest UP-TO-DATE
:geode-web-api:integrationTest UP-TO-DATE
:combineReports
All test reports at <https://builds.apache.org/job/Geode-nightly/ws/build/reports/combined>
:extensions/geode-modules:precheckin
:extensions/geode-modules-assembly:precheckin
:extensions/geode-modules-hibernate:precheckin
:extensions/geode-modules-session:precheckin
:extensions/geode-modules-session-internal:precheckin
:extensions/geode-modules-tomcat7:precheckin
:geode-assembly:precheckin
:geode-common:precheckin
:geode-cq:precheckin
:geode-json:precheckin
:geode-junit:precheckin
:geode-lucene:precheckin
:geode-pulse:precheckin
:geode-rebalancer:precheckin
:geode-wan:precheckin
:geode-web:precheckin
:geode-web-api:precheckin
:extensions/geode-modules:uploadArchives
:extensions/geode-modules-assembly:uploadArchives SKIPPED
:extensions/geode-modules-hibernate:uploadArchives
:extensions/geode-modules-session:uploadArchives
:extensions/geode-modules-session-internal:uploadArchives
:extensions/geode-modules-tomcat7:uploadArchives
:geode-assembly:uploadArchives SKIPPED
:geode-common:uploadArchives
:geode-core:uploadArchives
:geode-cq:uploadArchives
:geode-json:uploadArchives
:geode-junit:uploadArchives
:geode-lucene:uploadArchives
:geode-pulse:uploadArchives
:geode-rebalancer:uploadArchives
:geode-wan:uploadArchives
:geode-web:uploadArchives
:geode-web-api:uploadArchives
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:integrationTest'.
> There were failing tests. See the report at: file://<https://builds.apache.org/job/Geode-nightly/ws/geode-core/build/reports/integrationTest/index.html>
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 10 hrs 36 mins 40.994 secs
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Compressed 255.94 MB of artifacts by 37.6% relative to #514
Recording test results
Jenkins build is back to normal : Geode-nightly #521
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Geode-nightly/521/changes>
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Swapnil Bawaskar <sb...@pivotal.io>.
I filed https://issues.apache.org/jira/browse/GEODE-1620 for the
unrecognized options issue.
On Tue, Jul 5, 2016 at 10:11 AM, Jinmei Liao <ji...@pivotal.io> wrote:
> Let's change the test first and then create a jira ticket to have gfsh fail
> on unrecognized options. Thanks!
>
> On Tue, Jul 5, 2016 at 9:57 AM, Kirk Lund <kl...@pivotal.io> wrote:
>
> > GfshHistoryJUnitTest is now failing after my commit on Friday.
> >
> > The test expects unrecognized options to cause the command to fail.
> >
> > Replacing our forked version of jopt-simple with a released version has
> > caused us to lose the ability to fail any command that contains
> > unrecognized arguments or unrecognized options. The latter could be
> > restored but it currently causes incorrect behavior with auto-complete.
> >
> > I propose changing the test to match the new behavior. My opinion is that
> > this is a better compromise that breaking auto-complete or spending
> further
> > unknown time devising additional workarounds. This is up for discussion
> so
> > please weigh in.
> >
> > -Kirk
> >
> > On Tuesday, July 5, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> >
> > > Thanks Jinmei! Can you share with the list the results of your
> > discussion?
> > >
> > > “If it doesn’t happen on the mailing list, it didn’t happen.” [1]
> > > —The Apache Way
> > >
> > > Anthony
> > >
> > > [1] https://community.apache.org/newbiefaq.html
> > >
> > > > On Jul 5, 2016, at 8:50 AM, Jinmei Liao <jiliao@pivotal.io
> > > <javascript:;>> wrote:
> > > >
> > > > It has something to do with the 7/1 checkin on gfshParser. I'll talk
> to
> > > the
> > > > team about if they want to revert the changes or fix the test if the
> > > change
> > > > is expected.
> > > >
> > > > On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao <jiliao@pivotal.io
> > > <javascript:;>> wrote:
> > > >
> > > >> I'll take a look.
> > > >>
> > > >> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <abaker@pivotal.io
> > > <javascript:;>> wrote:
> > > >>
> > > >>> This test is failing pretty regularly. Any volunteers to take a
> > look?
> > > >>>
> > > >>> Anthony
> > > >>>
> > > >>> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
> > > >>> jenkins@builds.apache.org <javascript:;>> wrote:
> > > >>>
> > > >>> geode-core:integrationTest
> > > >>>
> > > >>>
> > >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> > > >>> testHistoryFileIsCreated FAILED
> > > >>> org.junit.ComparisonFailure: expected:<[]connect --fake-param...>
> > but
> > > >>> was:<[// [failed] ]connect --fake-param...>
> > > >>> at org.junit.Assert.assertEquals(Assert.java:115)
> > > >>> at org.junit.Assert.assertEquals(Assert.java:144)
> > > >>> at
> > > >>>
> > >
> >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
> > > >>>
> > > >>>
> > >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> > > >>> testHistoryFileDoesNotContainPasswords FAILED
> > > >>> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
> > > >>> --password=*...> but was:<[]connect --password=*...>
> > > >>> at org.junit.Assert.assertEquals(Assert.java:115)
> > > >>> at org.junit.Assert.assertEquals(Assert.java:144)
> > > >>> at
> > > >>>
> > >
> >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Cheers
> > > >>
> > > >> Jinmei
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Cheers
> > > >
> > > > Jinmei
> > >
> > >
> >
>
>
>
> --
> Cheers
>
> Jinmei
>
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Jinmei Liao <ji...@pivotal.io>.
Let's change the test first and then create a jira ticket to have gfsh fail
on unrecognized options. Thanks!
On Tue, Jul 5, 2016 at 9:57 AM, Kirk Lund <kl...@pivotal.io> wrote:
> GfshHistoryJUnitTest is now failing after my commit on Friday.
>
> The test expects unrecognized options to cause the command to fail.
>
> Replacing our forked version of jopt-simple with a released version has
> caused us to lose the ability to fail any command that contains
> unrecognized arguments or unrecognized options. The latter could be
> restored but it currently causes incorrect behavior with auto-complete.
>
> I propose changing the test to match the new behavior. My opinion is that
> this is a better compromise that breaking auto-complete or spending further
> unknown time devising additional workarounds. This is up for discussion so
> please weigh in.
>
> -Kirk
>
> On Tuesday, July 5, 2016, Anthony Baker <ab...@pivotal.io> wrote:
>
> > Thanks Jinmei! Can you share with the list the results of your
> discussion?
> >
> > “If it doesn’t happen on the mailing list, it didn’t happen.” [1]
> > —The Apache Way
> >
> > Anthony
> >
> > [1] https://community.apache.org/newbiefaq.html
> >
> > > On Jul 5, 2016, at 8:50 AM, Jinmei Liao <jiliao@pivotal.io
> > <javascript:;>> wrote:
> > >
> > > It has something to do with the 7/1 checkin on gfshParser. I'll talk to
> > the
> > > team about if they want to revert the changes or fix the test if the
> > change
> > > is expected.
> > >
> > > On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao <jiliao@pivotal.io
> > <javascript:;>> wrote:
> > >
> > >> I'll take a look.
> > >>
> > >> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <abaker@pivotal.io
> > <javascript:;>> wrote:
> > >>
> > >>> This test is failing pretty regularly. Any volunteers to take a
> look?
> > >>>
> > >>> Anthony
> > >>>
> > >>> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
> > >>> jenkins@builds.apache.org <javascript:;>> wrote:
> > >>>
> > >>> geode-core:integrationTest
> > >>>
> > >>>
> > com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> > >>> testHistoryFileIsCreated FAILED
> > >>> org.junit.ComparisonFailure: expected:<[]connect --fake-param...>
> but
> > >>> was:<[// [failed] ]connect --fake-param...>
> > >>> at org.junit.Assert.assertEquals(Assert.java:115)
> > >>> at org.junit.Assert.assertEquals(Assert.java:144)
> > >>> at
> > >>>
> >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
> > >>>
> > >>>
> > com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> > >>> testHistoryFileDoesNotContainPasswords FAILED
> > >>> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
> > >>> --password=*...> but was:<[]connect --password=*...>
> > >>> at org.junit.Assert.assertEquals(Assert.java:115)
> > >>> at org.junit.Assert.assertEquals(Assert.java:144)
> > >>> at
> > >>>
> >
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Cheers
> > >>
> > >> Jinmei
> > >>
> > >
> > >
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> >
> >
>
--
Cheers
Jinmei
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Kirk Lund <kl...@pivotal.io>.
GfshHistoryJUnitTest is now failing after my commit on Friday.
The test expects unrecognized options to cause the command to fail.
Replacing our forked version of jopt-simple with a released version has
caused us to lose the ability to fail any command that contains
unrecognized arguments or unrecognized options. The latter could be
restored but it currently causes incorrect behavior with auto-complete.
I propose changing the test to match the new behavior. My opinion is that
this is a better compromise that breaking auto-complete or spending further
unknown time devising additional workarounds. This is up for discussion so
please weigh in.
-Kirk
On Tuesday, July 5, 2016, Anthony Baker <ab...@pivotal.io> wrote:
> Thanks Jinmei! Can you share with the list the results of your discussion?
>
> “If it doesn’t happen on the mailing list, it didn’t happen.” [1]
> —The Apache Way
>
> Anthony
>
> [1] https://community.apache.org/newbiefaq.html
>
> > On Jul 5, 2016, at 8:50 AM, Jinmei Liao <jiliao@pivotal.io
> <javascript:;>> wrote:
> >
> > It has something to do with the 7/1 checkin on gfshParser. I'll talk to
> the
> > team about if they want to revert the changes or fix the test if the
> change
> > is expected.
> >
> > On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao <jiliao@pivotal.io
> <javascript:;>> wrote:
> >
> >> I'll take a look.
> >>
> >> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <abaker@pivotal.io
> <javascript:;>> wrote:
> >>
> >>> This test is failing pretty regularly. Any volunteers to take a look?
> >>>
> >>> Anthony
> >>>
> >>> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
> >>> jenkins@builds.apache.org <javascript:;>> wrote:
> >>>
> >>> geode-core:integrationTest
> >>>
> >>>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> >>> testHistoryFileIsCreated FAILED
> >>> org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but
> >>> was:<[// [failed] ]connect --fake-param...>
> >>> at org.junit.Assert.assertEquals(Assert.java:115)
> >>> at org.junit.Assert.assertEquals(Assert.java:144)
> >>> at
> >>>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
> >>>
> >>>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> >>> testHistoryFileDoesNotContainPasswords FAILED
> >>> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
> >>> --password=*...> but was:<[]connect --password=*...>
> >>> at org.junit.Assert.assertEquals(Assert.java:115)
> >>> at org.junit.Assert.assertEquals(Assert.java:144)
> >>> at
> >>>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Cheers
> >>
> >> Jinmei
> >>
> >
> >
> >
> > --
> > Cheers
> >
> > Jinmei
>
>
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Anthony Baker <ab...@pivotal.io>.
Thanks Jinmei! Can you share with the list the results of your discussion?
“If it doesn’t happen on the mailing list, it didn’t happen.” [1]
—The Apache Way
Anthony
[1] https://community.apache.org/newbiefaq.html
> On Jul 5, 2016, at 8:50 AM, Jinmei Liao <ji...@pivotal.io> wrote:
>
> It has something to do with the 7/1 checkin on gfshParser. I'll talk to the
> team about if they want to revert the changes or fix the test if the change
> is expected.
>
> On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao <ji...@pivotal.io> wrote:
>
>> I'll take a look.
>>
>> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>>> This test is failing pretty regularly. Any volunteers to take a look?
>>>
>>> Anthony
>>>
>>> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
>>> jenkins@builds.apache.org> wrote:
>>>
>>> geode-core:integrationTest
>>>
>>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
>>> testHistoryFileIsCreated FAILED
>>> org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but
>>> was:<[// [failed] ]connect --fake-param...>
>>> at org.junit.Assert.assertEquals(Assert.java:115)
>>> at org.junit.Assert.assertEquals(Assert.java:144)
>>> at
>>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
>>>
>>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
>>> testHistoryFileDoesNotContainPasswords FAILED
>>> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
>>> --password=*...> but was:<[]connect --password=*...>
>>> at org.junit.Assert.assertEquals(Assert.java:115)
>>> at org.junit.Assert.assertEquals(Assert.java:144)
>>> at
>>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
>>>
>>>
>>>
>>
>>
>> --
>> Cheers
>>
>> Jinmei
>>
>
>
>
> --
> Cheers
>
> Jinmei
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Jinmei Liao <ji...@pivotal.io>.
It has something to do with the 7/1 checkin on gfshParser. I'll talk to the
team about if they want to revert the changes or fix the test if the change
is expected.
On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao <ji...@pivotal.io> wrote:
> I'll take a look.
>
> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
>> This test is failing pretty regularly. Any volunteers to take a look?
>>
>> Anthony
>>
>> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>>
>> geode-core:integrationTest
>>
>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
>> testHistoryFileIsCreated FAILED
>> org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but
>> was:<[// [failed] ]connect --fake-param...>
>> at org.junit.Assert.assertEquals(Assert.java:115)
>> at org.junit.Assert.assertEquals(Assert.java:144)
>> at
>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
>>
>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
>> testHistoryFileDoesNotContainPasswords FAILED
>> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
>> --password=*...> but was:<[]connect --password=*...>
>> at org.junit.Assert.assertEquals(Assert.java:115)
>> at org.junit.Assert.assertEquals(Assert.java:144)
>> at
>> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
>>
>>
>>
>
>
> --
> Cheers
>
> Jinmei
>
--
Cheers
Jinmei
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Jinmei Liao <ji...@pivotal.io>.
I'll take a look.
On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <ab...@pivotal.io> wrote:
> This test is failing pretty regularly. Any volunteers to take a look?
>
> Anthony
>
> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
> geode-core:integrationTest
>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> testHistoryFileIsCreated FAILED
> org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but
> was:<[// [failed] ]connect --fake-param...>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest >
> testHistoryFileDoesNotContainPasswords FAILED
> org.junit.ComparisonFailure: expected:<[// [failed] ]connect
> --password=*...> but was:<[]connect --password=*...>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)
>
>
>
--
Cheers
Jinmei
Re: Build failed in Jenkins: Geode-nightly #520
Posted by Anthony Baker <ab...@pivotal.io>.
This test is failing pretty regularly. Any volunteers to take a look?
Anthony
> On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server <je...@builds.apache.org> wrote:
>
> geode-core:integrationTest
>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest > testHistoryFileIsCreated FAILED
> org.junit.ComparisonFailure: expected:<[]connect --fake-param...> but was:<[// [failed] ]connect --fake-param...>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileIsCreated(GfshHistoryJUnitTest.java:75)
>
> com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest > testHistoryFileDoesNotContainPasswords FAILED
> org.junit.ComparisonFailure: expected:<[// [failed] ]connect --password=*...> but was:<[]connect --password=*...>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest.testHistoryFileDoesNotContainPasswords(GfshHistoryJUnitTest.java:84)