From a9fd57056cdbf041f8f0ad1350846a175028542a Mon Sep 17 00:00:00 2001 From: Koichi Sasada Date: Fri, 9 Aug 2019 13:02:31 +0900 Subject: [PATCH] double memory limit on MJIT. On test with MJIT, sometimes it fails like: http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/2189967 --- test/ripper/test_parser_events.rb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/ripper/test_parser_events.rb b/test/ripper/test_parser_events.rb index 2c3b141904..59d4ad3987 100644 --- a/test/ripper/test_parser_events.rb +++ b/test/ripper/test_parser_events.rb @@ -1482,7 +1482,8 @@ class TestRipper::ParserEvents < Test::Unit::TestCase assert_equal("[fcall(proc,[],&block([],[void()]))]", parse("proc{|;y|}")) if defined?(Process::RLIMIT_AS) dir = File.dirname(__FILE__) - as = (RubyVM::MJIT.enabled? ? 150 : 100) * 1024 * 1024 + as = 100 * 1024 * 1024 # 100MB + as *= 2 if RubyVM::MJIT.enabled? # space for compiler assert_in_out_err(%W(-I#{dir} -rdummyparser), "Process.setrlimit(Process::RLIMIT_AS,#{as}); "\ "puts DummyParser.new('proc{|;y|!y}').parse",