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 <[email protected]> wrote:

> I'll take a look.
>
> On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker <[email protected]> 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 <
>> [email protected]> 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

Reply via email to