Project

General

Profile

Actions

Patch #42500

closed

Skip repository tests when the SCM client command is unavailable

Added by Go MAEDA 23 days ago. Updated 13 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
SCM
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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

Related to Redmine - Feature #33784: Update Mercurial repository support to be compatible with Python 3 and remove support for Mercurial < 5.1ClosedGo MAEDA

Actions
Actions #1

Updated by Go MAEDA 17 days ago

  • Target version changed from Candidate for next major release to 6.1.0

Setting the target version to 6.1.0.

Actions #2

Updated by Go MAEDA 14 days 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.

Actions #3

Updated by Go MAEDA 13 days ago

  • Status changed from Resolved to Closed

Merged the change into the stable branches in r23644 and r23645.

Actions #4

Updated by Go MAEDA 5 days ago

  • Related to Feature #33784: Update Mercurial repository support to be compatible with Python 3 and remove support for Mercurial < 5.1 added
Actions

Also available in: Atom PDF