From: eregontp@... Date: 2019-03-29T18:13:50+00:00 Subject: [ruby-core:92051] [Ruby trunk Bug#15736] r67361 Update to ruby/spec@e81b3cd - spec failures on MinGW ? Issue #15736 has been updated by Eregon (Benoit Daloze). MSP-Greg (Greg L) wrote: > Sorry & fixed. My test code had some `disable=gems` in test-all, and I never cleared it for spec. The new tests aren't happy with that. Great. Now, it is weird that the command line doesn't override the environment variable (I assume you use RUBYOPT): ``` $ RUBYOPT=--disable-gems ruby --enable=gems -e 'p defined?(Gem)' nil ``` That seems a bug. ``` $ ruby --disable=gems --enable=gems -e 'p defined?(Gem)' "constant" $ ruby --enable=gems --disable=gems -e 'p defined?(Gem)' nil ``` works as expected. ---------------------------------------- Bug #15736: r67361 Update to ruby/spec@e81b3cd - spec failures on MinGW ? https://bugs.ruby-lang.org/issues/15736#change-77372 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.7.0dev (2019-03-29 trunk 67365) [x64-mingw32] * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- ruby-loco (MinGW trunk) had the following failures in spec tests as of r67365 (r67357 passed) ``` 1) The --enable and --disable flags can be used with gems FAILED Expected "nil" to equal "\"constant\"" /ruby/spec/ruby/command_line/feature_spec.rb:6:in `block (2 levels) in ' /ruby/spec/ruby/command_line/feature_spec.rb:3:in `' 2) The --enable and --disable flags can be used with gem FAILED Expected "nil" to equal "\"constant\"" /ruby/spec/ruby/command_line/feature_spec.rb:13:in `block (2 levels) in ' /ruby/spec/ruby/command_line/feature_spec.rb:3:in `' 3) The --enable and --disable flags can be used with did_you_mean FAILED Expected "nil" to equal "\"constant\"" /ruby/spec/ruby/command_line/feature_spec.rb:20:in `block (2 levels) in ' /ruby/spec/ruby/command_line/feature_spec.rb:3:in `' ``` -- https://bugs.ruby-lang.org/ Unsubscribe: