diff options
author | Alan Wu <XrXr@users.noreply.github.com> | 2021-11-30 18:11:42 -0500 |
---|---|---|
committer | Alan Wu <XrXr@users.noreply.github.com> | 2021-12-04 11:35:37 -0500 |
commit | 34b5e2566da88c392ada07437c3e8b44c295c9b2 (patch) | |
tree | d6d63592a65722cbcf6ac4e5fe3e4b524c1d1314 /bootstraptest | |
parent | 4a6ca12904c8160d68ac4b552636159926afff41 (diff) | |
download | ruby-34b5e2566da88c392ada07437c3e8b44c295c9b2.tar.gz |
YJIT: Enable out of memory tests
As of [1] and [2], YJIT has enough support for out of memory conditions
to pass these two basic tests.
OOM code paths are prone to bugs since they are rarely exercised in
common workloads. We might want to add CI runs that stress test these
code paths. Maybe outside of GitHub Actions for capacity reasons.
[1]: f41b4d44f95978dfa97af04af00055dc3fbf7978
[2]: b5b6ab4194f16e96ee5004288cc469ac1bca41a3
Diffstat (limited to 'bootstraptest')
-rw-r--r-- | bootstraptest/test_yjit.rb | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bootstraptest/test_yjit.rb b/bootstraptest/test_yjit.rb index f30c5ff900..18d1f85b93 100644 --- a/bootstraptest/test_yjit.rb +++ b/bootstraptest/test_yjit.rb @@ -2450,10 +2450,10 @@ assert_equal 'ok', %q{ RubyVM::YJIT.simulate_oom! if defined?(RubyVM::YJIT) nimai(false) -} if false # disabled for now since OOM crashes in the test harness +} -# block invalidation while out of memory assert_equal 'new', %q{ + # test block invalidation while out of memory def foo :old end @@ -2472,7 +2472,7 @@ assert_equal 'new', %q{ end test -} if false # disabled for now since OOM crashes in the test harness +} assert_equal 'ok', %q{ # Try to compile new method while OOM |