Issue #10643 has been updated by nagachika (Tomoyuki Chikanaga).


Hello, Grep
Thank you very much for your investigation!

I confirmed that the revision r59040 was depend on some other changesets, and it isn't clear that it can be backported without unexpected behavior change.

Anyway please show up the error message of test_command_line_progname_nonascii on ruby_2_4.
We don't know exactly what was happened there.

----------------------------------------
Bug #10643: 2.2: TestRubyOptions#test_command_line_progname_nonascii test failure (MinGW)
https://bugs.ruby-lang.org/issues/10643#change-69582

* Author: luislavena (Luis Lavena)
* Status: Closed
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version: 
* ruby -v: ruby 2.2.0dev (2014-12-24) [i386-mingw32]
* Backport: 2.4: REQUIRED, 2.5: DONTNEED
----------------------------------------
Hello,

Running tests against ruby_2_2 branch, the following failures were detected (mingw-w64 4.7.2 32bits, GCC 4.7.2, Windows 7 x64):

~~~
TestRubyOptions#test_command_line_progname_nonascii [C:/Users/Luis/Code/ruby/ruby/test/ruby/test_rubyoptions.rb:719]:
[ruby-dev:48752] [Bug #10555].
<["?.rb"]> expected but was
<[]>.
---
<[]> expected but was
<["C:\\Users\\Luis\\Code\\oneclick\\rubyinstaller\\sandbox\\ruby21_build\\ruby.exe: Invalid argument -- ?.rb (LoadError)"]>.
~~~




-- 
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>