[
http://jira.codehaus.org/browse/SCM-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176524#action_176524
]
Mark Struberg commented on SCM-472:
-----------------------------------
Benjamin started a CI build with enabled TCK profile, which did also show 2
errors:
https://grid.sonatype.org/ci/job/scm/44/
A few TCKs cannot be run there because e.g. git is not setup on all boxes, but
SVN should definitely work there.
Can you please post the stack trace of the failed TCK or is it identical to
mine?
> some SVN TCK tests are broken
> -----------------------------
>
> Key: SCM-472
> URL: http://jira.codehaus.org/browse/SCM-472
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.2
> Environment: SVN 1.5.4 (r33841), Fedora 10
> 2.6.27.21-170.2.56.fc10.x86_64
> Reporter: Mark Struberg
> Attachments:
> org.apache.maven.scm.provider.svn.svnexe.command.changelog.SvnExeChangeLogCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest.txt
>
>
> The following TCK tests have errors:
> *
> testCheckOutCommandTest(org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest)
> *
> testChangeLogCommand(org.apache.maven.scm.provider.svn.svnexe.command.changelog.SvnExeChangeLogCommandTckTest)
> surefire logs attached
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
