1. 23 Dec, 2019 1 commit
  2. 09 Dec, 2019 2 commits
  3. 02 Dec, 2019 1 commit
  4. 08 Dec, 2019 2 commits
    • overlaychangectx: adding attribute expected in future hg 5.3 · 5f9122431e1
      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 authored
    • compat: fixed access to status attributes · 3de074bf800
      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.
      Georges Racinet authored
  5. 22 Dec, 2019 2 commits
  6. 08 Dec, 2019 1 commit
    • heptapod-ci: fixed job for Mercurial 4.6 by silencing warnings · 3ca1f7cddb8
      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.
      Georges Racinet authored
  7. 07 Dec, 2019 1 commit
  8. 22 Dec, 2019 3 commits
  9. 08 Dec, 2019 2 commits
    • heptapod-ci: adding versions that pass the tests down to 4.3 · 9a29f59e108
      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
      runs.
      Georges Racinet authored
    • heptapod-ci: tests for one fixed and one moving Mercurial version · 78523621d50
      This Gitlab CI configuration launches the tests of the target hg-git revision
      against:
      
      - 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).
      Georges Racinet authored
  10. 20 Nov, 2019 2 commits
  11. 18 Nov, 2019 3 commits
  12. 07 Sep, 2019 1 commit
  13. 07 Aug, 2019 7 commits
  14. 01 Aug, 2019 2 commits
  15. 19 May, 2019 7 commits
  16. 16 May, 2019 1 commit
  17. 03 May, 2019 2 commits