Skip to content
Snippets Groups Projects
  1. Jan 29, 2025
  2. Dec 01, 2022
  3. Nov 28, 2022
  4. Jul 09, 2021
    • Pierre-Yves David's avatar
      run-tests: introduce a `HGTEST_REAL_HG` variable for test · ee1fc8f970e6
      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
      ee1fc8f970e6
  5. Sep 29, 2019
  6. Oct 13, 2018
  7. Oct 08, 2018
    • Katsunori FUJIWARA's avatar
      tests: use NO_CHECK_EOF for fragments having intentional error · 89ba51c3e4f1
      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.
      89ba51c3e4f1
  8. Sep 19, 2018
  9. Oct 04, 2017
  10. Jul 02, 2017
  11. Jun 28, 2017
    • Adam Simpkins's avatar
      tests: use the system hg for examining the local repository · 6c113a7dec52
      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.
      6c113a7dec52
  12. Jun 04, 2017
    • Gregory Szorc's avatar
      tests: remove support for warned tests · 5af78c524f34
      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.
      5af78c524f34
  13. Sep 02, 2015
    • timeless's avatar
      run-tests: use $HGTEST_RUN_TESTS_PURE · 342ab95a1f4b
      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.
      342ab95a1f4b
  14. Jul 02, 2015
    • Katsunori FUJIWARA's avatar
      hghave: allow adding customized features at runtime · b94df10cc3b5
      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.
      b94df10cc3b5
  15. Jun 08, 2015
  16. Sep 26, 2010
  17. Apr 07, 2009
Loading