Disable RJIT_FORCE_ENABLE CI for now

Somehow btest-ruby is running miniruby. Not sure why. https://github.com/ruby/ruby/actions/runs/4412043427/jobs/7731124729#step:16:402 For RJIT's experimental purposes, having just one CI is enough. I'd like to focus on keeping .github/workflows/rjit.yml green.
ruby · Mar 14, 2023 · 278b639 · 278b639
1 parent 5868a78
commit 278b639
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/.github/workflows/compilers.yml b/.github/workflows/compilers.yml
@@ -200,7 +200,7 @@ jobs:
           - { name: enable-yjit,                    env: { append_configure: '--enable-yjit --disable-rjit' }, rust: true }
           - { name: enable-rjit,                    env: { append_configure: '--enable-rjit --disable-yjit' } }
           - { name: YJIT_FORCE_ENABLE,              env: { cppflags: '-DYJIT_FORCE_ENABLE' }, rust: true }
-          - { name: RJIT_FORCE_ENABLE,              env: { cppflags: '-DRJIT_FORCE_ENABLE' } }
+#         - { name: RJIT_FORCE_ENABLE,              env: { cppflags: '-DRJIT_FORCE_ENABLE' } }
 
     name: ${{ matrix.entry.name }}
     runs-on: ubuntu-latest