[#17055] Set#map! vs. map — "David A. Black" <dblack@...>

Hi --

23 messages 2008/06/03

[#17084] Enumerable::Enumerator#with_memo — "Akinori MUSHA" <knu@...>

Hi,

36 messages 2008/06/03
[#17168] Re: Enumerable::Enumerator#with_memo — David Flanagan <david@...> 2008/06/09

Akinori MUSHA wrote:

[#17173] Re: Enumerable::Enumerator#with_memo — "Jeremy Kemper" <jeremy@...> 2008/06/10

On Mon, Jun 9, 2008 at 12:11 PM, David Flanagan <david@davidflanagan.com> wrote:

[#17192] Re: Enumerable::Enumerator#with_memo — "Martin DeMello" <martindemello@...> 2008/06/10

On Mon, Jun 9, 2008 at 10:57 PM, Jeremy Kemper <jeremy@bitsweat.net> wrote:

[#17162] Release Plan: Ruby 1.9.0-2 — SASADA Koichi <ko1@...>

Hi,

44 messages 2008/06/09
[#17254] Re: Release Plan: Ruby 1.9.0-2 — SASADA Koichi <ko1@...> 2008/06/15

Hi,

[#17273] Re: Release Plan: Ruby 1.9.0-2 — Ryan Davis <ryand-ruby@...> 2008/06/16

[#17276] Re: Release Plan: Ruby 1.9.0-2 — Kouhei Sutou <kou@...> 2008/06/16

Hi,

[#17312] Re: Release Plan: Ruby 1.9.0-2 — Ryan Davis <ryand-ruby@...> 2008/06/18

[#17346] Re: Release Plan: Ruby 1.9.0-2 — Kouhei Sutou <kou@...> 2008/06/19

Hi,

[#17167] Mail count in Subject — "Dirk Traulsen" <dirk.traulsen@...>

Hi!

20 messages 2008/06/09
[#17169] Re: Mail count in Subject — "Warren Brown" <warrenb@...> 2008/06/09

All,

[#17171] Re: Mail count in Subject — Urabe Shyouhei <shyouhei@...> 2008/06/10

Warren Brown wrote:

[#17327] A plea for a release process — Brian Ford <brixen@...>

Hi all,

15 messages 2008/06/18

[#17377] Re: Ruby 1.9.0/1.8.7/1.8.6/1.8.5 new releases (Security Fix) — "Bill Kelly" <billk@...>

Hi,

12 messages 2008/06/23

[#17393] URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — "Igal Koshevoy" <igal@...>

All currently available versions of MRI Ruby are either vulnerable to

104 messages 2008/06/24
[#17416] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Urabe Shyouhei <shyouhei@...> 2008/06/28

Sorry for a late reply but I think I've fixed this issue. Can someone

[#17417] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Igal Koshevoy <igal@...> 2008/06/28

Urabe Shyouhei wrote:

[#17419] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Urabe Shyouhei <shyouhei@...> 2008/06/28

Igal Koshevoy wrote:

[#17422] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Igal Koshevoy <igal@...> 2008/06/29

Urabe Shyouhei wrote:

[#17426] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Urabe Shyouhei <shyouhei@...> 2008/06/29

Igal Koshevoy wrote:

[#17438] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Igal Koshevoy <igal@...> 2008/06/29

Urabe Shyouhei wrote:

[#17499] We'll release 1.8.6/1.8.7 this Friday — Urabe Shyouhei <shyouhei@...> 2008/07/02

Hello, I think current 1.8.6/1.8.7 is stable than p230/p22, so I decided

[#17504] Re: We'll release 1.8.6/1.8.7 this Friday — "Vladimir Sizikov" <vsizikov@...> 2008/07/02

Hi Urabe,

[#17506] Re: We'll release 1.8.6/1.8.7 this Friday — Charles Oliver Nutter <charles.nutter@...> 2008/07/02

Vladimir Sizikov wrote:

[#17521] Re: We'll release 1.8.6/1.8.7 this Friday — Urabe Shyouhei <shyouhei@...> 2008/07/03

Charles Oliver Nutter wrote:

[#17544] Re: We'll release 1.8.6/1.8.7 this Friday — Igal Koshevoy <igal@...> 2008/07/03

Urabe Shyouhei wrote:

[#17545] Re: We'll release 1.8.6/1.8.7 this Friday — Charles Oliver Nutter <charles.nutter@...> 2008/07/03

Igal Koshevoy wrote:

[#17806] Re: We'll release 1.8.6/1.8.7 this Friday — "Michal Suchanek" <hramrach@...> 2008/07/16

On 02/07/2008, Charles Oliver Nutter <charles.nutter@sun.com> wrote:

[#17851] Re: We'll release 1.8.6/1.8.7 this Friday — Tanaka Akira <akr@...> 2008/07/19

In article <a5d587fb0807160533r4534fabdg257b4a9523b15f1e@mail.gmail.com>,

[#17852] Re: We'll release 1.8.6/1.8.7 this Friday — Federico Builes <federico.builes@...> 2008/07/19

[#17855] Re: We'll release 1.8.6/1.8.7 this Friday — Jeremy Henty <onepoint@...> 2008/07/19

On Sat, Jul 19, 2008 at 02:18:05PM +0900, Federico Builes wrote:

[#17857] Re: We'll release 1.8.6/1.8.7 this Friday — Federico Builes <federico.builes@...> 2008/07/19

[#17860] Re: We'll release 1.8.6/1.8.7 this Friday — Jeremy Henty <onepoint@...> 2008/07/19

On Sun, Jul 20, 2008 at 12:43:46AM +0900, Federico Builes wrote:

[#17939] Re: We'll release 1.8.6/1.8.7 this Friday — Kurt Stephens <ks@...> 2008/07/24

When will we see a new 1.8.6 release?

[#17940] Re: We'll release 1.8.6/1.8.7 this Friday — Nobuyoshi Nakada <nobu@...> 2008/07/24

Hi,

[#17941] Re: We'll release 1.8.6/1.8.7 this Friday — "Vladimir Sizikov" <vsizikov@...> 2008/07/24

Hi,

[#17945] Re: We'll release 1.8.6/1.8.7 this Friday — Jeremy Henty <onepoint@...> 2008/07/24

On Fri, Jul 25, 2008 at 02:04:15AM +0900, Vladimir Sizikov wrote:

[#17946] Re: We'll release 1.8.6/1.8.7 this Friday — Jeremy Henty <onepoint@...> 2008/07/24

On Fri, Jul 25, 2008 at 04:35:43AM +0900, Jeremy Henty wrote:

[#17947] Re: We'll release 1.8.6/1.8.7 this Friday — Federico Builes <federico.builes@...> 2008/07/24

Jeremy,

[#17948] Re: We'll release 1.8.6/1.8.7 this Friday — Nobuyoshi Nakada <nobu@...> 2008/07/25

Hi,

[#17953] Re: We'll release 1.8.6/1.8.7 this Friday — "Daniel Luz" <dev@...> 2008/07/25

On Thu, Jul 24, 2008 at 9:19 PM, Nobuyoshi Nakada <nobu@ruby-lang.org>

[#17423] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Tanaka Akira <akr@...> 2008/06/29

In article <48662E99.7030508@pragmaticraft.com>,

[#17424] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Federico Builes <federico.builes@...> 2008/06/29

[#17429] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — Igal Koshevoy <igal@...> 2008/06/29

Federico Builes wrote:

[#17431] Re: URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — "M. Edward (Ed) Borasky" <znmeb@...> 2008/06/29

Igal Koshevoy wrote:

[#17427] 1.8 release management — Yukihiro Matsumoto <matz@...>

Hi,

43 messages 2008/06/29
[#17455] Re: 1.8 release management — Stephen Bannasch <stephen.bannasch@...> 2008/06/30

Let me describe some simple questions about Ruby 1.8.6 that are not

[#17458] Re: 1.8 release management — Urabe Shyouhei <shyouhei@...> 2008/06/30

For what I know,

[#17547] Re: 1.8 release management — "Wilson Bilkovich" <wilsonb@...> 2008/07/03

On 6/30/08, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#17549] Re: 1.8 release management — Igal Koshevoy <igal@...> 2008/07/03

Wilson Bilkovich wrote:

[#17555] Re: 1.8 release management — "Luis Lavena" <luislavena@...> 2008/07/03

On Thu, Jul 3, 2008 at 4:41 PM, Igal Koshevoy <igal@pragmaticraft.com> wrote:

[#17585] Re: 1.8 release management — Urabe Shyouhei <shyouhei@...> 2008/07/04

Luis Lavena wrote:

[#17588] Re: 1.8 release management — Igal Koshevoy <igal@...> 2008/07/04

Urabe Shyouhei wrote:

[#17589] Re: 1.8 release management — Urabe Shyouhei <shyouhei@...> 2008/07/04

Igal Koshevoy wrote:

[#17591] Re: 1.8 release management — Igal Koshevoy <igal@...> 2008/07/04

Urabe Shyouhei wrote:

[#17593] Re: 1.8 release management — "Vladimir Sizikov" <vsizikov@...> 2008/07/04

Hi,

[ruby-core:17353] patches for tests of rubygems

From: "Yusuke ENDOH" <mame@...>
Date: 2008-06-20 13:22:50 UTC
List: ruby-core #17353
Hi,

Twelve test cases for rubygems fail in my environment.


| $ make test-all TESTS=rubygems
| ./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb
./runruby.rb --extout=.ext  -- "./test/runner.rb" --basedir="./test"
--runner=console rubygems
| Gem::Indexer tests are being skipped.  Install builder gem.
| Loaded suite rubygems
| Started
| ...............................FF...................................................................................................................................................................................................F......E........................................E...E..........................E...........................................................................................................................................................................................................................................................................................................EEEEE....................................................
| Finished in 21.170319349 seconds.
|
|   1) Failure:
| test_self_prefix_libdir(TestGem)
[/home/mame/work/ruby19/ruby/test/rubygems/test_gem.rb:343]:
| <nil> expected but was
| <"/home/mame/work/ruby19/ruby">.
|
|   2) Failure:
| test_self_prefix_sitelibdir(TestGem)
[/home/mame/work/ruby19/ruby/test/rubygems/test_gem.rb:356]:
| <nil> expected but was
| <"/home/mame/work/ruby19/ruby">.


I think the tests are wrong.  Here is patch.  I referred to
test_self_prefix.


Index: test/rubygems/test_gem.rb
===================================================================
--- test/rubygems/test_gem.rb	(revision 17489)
+++ test/rubygems/test_gem.rb	(working copy)
@@ -337,6 +337,7 @@

     file_name = File.expand_path __FILE__
     prefix = File.dirname File.dirname(file_name)
+    prefix = File.dirname prefix if File.basename(prefix) == 'test'

     Gem::ConfigMap[:libdir] = prefix

@@ -350,6 +351,7 @@

     file_name = File.expand_path __FILE__
     prefix = File.dirname File.dirname(file_name)
+    prefix = File.dirname prefix if File.basename(prefix) == 'test'

     Gem::ConfigMap[:sitelibdir] = prefix



|   3) Failure:
| test_self_build(TestGemExtConfigureBuilder)
[/home/mame/work/ruby19/ruby/test/rubygems/test_gem_ext_configure_builder.rb:37]:
| <["sh ./configure --prefix=/tmp/test_rubygems_12643/prefix",
|  "",
|  "make",
|  "ok\n",
|  "make install",
|  "ok\n"]> expected but was
| <["sh ./configure --prefix=/tmp/test_rubygems_12643/prefix",
|  "",
|  "make",
|  "make[1]: Entering directory
`/tmp/test_rubygems_12643/ext'\nok\nmake[1]: Leaving directory
`/tmp/test_rubygems_12643/ext'\n",
|  "make install",
|  "make[1]: Entering directory
`/tmp/test_rubygems_12643/ext'\nok\nmake[1]: Leaving directory
`/tmp/test_rubygems_12643/ext'\n"]>.


make prints Entering/Leaving directory in my environment.


Index: test/rubygems/test_gem_ext_configure_builder.rb
===================================================================
--- test/rubygems/test_gem_ext_configure_builder.rb	(revision 17489)
+++ test/rubygems/test_gem_ext_configure_builder.rb	(working copy)
@@ -29,12 +29,12 @@
       Gem::Ext::ConfigureBuilder.build nil, nil, @dest_path, output
     end

-    expected = [
-      "sh ./configure --prefix=#{@dest_path}",
-      "", "make", "ok\n", "make install", "ok\n"
-    ]
-
-    assert_equal expected, output
+    assert_equal "sh ./configure --prefix=#{@dest_path}", output.shift
+    assert_equal "", output.shift
+    assert_equal "make", output.shift
+    assert_match /^ok$/m, output.shift
+    assert_equal "make install", output.shift
+    assert_match /^ok$/m, output.shift
   end

   def test_self_build_fail


|   4) Error:
| test_class_build(TestGemExtRakeBuilder):
| Gem::InstallError: rake failed:
|
| /home/mame/work/ruby19/local/bin/ruby mkrf_conf.rb
|
| rake RUBYARCHDIR=/tmp/test_rubygems_12643/prefix
RUBYLIBDIR=/tmp/test_rubygems_12643/prefix
| sh: rake: command not found
|
|     /home/mame/work/ruby19/ruby/lib/rubygems/ext/builder.rb:51:in `run'
|     /home/mame/work/ruby19/ruby/lib/rubygems/ext/rake_builder.rb:21:in `build'
|     /home/mame/work/ruby19/ruby/test/rubygems/test_gem_ext_rake_builder.rb:31:in
`block in test_class_build'
|     /home/mame/work/ruby19/ruby/test/rubygems/test_gem_ext_rake_builder.rb:29:in
`chdir'
|     /home/mame/work/ruby19/ruby/test/rubygems/test_gem_ext_rake_builder.rb:29:in
`test_class_build'


The test failed to execute rake, because I installed ruby and rake
to /home/mame/work/ruby19/local that is not included in the
environment variable PATH.
I guess this test should specify an absolute path to rake.


In addition, lib/rubygems/ext/rake_builder.rb tried to rewrite a
frozen string (which was returned from ENV object) destructively.
I think it's a bug.


Index: runruby.rb
===================================================================
--- runruby.rb	(revision 17489)
+++ runruby.rb	(working copy)
@@ -46,6 +46,7 @@
 config["bindir"] = abs_archdir
 ENV["RUBY"] = File.expand_path(ruby)
 ENV["PATH"] = [abs_archdir, ENV["PATH"]].compact.join(File::PATH_SEPARATOR)
+ENV["rake"] = ENV["RUBY"] + " " + File.join(abs_archdir, "bin", "rake")

 if pure
   libs << File.expand_path("ext", srcdir) << "-"
Index: test/rubygems/test_gem_ext_rake_builder.rb
===================================================================
--- test/rubygems/test_gem_ext_rake_builder.rb	(revision 17489)
+++ test/rubygems/test_gem_ext_rake_builder.rb	(working copy)
@@ -34,7 +34,7 @@
     expected = [
       "#{Gem.ruby} mkrf_conf.rb",
       "",
-      "rake RUBYARCHDIR=#{@dest_path} RUBYLIBDIR=#{@dest_path}",
+      "#{ENV["rake"] || "rake"} RUBYARCHDIR=#{@dest_path}
RUBYLIBDIR=#{@dest_path}",
       "(in #{realdir})\n"
     ]

@@ -63,7 +63,7 @@

 #{Gem.ruby} mkrf_conf.rb

-rake RUBYARCHDIR=#{@dest_path} RUBYLIBDIR=#{@dest_path}
+#{ENV["rake"] || "rake"} RUBYARCHDIR=#{@dest_path} RUBYLIBDIR=#{@dest_path}
     EOF

     assert_equal expected, error.message.split("\n")[0..4].join("\n")
Index: lib/rubygems/ext/rake_builder.rb
===================================================================
--- lib/rubygems/ext/rake_builder.rb	(revision 17489)
+++ lib/rubygems/ext/rake_builder.rb	(working copy)
@@ -16,7 +16,7 @@
     end

     cmd = ENV['rake'] || 'rake'
-    cmd << " RUBYARCHDIR=#{dest_path} RUBYLIBDIR=#{dest_path}"
+    cmd += " RUBYARCHDIR=#{dest_path} RUBYLIBDIR=#{dest_path}"

     run cmd, results



|   7) Error:
| test_execute(TestGemOutdatedCommand):
| Gem::RemoteFetcher::FetchError: getaddrinfo: Name or service not
known (SocketError)
|         fetching size (http://gems.example.com/yaml)
|     /home/mame/work/ruby19/ruby/lib/rubygems/remote_fetcher.rb:173:in
`rescue in fetch_size'
|     /home/mame/work/ruby19/ruby/lib/rubygems/remote_fetcher.rb:153:in
`fetch_size'
|     /home/mame/work/ruby19/ruby/lib/rubygems/spec_fetcher.rb:146:in
`rescue in block in legacy_repos'
|     /home/mame/work/ruby19/ruby/lib/rubygems/spec_fetcher.rb:142:in
`block in legacy_repos'
|     /home/mame/work/ruby19/ruby/lib/rubygems/spec_fetcher.rb:138:in `reject'
|     /home/mame/work/ruby19/ruby/lib/rubygems/spec_fetcher.rb:138:in
`legacy_repos'
|     /home/mame/work/ruby19/ruby/lib/rubygems/spec_fetcher.rb:237:in
`warn_legacy'
|     /home/mame/work/ruby19/ruby/lib/rubygems/source_index.rb:310:in
`rescue in block in outdated'
|     /home/mame/work/ruby19/ruby/lib/rubygems/source_index.rb:305:in
`block in outdated'
|     /home/mame/work/ruby19/ruby/lib/rubygems/source_index.rb:302:in `each'
|     /home/mame/work/ruby19/ruby/lib/rubygems/source_index.rb:302:in `outdated'
|     /home/mame/work/ruby19/ruby/lib/rubygems/commands/outdated_command.rb:21:in
`execute'
|     /home/mame/work/ruby19/ruby/test/rubygems/test_gem_outdated_command.rb:33:in
`block in test_execute'
|     /home/mame/work/ruby19/ruby/lib/rubygems/user_interaction.rb:42:in
`use_ui'
|     /home/mame/work/ruby19/ruby/lib/rubygems/user_interaction.rb:65:in
`use_ui'
|     /home/mame/work/ruby19/ruby/test/rubygems/test_gem_outdated_command.rb:33:in
`test_execute'


The test tried to resolve gems.example.com, and of course failed.
I have no idea to remove this error.


| 664 tests, 1917 assertions, 3 failures, 9 errors
| make: *** [test-all] Error 1


Other failures and errors are removed by above patches.

What do you think?

-- 
Yusuke ENDOH <mame@tsg.ne.jp>

In This Thread

Prev Next