[#80531] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...>

SASADA Koichi <ko1@ruby-lang.org> wrote:

24 messages 2017/04/02
[#80532] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/04/02

On 2017/04/02 11:35, Eric Wong wrote:

[#80540] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/04/03

SASADA Koichi <ko1@atdot.net> wrote:

[#81027] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

Eric Wong <normalperson@yhbt.net> wrote:

[#81028] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 9:33, Eric Wong wrote:

[#81029] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 10:53, SASADA Koichi wrote:

[#81031] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81033] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/08

On 2017/05/08 12:01, Eric Wong wrote:

[#81035] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/08

SASADA Koichi <ko1@atdot.net> wrote:

[#81042] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/08 15:36, Eric Wong wrote:

[#81044] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[#81045] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — SASADA Koichi <ko1@...> 2017/05/09

On 2017/05/09 12:38, Eric Wong wrote:

[#81047] Re: [ruby-cvs:65407] normal:r58236 (trunk): thread.c: comments on M:N threading [ci skip] — Eric Wong <normalperson@...> 2017/05/09

SASADA Koichi <ko1@atdot.net> wrote:

[ruby-core:80701] [Ruby trunk Bug#13441] building - GIT variable, ruby, rubygems tests

From: Greg.mpls@...
Date: 2017-04-15 17:40:22 UTC
List: ruby-core #80701
Issue #13441 has been updated by MSP-Greg (Greg L).


nobu (Nobuyoshi Nakada) wrote:
> Try `--with-git=git.exe` configuration option.

Thanks.  I'll try, just started a build testing the `io.c` patch.

Should that be `git.exe` or a full path to the file?

----------------------------------------
Bug #13441: building - GIT variable, ruby, rubygems tests
https://bugs.ruby-lang.org/issues/13441#change-64247

* Author: MSP-Greg (Greg L)
* Status: Feedback
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.0dev (2017-04-15 trunk 58363) [x64-mingw32]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
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](https://github.com/ruby/spec) repo.  These seem to conflict with the RubyGems tests use of the variable.

FYI, a while ago I patched [`test/runner.rb`](https://github.com/ruby/ruby/blob/trunk/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](https://msp-greg.github.io/)




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next