diff options
| author | Takashi Kokubun <takashikkbn@gmail.com> | 2022-12-24 01:13:40 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-12-24 01:13:40 -0800 |
| commit | b9332ac8e7126066ac4238443d63eaa4c06789f9 (patch) | |
| tree | 1d3d45ec28ddbcc7e124d026540be61cf4ef3840 /.github/workflows | |
| parent | d521c9e5a7ed603f8f1aaa9a9a66c3cc80599b0c (diff) | |
MJIT: Cancel all on disastrous situations (#7019)
I noticed this while running test_yjit with --mjit-call-threshold=1,
which redefines `Integer#<`. When Ruby is monkey-patched,
MJIT itself could be broken.
Similarly, Ruby scripts could break MJIT in many different ways. I
prepared the same set of hooks as YJIT so that we could possibly
override it and disable it on those moments. Every constant under
RubyVM::MJIT is private and thus it's an unsupported behavior though.
Notes
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
Diffstat (limited to '.github/workflows')
| -rw-r--r-- | .github/workflows/mjit.yml | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/.github/workflows/mjit.yml b/.github/workflows/mjit.yml index c1c6490203..34c971bdee 100644 --- a/.github/workflows/mjit.yml +++ b/.github/workflows/mjit.yml @@ -69,10 +69,9 @@ jobs: - run: make incs - run: make - run: sudo make -s install - - run: sudo apt-get install gdb # used by test / test-all failure - name: Run test run: | - ulimit -c unlimited + unset GNUMAKEFLAGS make -s test RUN_OPTS="$RUN_OPTS" timeout-minutes: 60 # - name: Run test-all @@ -82,7 +81,7 @@ jobs: # timeout-minutes: 60 - name: Run test-spec run: | - ulimit -c unlimited + unset GNUMAKEFLAGS make -s test-spec RUN_OPTS="$RUN_OPTS" timeout-minutes: 60 - uses: ruby/action-slack@b6882ea6ef8f556f9f9af9ec1220d3f1ced74acf # v3.0.0 |