Bug #10457
closedProc instead of String as error message still doesn't work (gem problem?)
Description
Proc instead of String as error message still doesn't work for me (see #10430).
The relevant gem has been updated (see https://bugs.ruby-lang.org/issues/10430#note-10), and the new gem is being downloaded and installed (see r48180), but it still doesn't work for me.
I suspect this is due to a problem when there are two or more versions of the same gem. If there's more than one gem, is there a rule for which version is selected? Is it possible to get rid of some of these gem versions? Can old gems be removed automatically?
How to reproduce:
Make a small change in lib/unicode_normalize/tables.rb. Any change should do; I changed "Q" to "QQ" in one instance. Run make install(-nodoc). Run ruby test/test_unicode_normalize.rb.
The result I get is as follows:
===============================================================================
Failure:
test_normalize_to_NFKD_from_source_with_nfkd(TestNormalize)
test/test_unicode_normalize.rb:38:in block (2 levels) in generate_test_normalize' test/test_unicode_normalize.rb:33:in
each'
test/test_unicode_normalize.rb:33:in `block in generate_test_normalize'
#Proc:0x000006033229f0@test/test_unicode_normalize.rb:32
<"Q"> expected but was
<"QQ">
===============================================================================
The failure is expected (artificially generated). The problem is the line
#Proc:0x000006033229f0@test/test_unicode_normalize.rb:32
The installation procedure ends with:
installing bundle gems: /usr/local/lib/ruby/gems/2.2.0 (build_info, cache, doc, extensions, gems, specifications)
DL is deprecated, please use Fiddle
minitest-5.4.1.gem
minitest-5.4.2.gem
power_assert-0.1.4.gem
test-unit-3.0.1.gem
test-unit-3.0.3.gem
Updated by duerst (Martin Dürst) about 10 years ago
- Related to Bug #10430: Proc instead of String as error message doesn't work. added
Updated by duerst (Martin Dürst) almost 9 years ago
- Status changed from Open to Closed