You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/08/05 20:40:00 UTC
[jira] [Closed] (SCM-955) gitexe and svnexe provider TCK tests fail
when path is absolute
[ https://issues.apache.org/jira/browse/SCM-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SCM-955.
------------------------------
Resolution: Fixed
Fixed with [a434fe6fffe110dc78e4c84f6c0d41e72a932e33|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=a434fe6fffe110dc78e4c84f6c0d41e72a932e33].
> gitexe and svnexe provider TCK tests fail when path is absolute
> ---------------------------------------------------------------
>
> Key: SCM-955
> URL: https://issues.apache.org/jira/browse/SCM-955
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe, maven-scm-provider-svn
> Affects Versions: 1.11.2
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 1.11.3
>
>
> I see the following with Git 2.20+ and Subversion 1.10+:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project maven-scm-provider-gitexe: There are test failures.
> [ERROR]
> [ERROR] Please refer to /var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/surefire-reports for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on project maven-scm-provider-svnexe: There are test failures.
> [ERROR]
> [ERROR] Please refer to /var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-svn/maven-scm-provider-svnexe/target/surefire-reports for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] -> [Help 1]
> [ERROR]
> {noformat}
> and
> {noformat}
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.871 s - in org.apache.maven.scm.provider.svn.svnexe.command.remoteinfo.SvnExeRemoteInfoCommandTckTest
> [INFO] Running org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoCommandTest
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 s - in org.apache.maven.scm.provider.svn.svnexe.command.info.SvnInfoCommandTest
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] SvnExeUpdateCommandTckTest>UpdateCommandTckTest.testUpdateCommand:168->ScmTestCase.assertPath:168 expected:<[/]src/main/java/org/Fo...> but was:<[]src/main/java/org/Fo...>
> [INFO]
> [ERROR] Tests run: 92, Failures: 1, Errors: 0, Skipped: 1
> [INFO]
> [INFO]
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.431 s <<< FAILURE! - in org.apache.maven.scm.provider.git.gitexe.command.update.GitExeUpdateCommandTckTest
> [ERROR] testUpdateCommand(org.apache.maven.scm.provider.git.gitexe.command.update.GitExeUpdateCommandTckTest) Time elapsed: 5.43 s <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[/]src/main/java/org/Fo...> but was:<[]src/main/java/org/Fo...>
> {noformat}
> I wonder why it worked all these years or it has not been properly tested. Will provide a PR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)