Avoid failing test_enable on warnings

This fails on RubyCI due to RJIT warnings too often. It should be enough
to test RJIT feature in test_rjit_version. We only want warnings instead
of test failures when there are warnings, at least for this case.
This commit is contained in:
Takashi Kokubun 2023-04-03 08:52:46 -07:00
parent 3cb5e7558d
commit ba4ff2552e

View File

@ -172,10 +172,15 @@ class TestRubyOptions < Test::Unit::TestCase
end
def test_enable
if JITSupport.yjit_supported? || JITSupport.rjit_supported?
if JITSupport.yjit_supported?
assert_in_out_err(%w(--enable all -e) + [""], "", [], [])
assert_in_out_err(%w(--enable-all -e) + [""], "", [], [])
assert_in_out_err(%w(--enable=all -e) + [""], "", [], [])
elsif JITSupport.rjit_supported?
# Avoid failing tests by RJIT warnings
assert_in_out_err(%w(--enable all --disable rjit -e) + [""], "", [], [])
assert_in_out_err(%w(--enable-all --disable-rjit -e) + [""], "", [], [])
assert_in_out_err(%w(--enable=all --disable=rjit -e) + [""], "", [], [])
end
assert_in_out_err(%w(--enable foobarbazqux -e) + [""], "", [],
/unknown argument for --enable: `foobarbazqux'/)