1. 15 Apr, 2021 3 commits
  2. 13 Apr, 2021 4 commits
  3. 08 Apr, 2021 1 commit
  4. 05 Apr, 2021 5 commits
    • Georges Racinet's avatar
      HGitaly RSpec tests for Blob/Tree in fully native mode · 5a6c09aa65b2
      Georges Racinet authored
      The tests are conditionally skipped according to the
      HGitaly server version.
      
      There *is* a small discrepancy: line ending in commit message,
      but it doesn't actually lie in the code being tested, it should
      be a comparison case in `FindCommit`.
      
      Comparing with `HgGitRepository` is still useful for these
      tests at this point, because there is some plumbery involved
      on the Rails side for the HGitaly1 mode, and even in fully native
      mode, it's good to check that nothing goes wrong. When the dust
      settles on all this, though, it will be removable: actual thorough
      comparisons are to be done in the testing code of HGitaly.
      
      --HG--
      branch : heptapod
      5a6c09aa65b2
    • Georges Racinet's avatar
      RSpec: request and store HGitaly version on configuration object · ea7d9baf84e2
      Georges Racinet authored
      With this, the HGitaly version will be accessible as
      `RSpec.configuration.hgitaly_version`, and mostly used
      for conditional skipping, making hooking in Rails and
      landing in HGitaly less interdependent, provided new
      features in HGitaly come with an appropriate version
      change (doesn't have to be pushed to PyPI because the
      CI always run HGitaly from the head of the `default` or
      `stable` branch).
      
      The simplest syntax to skip RSpec tests is
      
      ```ruby
      
        if 'does something', skip: boolean_method
      
      ```
      
      but `boolean_method` would have to be a class method, and
      would turn out to be executed before `TestEnv`, hence before
      HGitaly is started. Therefore the `skip` method will have to
      be run from examples (and `before` hooks). The new
      `RSpec.configuration` method is a good way to access the version
      information. It's not lazy, but it's expected to be negligible
      compared to the huge startup time.
      
      --HG--
      branch : heptapod
      ea7d9baf84e2
    • Georges Racinet's avatar
      Merge from heptapod branch · 67810d172bf7
      Georges Racinet authored
      In release branches, tests are almost exclusively run from
      the CI, were the test harness improvement avoiding rebuild
      of Workhorse should entirely be bypassed.
      
      This merge will be validated by CI, hence making sure that
      we didn't introduce trouble for the next release.
      
      --HG--
      branch : heptapod-0-21
      67810d172bf7
    • Georges Racinet's avatar
      Merged test harness improvement from heptapod-stable · 7b2da10cf18f
      Georges Racinet authored
      --HG--
      branch : heptapod
      7b2da10cf18f
    • Georges Racinet's avatar
      RSpec tests harness: avoid useless Workhorse rebuilds · 22de94601b66
      Georges Racinet authored
      Since Workhorse upstream GitLab bundled Workhorse in the main
      repository, the test harness is using it, with a detection system
      to trigger rebuilds. Being based on Git, it wasn't working
      properly, resulting in `bin/rspec` always rebuilding Workhorse.
      
      Here we adapt the rebuild triggering logic to Mercurial
      
      One could expect a Makefile calling the Go compiler to run fast
      in any case, but that still took 14 seconds on my fast workstation,
      the irony being that the tests we are using in development of
      Heptapod are very seldom calling through Workhorse.
      
      --HG--
      branch : heptapod-stable
      22de94601b66
  5. 02 Apr, 2021 11 commits
  6. 01 Apr, 2021 5 commits
  7. 31 Mar, 2021 3 commits
  8. 30 Mar, 2021 8 commits