1. 14 May, 2020 1 commit
    • Georges Racinet's avatar
      SourceHeptapod: make run_shell work · 757d36e282bc
      Georges Racinet authored
      Some callers want to pass a system user name, and we have to
      accept that for uniformity ('git' is been used as meaning
      "the default user", which is lame but that's another story)
  2. 12 May, 2020 6 commits
  3. 01 May, 2020 4 commits
  4. 29 Apr, 2020 3 commits
  5. 28 Apr, 2020 4 commits
  6. 27 Apr, 2020 5 commits
  7. 01 Mar, 2020 1 commit
  8. 06 Apr, 2020 1 commit
  9. 30 Mar, 2020 1 commit
    • Georges Racinet's avatar
      test for the gate-topics feature of hg-evolve 9.3.0 · aa4d04011cce
      Georges Racinet authored
      It seems that the topic aware client must have hg-evolve 9.3.0 in
      order to push the topic.
      For the time being, besides asserting that clients without the
      `topic` extension don't get topics, we check that the `topic`
      extension *alone* is enough to pull by revision, which is what the
      runners do.
  10. 26 Apr, 2020 1 commit
    • Georges Racinet's avatar
      Typo in test_404 creates a 403 · 25cf971a249b
      Georges Racinet authored
      In future Heptapod 0.13, the check for command existence happens first,
      leading to a 403 before the 404 is indeed generated.
      This doesn't break the test in Heptapod 0.12
  11. 03 Dec, 2019 1 commit
    • Georges Racinet's avatar
      Late conflict test case becomes inside file test · a1a28159cd06
      Georges Racinet authored
      As expected, once Mercurial does 3-way merges of files,
      it becomes very difficult to test that we don't have
      discrepancies with Git (and it would depend potentiallhy
      on bugs that have a tendency to be fixed).
      So better test that the in-file merge worked
  12. 05 Apr, 2020 1 commit
  13. 04 Apr, 2020 1 commit
    • Georges Racinet's avatar
      Hashed or not variants for tests of project transfers and destruction · 10fa8ba48883
      Georges Racinet authored
      Like the other ones, these are Docker only, since we don't have
      a real service manager in the source (GDK) case. And that's why they
      are additions to the existing test: we still want the basic form
      of the test to be executed in the source case.
      All of this is terribly inefficient, and it would also be better
      to minimize the number of restarts by grouping hashed and legacy
      storage tests together.
  14. 02 Apr, 2020 4 commits
  15. 01 Apr, 2020 3 commits
  16. 02 Apr, 2020 1 commit
    • Georges Racinet's avatar
      Group: ensuring directory existence while putting an HGRC · 70f8ec33c26e
      Georges Racinet authored
      With the hashed storage, the group directory is not guaranteed
      to exist any more. It wouldn't on plain GitLab if all the projects
      have been created with the hashed storage.
      Care must be taken to create with the proper system user,
      otherwise tests would break in non obvious ways, especially since
      Rails has automatic rollbacks (mostly silent) for what
      we're testing (transfers…)
  17. 01 Apr, 2020 2 commits