From 5f376ce0a757496129fd3ec4ff282df8d02d7dfe Mon Sep 17 00:00:00 2001
From: k0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
Date: Tue, 13 Nov 2018 05:46:41 +0000
Subject: appveyor.yml: run memory-exchausting test separately

r65690 had no impact
https://ci.appveyor.com/project/ruby/ruby/builds/20253561/job/p5u235m8xx85t9o5.
Gave up to solve the issue inside the test.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65703 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
---
 test/ruby/test_array.rb | 1 -
 1 file changed, 1 deletion(-)

(limited to 'test/ruby/test_array.rb')

diff --git a/test/ruby/test_array.rb b/test/ruby/test_array.rb
index 6d77b1ebdd..1b102c4658 100644
--- a/test/ruby/test_array.rb
+++ b/test/ruby/test_array.rb
@@ -2943,7 +2943,6 @@ class TestArray < Test::Unit::TestCase
     Bug11235 = '[ruby-dev:49043] [Bug #11235]'
 
     def test_push_over_ary_max
-      GC.start # avoid NoMemoryError on the next line
       assert_separately(['-', ARY_MAX.to_s, Bug11235], "#{<<~"begin;"}\n#{<<~'end;'}", timeout: 30)
       begin;
         a = Array.new(ARGV[0].to_i)
-- 
cgit v1.2.3