An error occurred fetching the project authors.
  1. 22 Oct, 2021 1 commit
    • Toon Claes's avatar
      test: Inject bundler config in environment · e94f41c9
      Toon Claes authored
      Setting up and spawning Gitaly in tests needs to have some Bundler
      settings configured. Until now this was done by writing to the local
      config file in the ruby directory inside the gitaly dir used in test.
      
      This method didn't seem to be robust for all our user and
      use-cases (i.e. CI), because this configuration _could_ be done from
      different places.
      
      To make the situation more predictable, this change injects all Bundler
      configuration through environment variables instead. It sets
      BUNDLE_IGNORE_CONFIG to make sure any existing configuration written to
      file is ignored, this includes the .bundle/config inside the project and
      possibly in the user's $HOME directory.
      e94f41c9
  2. 20 Apr, 2021 1 commit
  3. 31 Mar, 2021 1 commit
  4. 12 Feb, 2021 1 commit
  5. 17 Dec, 2020 1 commit
  6. 16 Dec, 2020 1 commit
  7. 25 Mar, 2020 1 commit
    • John Cai's avatar
      Add praefect as a socket for tests · be578468
      John Cai authored
      Praefect functions as a proxy, but there are a few RPCs that are only in
      praefect and do not get proxied to gitaly. To test functionality that
      hits these RPCs, we need a way to hit a praefect instance that talks to
      a gitaly instance.
      
      This MR sets up praefect in front of the existing gitaly that is used in
      tests.
      be578468
  8. 14 May, 2018 1 commit
  9. 19 Dec, 2017 1 commit
    • Lin Jen-Shin's avatar
      Preserve gem path so that we use the same gems · 873bc3a6
      Lin Jen-Shin authored
      Without this patch, I would end up with:
      
      ```
      An error occurred in a `before(:suite)` hook.
      Failure/Error: raise "could not connect to gitaly at #{socket.inspect} after #{sleep_time} seconds"
      
      RuntimeError:
        could not connect to gitaly at "tmp/tests/gitaly/gitaly.socket" after 10 seconds
      ```
      
      Digging into it, it's because `scripts/gitaly-test-spawn` could not
      spawn the process, because it cannot find the installed gems.
      
      I personally installed all my gems under $HOME, namely with:
      
      * `gem install rake --user-install` or:
      * `bundle install --path ~/.gem`
      
      The gems would be installed to `~/.gem/ruby/2.4.0/gems`, where
      the version is Ruby ABI version.
      
      Now we're changing $HOME, making RubyGems think that the gems
      would be installed to `tmp/tests/ruby/2.4.0/gems` which is
      apparently not the case.
      
      In order to workaround this, we could preserve $GEM_PATH
      populated by RubyGems, ignoring the default path based on $HOME.
      873bc3a6
  10. 30 Nov, 2017 1 commit
  11. 02 Aug, 2017 1 commit
  12. 01 Aug, 2017 1 commit