An error occurred fetching the project authors.
- 22 Oct, 2021 1 commit
-
-
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.
-
- 20 Apr, 2021 1 commit
-
-
Rémy Coutable authored
This makes sure unit and integration tests run when this file is touched. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 31 Mar, 2021 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 12 Feb, 2021 1 commit
-
-
Markus Koller authored
Auto-corrected with Rubocop
-
- 17 Dec, 2020 1 commit
-
-
Rémy Coutable authored
The _build dir is 211MB (uncompressed) but the executables are moved to the top gitaly folder after they're compiled, so there's no need to save the _build dir in the artifacts of the setup-test-env job. That should speed up the artifacts upload/download phases for setup-test-env and all the jobs that depend on it. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 16 Dec, 2020 1 commit
-
-
Stan Hu authored
In the test environment, we go through the trouble of spinning up Gitaly and Praefect, only to bypass Praefect entirely and go directly to the Gitaly socket. This renders the Praefect step useless and causes us to miss errors in proxying. To fix this, we now proxy all calls through Praefect and add a second Gitaly shard. This was discovered in https://gitlab.com/gitlab-org/gitaly/-/issues/3379.
-
- 25 Mar, 2020 1 commit
-
-
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.
-
- 14 May, 2018 1 commit
-
-
- 19 Dec, 2017 1 commit
-
-
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.
-
- 30 Nov, 2017 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 02 Aug, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 01 Aug, 2017 1 commit
-
-
Jacob Vosmaer authored
-