From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2013-01-25T11:42:19+09:00
Subject: [ruby-core:51627] [ruby-trunk - Bug #7721] test_too_long_path2(TestProcess) fails on mingw32


Issue #7721 has been updated by nobu (Nobuyoshi Nakada).

File 0001-error.c-defer-error-message.patch added
ruby -v set to 38934

NoMemoryError could occur at many places, almostly everywhere creating
a new object, adding a new instance variable, growing up a container
object, etc.  It's just rare in normal cases.

r30682 reduced the sizes from 100MB to 10MB because NoMemoryError is
not intended, but test_too_long_path2 is still consuming double of
test_too_long_path.

I fix these tests instead for the time being.

Another strategy is, similar to NameError::message, keeping the given
parameters untouched and defer generating the message until to_s is
called.  But it's complex considering Marshal.

----------------------------------------
Bug #7721: test_too_long_path2(TestProcess) fails on mingw32
https://bugs.ruby-lang.org/issues/7721#change-35587

Author: phasis68 (Heesob Park)
Status: Closed
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: 
Target version: 
ruby -v: 38934


[ 6319/11317] TestProcess#test_too_long_path2Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\work\snapshot-mg32>exit
 = 8.03 s
 33) Failure:
test_too_long_path2(TestProcess) [C:/work/snapshot-mg32/test/ruby/test_process.rb:1393]:
[ruby-core:34833].
[Errno::ENOENT, Errno::E2BIG] expected but nothing was raised.

This failure is also mentioned at https://bugs.ruby-lang.org/issues/7710#note-3



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