Project

General

Profile

Actions

Bug #13441

closed

building - GIT variable, ruby, rubygems tests

Added by MSP-Greg (Greg L) almost 7 years ago. Updated over 4 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.5.0dev (2017-04-15 trunk 58363) [x64-mingw32]
[ruby-core:80697]

Description

As I've mentioned before, I've been building and using MinGW trunk builds for several months. I've needed a few patches to stop segv issues, but recent builds have had approx ten combined failures and errors.

I've never had issues with test and test-rubyspec, so I only run test-all. I also set --show-skip.

RubyGems uses git in its testing, and can read an environment variable for its location. I assume many windows users have a git install from https://git-scm.com/ (not the GitHub UI) installed, which defaults to an install location with a space in the path. Also, the MinGW / msys2 build environment does not reliably read the native PATH variable (could be a spaces issue).

The RubyGems tests allow one to set a GIT environment variable for the location of the git executable. I added a 'non-space' symlink to git in my build system, and added it as an environment variable. Without it, several of the RubyGems tests skip with the following message -

cannot find git executable, use GIT environment variable to set

I haven't looked thru all the code, but it appears there have been several recent commits that may address refereshing the ruby / spec repo. These seem to conflict with the RubyGems tests use of the variable.

FYI, a while ago I patched test/runner.rb to output the evironment variables before the tests run. Before these commits, ENV['GIT'] was showing the git command file correctly. After them, it's set to the string git.

Is there any way to work around this issue?

Ruby, Rails, etc Docs

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0