1. 03 Jul, 2019 1 commit
  2. 19 Jun, 2018 1 commit
  3. 01 Mar, 2020 1 commit
  4. 11 Jan, 2020 1 commit
  5. 08 Dec, 2019 2 commits
    • Georges Racinet's avatar
      overlaychangectx: adding attribute expected in future hg 5.3 · 5f9122431e18
      Georges Racinet authored
      This `_maybe_filtered` attribute has been introduced in Mercurial
      revision 8a37203ab1d5, and is henceforth expected by some callers.
      Adding it inconditionnally should not harm on previous versions: it
      would simply not get used.
    • Georges Racinet's avatar
      compat: fixed access to status attributes · 3de074bf8003
      Georges Racinet authored
      as of Mercurial c5548b0b6847, status is no more a tuple. Its attributes
      must be accessed explicitely.
      These attributes have been available since 3.2 (introduced in cb4449921a1d),
      so that we don't need to introduce a conditional such as `isinstance(tuple)`.
      Technically, these are slots, so that performance-wise, such prefetching in
      locals should not matter, but they make for the smallest changeset.
  6. 22 Dec, 2019 2 commits
    • Georges Racinet's avatar
      heptapod-ci: a job for current default branch of Mercurial · 1aa74ab163c0
      Georges Racinet authored
      Currently, the tests fail for this version of Mercurial, hence we'll
      add the job once they are fixed.
      Ideally, this changeset should be rebased on top of a revision that
      fixes hg-git for Mercurial default, hence validating the fix.
    • Georges Racinet's avatar
      heptapod-ci: protecting outer commands from PYTHONPATH · 0259c8aa557a
      Georges Racinet authored
      All commands that make use of Python and are meant to retrieve or prebuild
      code should not themselves use potentially incompatible stuff from
      For instance, updating Mercurial to 'stable' should not risk using a
      random version of the mercurial Python package. It must instead use
      the one provided system-wide, that is consistent with the `hg` command.
  7. 08 Dec, 2019 1 commit
    • Georges Racinet's avatar
      heptapod-ci: fixed job for Mercurial 4.6 by silencing warnings · 3ca1f7cddb86
      Georges Racinet authored
      Without these two flags, we get the following:
        devel-warn: changectx.__init__ is getting more limited, see context.changectxdeprecwarn() for details
        (compatibility will be dropped after Mercurial-4.6, update your code.) at: /tmp/hgtests.ShCiwV/install/lib/python/mercurial/localrepo.py:849 (__contains__)
      after inspection of the code paths, it turns out that these are self-inflicted
      Mercurial warnings. This can be seen with test-clone.t, the whole traceback
      does not involve hg-git at all.
      So the only practical solution we have is to silence the warnings.
      I think it's acceptable as long as it's for this single version and in
      particulary not for any version under active development or maintenance.
  8. 07 Dec, 2019 1 commit
    • Georges Racinet's avatar
      heptapod-ci: job for Mercurial 4.6 · 7f5c876cd679
      Georges Racinet authored
      Noticed that some tests don't pass while working on the CI configuration.
      Ideally, this changeset should be rebased on top of a revision that
      fixes hg-git for Mercurial default, hence validating the fix.
  9. 22 Dec, 2019 3 commits
    • Georges Racinet's avatar
      tests: skipping test-illegal-contents on Git >= 2.24 · ed3767c0bc92
      Georges Racinet authored
      Git behaviour and output has changed, in a way that seems
      hard to reconcile with glob or regex patterns.
      we'll probably have to write an entire variant of this test.
      In the meanwhile, this skipping should restore the main CI runs.
    • Georges Racinet's avatar
      tests: `gitbefore` feature family · a6ddd3f835af
      Georges Racinet authored
      This is to run some tests only if the Git version is smaller than
      the given one.
    • Georges Racinet's avatar
      ci: using hg-git own test runner with prebuilt Mercurial · 5691890fa36f
      Georges Racinet authored
      Now that Octobus images for CI of Mercurial extensions against
      a fixed Mercurial version have a prebuilt Mercurial,
      we can just use it, saving some
      computing resources and waiting time.
      Also, this makes sure that the CI will use the test runner
      provided with hg-git, which will avoid problems on older versions
      (seen one with a new skip rule).
      To avoid inconsistencies (hg executable importing the system wide
      mercurial Python package), we need to also set PYTHONPATH, and
      conversely unset it to run pip in before_script
  10. 08 Dec, 2019 2 commits
    • Georges Racinet's avatar
      heptapod-ci: adding versions that pass the tests down to 4.3 · 9a29f59e1081
      Georges Racinet authored
      Currently, hg-git does not pass the tests for
      - Mercurial 4.6
      - the head of Mercurial default branch
      In order to start benefit of the CI and enforcing that contributions must
      pass it, we will therefore add jobs for these two versions in separate
      topics and Merge Requests.
      Also worth of note is that 5.2 can have new point releases that will be
      provided in the base Docker image. Hence we don't exclude it from nightly
    • Georges Racinet's avatar
      heptapod-ci: tests for one fixed and one moving Mercurial version · 78523621d506
      Georges Racinet authored
      This Gitlab CI configuration launches the tests of the target hg-git revision
      - the current head of Mercurial `stable` branch
      - a fixed Mercurial version, assumed not to change anymore
      We'll add more versions in a follow-up.
      ## `image`
      All operations after cloning of the tested `hg-git` revision happen in a
      fresh container started on this Docker image.
      The ones we use are available on Docker Hub,
      with definitions in https://dev.heptapod.net/octobus/ci-dockerfiles
      ## `before_script`
      The `before_script` at toplevel will be executed for each job.
      In later GitLab versions, we'll also have a `default` toplevel key that will
      allow to specifiy a common value for `script` (and `before_script`, deprecating
      its use at toplevel).
      The installations performed by this `before_script` would be better provided
      by a dedicated series of base Docker images, saving resources and execution
      time. If that is done, we are able to remove this `before_script` altogether.
      ## `except`
      In a first installment, we'll add a nightly scheduler after landing of this
      configuration. We don't want it to relaunch tests against Mercurial versions
      that don't change
      ## `script`
      This form has the tests launcher build and use the appropriate Mercurial
      revision (information about it displayed first).
  11. 20 Nov, 2019 2 commits
  12. 18 Nov, 2019 3 commits
  13. 07 Sep, 2019 1 commit
  14. 07 Aug, 2019 7 commits
  15. 01 Aug, 2019 2 commits
  16. 19 May, 2019 7 commits
  17. 16 May, 2019 1 commit
  18. 03 May, 2019 2 commits