Looks like the test fails on my change, but it not the same failures.

I will looking into it, will need to upgrade my git

-D


On Tue, Jun 24, 2014 at 11:21 AM, Robert Scholte <rfscho...@apache.org>
wrote:

> According to https://builds.apache.org/view/M-R/view/Maven/job/maven-
> scm/changes and #847 being stable they should succeed.
> IIRC you should at least use version 1.8, although I'm not sure.
>
> Robert
>
> Op Tue, 24 Jun 2014 10:20:31 +0200 schreef Dan Tran <dant...@gmail.com>:
>
>
>  In another words,  are you able to get maven-scm-provider-gitexe built and
>> test passed?
>>
>> Thanks
>>
>> -D
>>
>>
>> On Mon, Jun 23, 2014 at 5:57 PM, Dan Tran <dant...@gmail.com> wrote:
>>
>>
>>> Hi I am running into test failures
>>>
>>> Linux: ( git version 1.7.9.5)
>>>
>>> Failed tests:
>>>
>>> GitCheckInCommandNoBranchTest.testCheckinNoBranch:75->
>>> ScmTestCase.assertResult
>>>
>>> GitCheckInCommandTest.testCheckinAfterRename:113->
>>> ScmTestCase.assertResultIsSu
>>>
>>>
>>> windows ( cygwin gitt version 1.7.9)
>>>
>>> Failed tests:
>>>
>>> GitCheckInCommandNoBranchTest.testCheckinNoBranch:64->
>>> checkoutRepo:93->ScmTestCase.assertResultIsSuccess:208
>>> The check out result success flag was false.
>>>
>>> GitCheckInCommandTest.testCheckinAfterRename:123->ScmTestCase.
>>> assertResultIsSuccess:208
>>> The check out result success flag was false.
>>>
>>> GitExeCheckOutCommandNoBranchTest.testCheckoutNoBranch:65->
>>> checkoutRepo:89->ScmTestCase.assertResultIsSuccess:208
>>> The check out result success flag was false.
>>>
>>> GitExeCheckOutCommandNoBranchTest.testDoubleCheckoutNoBranch:77-
>>> >checkoutRepo:89->ScmTestCase.assertResultIsSuccess:208
>>> The check out result success flag was false.
>>>
>>>
>>> Do I have the right setup?
>>>
>>> Thanks
>>>
>>> -D
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to