You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently do not run any of our JIT test runs with invokedynamic enabled. Had we been doing so, we probably would have caught #3950 and other recent issues with our indy logic.
This bug is a placeholder for getting indy enabled for our JIT runs, as additional runs.
I will start this by getting test:jruby:jit running with indy, since I added a test for #3950 within that suite.
This isn't a requirement for 9.1.3.0 but it would roust out some probably-easy-to-fix bugs.
The text was updated successfully, but these errors were encountered:
We currently do not run any of our JIT test runs with invokedynamic enabled. Had we been doing so, we probably would have caught #3950 and other recent issues with our indy logic.
This bug is a placeholder for getting indy enabled for our JIT runs, as additional runs.
I will start this by getting
test:jruby:jit
running with indy, since I added a test for #3950 within that suite.This isn't a requirement for 9.1.3.0 but it would roust out some probably-easy-to-fix bugs.
The text was updated successfully, but these errors were encountered: