Skip to content
Snippets Groups Projects
  1. May 19, 2021
  2. Apr 15, 2021
  3. May 17, 2021
  4. May 04, 2021
  5. Mar 29, 2021
  6. May 04, 2021
  7. May 03, 2021
  8. May 17, 2021
  9. May 03, 2021
    • Pierre-Yves David's avatar
      side-data: drop the associated config and requirements · 21b3e611
      Pierre-Yves David authored
      This is no longer and extensions of revlog v1, but a part of revlog v2. We no
      longer needs independent config and requirement management for that.
      
      Differential Revision: https://phab.mercurial-scm.org/D10620
      21b3e611
    • Pierre-Yves David's avatar
      test: no longer directly use the sidedata config and requirements · 0dedd3d0
      Pierre-Yves David authored
      They are on their way out, so we simply use revlogv2 in these cases.
      
      Some test does not requires explicite request for the revlogv2 format since the
      upgrade to a side-data-capable format is impled by
      `exp-use-copies-side-data-changeset`.
      
      Differential Revision: https://phab.mercurial-scm.org/D10618
      0dedd3d0
    • Pierre-Yves David's avatar
      sidedata: use revlogv2 requirement in the test helper · 8505d239
      Pierre-Yves David authored
      We are about to drop the requirement dedicated to sidedata (since revlogv2 will
      support them unconditionally and previous version will not.).
      
      To prepare this more we adapt the test code to not use that requirements.
      
      Differential Revision: https://phab.mercurial-scm.org/D10615
      8505d239
    • Pierre-Yves David's avatar
      upgrade: display sidedata before upgrade · 281060fb
      Pierre-Yves David authored
      This is a small gratuitous change that help making the test simpler to
      understand on its own.
      
      Differential Revision: https://phab.mercurial-scm.org/D10614
      281060fb
    • Pierre-Yves David's avatar
      requirements: no longer drop `generaldelta` requirement with revlogv2 · 5eb5b866
      Pierre-Yves David authored
      A repository could use a mix of revlogv1 and revlogv2, making the requirements
      still necessary. Overall we should move away from the "requirements" file being
      used a way to configure the repository and stick to it "what do you need to
      access this repository". However this is a wider work for another time.
      
      In addition the logic we just dropped was confusing the `hg debugformat`
      command, breaking the upgrade code and inconsistent (eg: `sparse-revlog` is also
      implied by `revlogv2`).
      
      Finally, multiple other config option would imply the use of the `revlogv2`
      requirements, without drop the `generaldelta` one, leading to more
      inconsistency.
      
      Differential Revision: https://phab.mercurial-scm.org/D10612
      5eb5b866
    • Pierre-Yves David's avatar
      revlog: introduce a mandatory `_writing` context to update revlog content · 906a7bca
      Pierre-Yves David authored
      Before this change, various revlog methods where managing the opening and
      closing of the revlog files manually and passing the file descriptor alors the
      call path. To simplify the tracking of the write operation by a future docket,
      we need something more organised. As a result, we introduce a `revlog._writing`
      context manager that will wrap each revlog update operation. The file
      descriptor are kept in the existing `revlog._writinghandles` parameter that
      was already used by the `addgroup` logic.
      
      All this change is internal to the revlog only, the "public" interface is not
      affected. The `addrevision` and `addgroup` logic are still responsible for
      setup up this context. However this new context give us multiple benefits:
      
      * all writer use a same, unified, logic,
      * this context is programmatically enforced,
      * each write "session" as a clearly identified start and end.
      
      The post-pull sidedata update logic is still doing writing by end and will be
      adjusted in a later changesets.
      
      This change affect the concurrency checker test, because register the state of
      the file in the transaction sooner in `addrevision` (about as early as what
      `addgroup` would do), so the abort is rollbacking the other commit. I don't want
      to weaken the current main logic.
      
      Differential Revision: https://phab.mercurial-scm.org/D10605
      906a7bca
  10. May 07, 2021
  11. May 05, 2021
    • Matt Harbison's avatar
      run-tests: fix whitelist/blacklist with directories on Windows · dff19fe2
      Matt Harbison authored
      The file name is resolved with `os.path.relpath()` in the `Test` constructor,
      which yields `\` on Windows.  That doesn't match the `/` separator when using
      MSYS tools to build the list, and it isn't obvious that this is the problem
      because directory separators can mostly be used interchangeably.  The
      `--test-list` argument already seems to be properly handled.
      dff19fe2
  12. Mar 12, 2021
  13. May 10, 2021
  14. May 11, 2021
  15. Apr 15, 2021
  16. May 11, 2021
  17. May 08, 2021
    • Matt Harbison's avatar
      run-tests: use the same python version for shebang lines on Windows · 6f976d54
      Matt Harbison authored
      The latest py3 is used if the minor number isn't specified.  After running the
      script to install all of the build dependencies, that moved the default from 3.8
      to 3.9 on the CI system.  That in turn caused a bunch of tests to be skipped
      that were running prior, even when the test runner was invoked with `py -3.8`.
      While we should almost always use the latest version, we really shouldn't make
      it hard to test different versions or allow things to randomly break in subtle
      ways like that.
      
      Differential Revision: https://phab.mercurial-scm.org/D10702
      6f976d54
  18. May 06, 2021
  19. May 03, 2021
Loading