=begin
I observe following error on PPC64:
7) Failure:
test_spawn_too_long_path(TestProcess) [/builddir/build/BUILD/ruby-2.0.0-r39357/test/ruby/test_process.rb:1383]:
[Errno::ENOENT, Errno::E2BIG, nil] expected but nothing was raised.
8) Failure:
test_aspawn_too_long_path(TestProcess) [/builddir/build/BUILD/ruby-2.0.0-r39357/test/ruby/test_process.rb:1388]:
[Errno::ENOENT, Errno::E2BIG, nil] expected but nothing was raised.
I am quite sure, that there was no such test error testing with rev38848. Not sure if that might be related to 38934.
=end
Failure of the same two tests were observed also on Solaris10 before r39374.
After r39375, failure of test_spawn_too_long_path also vanished on Solaris10.
On Solaris10, with r39376,
TestProcess#test_aspawn_too_long_path = sh: a: not found
sh: a: not found
sh: a: not found
sh: a: not found
(snip many lines)
sh: a: not found
sh: a: not found
sh: a: not found
sh: fork failed - too many processes
536.65 s = F
and
Failure:
test_aspawn_too_long_path(TestProcess) [/XXXXXXX/test/ruby/test_process.rb:1388]: [ruby-core:34833].
[Errno::ENOENT, Errno::E2BIG] expected but nothing was raised.
This issue was solved with changeset r39417.
Vit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
test_process.rb: fix test
test/ruby/test_process.rb (assert_fail_too_long_path): get rid of
syntax error on sh, increase command line size until it exceeds the
limit. [Bug #7904]
This issue was solved with changeset r39665.
Vit, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.