- Jan 29, 2025
-
-
Pierre-Yves David authored
This is a bit shooting in the dark, but this probably does not hurt to apply the same helper as the `test-run-tests.t` file.
-
- Dec 01, 2022
-
-
Anton Shestakov authored
log() in run-tests.py add a space to the end of all messages that it prints, and I missed this fact in my previous patch.
-
- Nov 28, 2022
-
-
Anton Shestakov authored
Couldn't reproduce locally, but apparently this message may occasionally pop up when running this test.
-
- Jul 09, 2021
-
-
Pierre-Yves David authored
It turns out that currently, `hg` and `which hg` can point to different things because `hg` is an alias… This is annoying because script and pieces of test are unknowingly using the wrong `hg`. We will fix it in another changeset. However some test actually need to use a real `hg` binary and not some `chg` or `rhg` equivalent. So we introduce a new variable with the right value and we put it to us in the appropriate location. Differential Revision: https://phab.mercurial-scm.org/D11049
-
- Sep 29, 2019
-
-
Gregory Szorc authored
This prevents the sub test harness from rebuilding Mercurial. It shaves ~30s from the test wall time on my machine. Differential Revision: https://phab.mercurial-scm.org/D6908
-
- Oct 13, 2018
-
-
Augie Fackler authored
Differential Revision: https://phab.mercurial-scm.org/D5085
-
- Oct 08, 2018
-
-
Katsunori FUJIWARA authored
Some test scripts are excluded in test-check-module-imports.t, because import-checker.py reports that code fragments embedded in these test scripts have syntax error. But these syntax error is intentional. This patch uses NO_CHECK_EOF instead of EOF as heredoc limit mark for such fragments, in order to make import-checker.py ignore them. NO_CHECK_EOF limit mark tells import-checker.py that this code fragment should be ignored, via testparseutil.py.
-
- Sep 19, 2018
-
-
Matt Harbison authored
Python3 defaults to installing under "Program Files".
-
- Oct 04, 2017
-
-
Augie Fackler authored
Some platforms (notably pkgsrc on NetBSD) only provide versioned Python interpreters (eg `python2.7` exists, but `python` does not), which exposes this error. We want to be running run-tests.py with the python given in $PYTHON, since that might be `pypy` or `python3`.
-
- Jul 02, 2017
-
-
Yuya Nishihara authored
-
- Jun 28, 2017
-
-
Adam Simpkins authored
Most test scripts use "hg" to interact with a temporary test repository. However a few tests also want to run hg commands to interact with the local repository containing the mercurial source code. Notably, many of the test-check-* tests want to check local files and commit messages. These tests were previously using the version of hg being tested to query the source repository. However, this will fail if the source repository requires extensions or other settings not supported by the version of mercurial being tested. The source repository was typically initially cloned using the system hg installation, so we should use the system hg installation to query it. There was already a helpers-testrepo.sh script designed to help cope with different requirements for the source repository versus the test repositories. However, it only handled the evolve extension. This new behavior works with any extensions that are different between the system installation and the test installation.
-
- Jun 04, 2017
-
-
Gregory Szorc authored
The previous changeset removed the last caller of addWarn(). So, we rip out that method and all the code related to tracking warned tests in the results system. There was even a comment saying we may want to fold warned tests into the "failed" state, which is what the previous changeset did.
-
- Sep 02, 2015
-
-
timeless authored
test-run-tests and test-hghave call run-tests; if you don't have a working build environment, and you are trying to use --pure, then if they don't use --pure or --with-hg, they'll break.
-
- Jul 02, 2015
-
-
Katsunori FUJIWARA authored
Before this patch, there is no way to add customized features to `hghave` without changing `hghave` and `hghave.py` themselves. This decreases reusability of `run-tests.py` framework for third party tools, because they may want to examine custom features at runtime (e.g. existence of some external tools). To allow adding customized features at runtime, this patch makes `hghave` import `hghaveaddon` module, only when `hghaveaddon.py` file can be found in directories below: - `TESTDIR` for invocation via `run-tests.py` - `.` for invocation via command line The path to the directory where `hghaveaddon.py` should be placed is added to `sys.path` only while importing `hghaveaddon`, because: - `.` may not be added to `PYTHONPATH` - adding additional path to `sys.path` may change behavior of subsequent `import` for other features `hghave` is terminated with exit code '2' at failure of `import hghaveaddon`, because exit code '2' terminates `run-tests.py` immediately. This is a one of preparations for issue4677.
-
- Jun 08, 2015
-
-
Matt Mackall authored
$TESTDIR is added to the path, so this is superfluous. Also, inconsistent use of quotes means we might have broken on tests with paths containing spaces.
-
- Sep 26, 2010
-
-
Matt Mackall authored
-
- Apr 07, 2009
-
-
Nicolas Dumazet authored
-