Commit graph

5 commits

Author SHA1 Message Date
GitLab Bot
5d75b2b9a9 Add latest changes from gitlab-org/gitlab@master 2020-03-25 18:08:10 +00:00
Jacob Vosmaer (out of office May 10-14)
d291f69fd9 Fix gitaly-ruby bundle poisoning in CI 2018-05-14 08:10:29 +00:00
Lin Jen-Shin
873bc3a685 Preserve gem path so that we use the same gems
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.
2017-12-19 17:41:59 +08:00
Jacob Vosmaer (GitLab)
a14bd24a02 Set an artificial $HOME for gitaly in test 2017-11-30 12:58:51 +00:00
Jacob Vosmaer
e99564568b CI fixes for gitaly-ruby 2017-08-01 10:48:46 +02:00