Skip to content
Snippets Groups Projects
  1. Feb 09, 2021
    • Georges Racinet's avatar
      lint: new separate script · 6f66184b
      Georges Racinet authored
      with the exclusion rule, it was inconvenient to launch flake8 manually,
      I was always doing it by a copy-paste from the CI config file.
      6f66184b
  2. Jan 29, 2021
  3. Jan 18, 2021
  4. Jan 11, 2021
  5. Jan 08, 2021
  6. Jan 14, 2021
  7. Dec 18, 2020
  8. Jan 13, 2021
  9. Dec 16, 2020
  10. Jan 12, 2021
  11. Dec 15, 2020
  12. Jan 10, 2021
  13. Jan 06, 2021
    • Georges Racinet's avatar
      Bumped Gitaly proto to 13.7.1 · 0cba916a
      Georges Racinet authored
      Significant change to subset implemented in HGitaly:
      
        GitCommit message now has `tree_id` to be always filled. This
        can be indicative of a serious problem to circumvent on the
        client side (or not) before we implement the tree/blob API.
      0cba916a
  14. Dec 18, 2020
  15. Dec 20, 2020
    • Georges Racinet's avatar
      Gitaly comparison tests: complete fixture and example · 80edfd87
      Georges Racinet authored
      This provides the `gitaly_comparison` fixture, which
      stores channels to both Gitaly and HGitaly servers,
      as well as a whole hg-git mirroring setup, thanks to
      the `GitLabMirrorFixture` class provided by py-heptapod.
      
      As before, the fixture is declared in `conftest.py` (with
      the docstring now making fully sense), but the main class
      if elsewhere, namely in the `comparison` module.
      
      A first comparison test is written, which already uncovers
      two differences that should be fixed.
      80edfd87
    • Georges Racinet's avatar
      Gitaly comparison tests: GitalyServer and gitaly_channel fixture · 49d6e778
      Georges Racinet authored
      The GitalyServer class is able to configure, start and shutdown
      a Gitaly server, using the binaries from the Gitaly installation.
      
      The gitaly_channel fixture starts a `GitalyServer`, opens
      a client channel to it and waits for readiness.
      
      The fixture is defined in a package-local `conftest.py`, which
      has drawbacks, but it the only way to share it in practice.
      Most of the code is in the `gitaly` submodule anyway.
      
      Finally, `test_gitaly_server` ensures that this is working.
      The test is skipped if there is not known Gitaly installation,
      thanks to the utility provided at toplevel.
      
      Neither HGitaly nor Mercurial are involved at this point.
      49d6e778
    • Georges Racinet's avatar
      Gitaly comparison tests: discovery of Gitaly installation · 024370a0
      Georges Racinet authored
      The ultimate goal being to be able to compare HGitaly responses
      to Gitaly responses, this defines concepts to describe
      Gitaly installations and adds a discovery system.
      
      A Gitaly installation is at this point a directory with
      all the compiled executables and a `ruby` subdirectory for
      the gitaly-ruby side.
      
      The CI will run on a base image with an existing installation,
      which will be specified by passing the `GITALY_INSTALL_DIR`
      environment variable, interpreted by these tests as a strong
      promise, and triggering the coverage of `tests_with_gitaly`
      in the `run-all-tests` script.
      
      Otherwise, the tests are able to detect the common case where
      HGitaly is part of a HDK workspace and use the standard location
      for the Gitaly checkout (after minimal checking).
      024370a0
  16. Dec 19, 2020
  17. Dec 18, 2020
  18. Dec 17, 2020
  19. Dec 06, 2020
  20. Dec 05, 2020
  21. Dec 03, 2020
Loading