[
https://issues.apache.org/jira/browse/SCM-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961690#comment-17961690
]
ASF GitHub Bot commented on SCM-472:
------------------------------------
jira-importer commented on issue #691:
URL: https://github.com/apache/maven-scm/issues/691#issuecomment-2964613455
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
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: https://issues.apache.org/jira/browse/SCM-472
> Project: Maven SCM (Moved to GitHub Issues)
> 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
> Priority: Major
> Attachments:
> org.apache.maven.scm.provider.svn.svnexe.command.branch.SvnExeBranchCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.changelog.SvnExeChangeLogCommandTckTest.txt,
>
> org.apache.maven.scm.provider.svn.svnexe.command.checkout.SvnExeCheckOutCommandTckTest.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 was sent by Atlassian Jira
(v8.20.10#820010)
