Actions
Patch #42500
closedSkip repository tests when the SCM client command is unavailable
Description
Repository tests can fail if the required SCM client command is unavailable or outdated (e.g., Mercurial 5.1 or higher is required for the current trunk), resulting in a large number of test failures.
To reproduce the issue, add the following lines to config/configuration.yml
and run the repository tests.
scm_subversion_command: /tmp/invalid-svn scm_mercurial_command: /tmp/invalid-hg scm_git_command: /tmp/invalid-git scm_cvs_command: /tmp/invalid-cvs scm_bazaar_command: /tmp/invalid-bzr
The attached patch modifies the test setup so that repository tests are skipped when the corresponding SCM client command is not available. This avoids test failures in such environments.
This issue is related to #33784#note-24.
Files
Related issues
Updated by Go MAEDA about 1 month ago
- Target version changed from Candidate for next major release to 6.1.0
Setting the target version to 6.1.0.
Updated by Go MAEDA about 1 month ago
- Category changed from Code cleanup/refactoring to SCM
- Status changed from New to Resolved
- Assignee set to Go MAEDA
- Target version changed from 6.1.0 to 6.0.5
Committed the patch in r23618.
Updated by Go MAEDA about 1 month ago
- Related to Feature #33784: Update Mercurial repository support to be compatible with Python 3 and remove support for Mercurial < 5.1 added
Actions