summaryrefslogtreecommitdiff
path: root/test/.excludes-zjit
AgeCommit message (Collapse)Author
2026-04-02Revert "ZJIT: Skip TestOpenURI and TestOpenURISSL (#16603)"Alan Wu
This reverts commit 33b9d2ab9f45a0c66665fb8dc40ddebd07c7b7b7.
2026-04-02Revert "ZJIT: Skip TestOpenURIProxy on Linux (#16606)"Alan Wu
This reverts commit d368d42ec6b50cece947556a2185ce73fa493bfe.
2026-03-30ZJIT: Skip TestOpenURIProxy on Linux (#16606)Takashi Kokubun
Same random SystemStackError as TestOpenURI and TestOpenURISSL.
2026-03-30ZJIT: Skip TestOpenURI and TestOpenURISSL (#16603)Takashi Kokubun
2025-11-14ZJIT: Skip a flaky DNS test (#15192)Takashi Kokubun
2025-09-08ZJIT: Fix backtraces on opt_new (#14461)Takashi Kokubun
2025-09-05ZJIT: Fix tests for ZJIT (#14460)Takashi Kokubun
2025-09-05ZJIT: Invalidate local variables on EP escape (#14448)Takashi Kokubun
2025-09-05ZJIT: Remove unneeded tracing and thread test exclusions (#14453)Stan Lo
2025-09-02ZJIT: Remove unneeded test exclusions (#14430)Stan Lo
2025-08-26Remove `opt_aref_with` and `opt_aset_with`Aaron Patterson
When these instructions were introduced it was common to read from a hash with mutable string literals. However, these days, I think these instructions are fairly rare. I tested this with the lobsters benchmark, and saw no difference in speed. In order to be sure, I tracked down every use of this instruction in the lobsters benchmark, and there were only 4 places where it was used. Additionally, this patch fixes a case where "chilled strings" should emit a warning but they don't. ```ruby class Foo def self.[](x)= x.gsub!(/hello/, "hi") end Foo["hello world"] ``` Removing these instructions shows this warning: ``` > ./miniruby -vw test.rb ruby 3.5.0dev (2025-08-25T21:36:50Z rm-opt_aref_with dca08e286c) +PRISM [arm64-darwin24] test.rb:2: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information) ``` [Feature #21553]
2025-08-18ZJIT: Codegen for NewHash (#14059)Donghee Na
This is my first contribution to ZJIT. Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com> Co-authored-by: Max Bernstein <ruby@bernsteinbear.com>
2025-08-06ZJIT: Run TestFixnumAlan Wu
2025-08-04Resurrect another ZJIT skip on test_handle_interrupted?Takashi Kokubun
Failed at: https://github.com/ruby/ruby/actions/runs/16737407508/job/47378992863 Partially reverting https://github.com/ruby/ruby/pull/14097
2025-08-04Resurrect a ZJIT skip on test_switch_while_busy_loopTakashi Kokubun
This can still hang: https://github.com/ruby/ruby/actions/runs/16735509694/job/47373381258 partially reverting https://github.com/ruby/ruby/pull/14097
2025-08-04ZJIT: Remove passing tests from exclusions (#14097)Stan Lo
2025-08-01ZJIT: Fix side-exit panicking when there's too many localsAlan Wu
Previously, ARM64 panicked due to compiled_side_exits() when the memory displacement got large enough to exceed the 9 bits limit. Usually, we split these kind of memory operands, but compiled_side_exits() runs after split. Using scratch registers, implement `Insn::Store` on ARM such that it can handle large displacements without split(). Do this for x86 as well, and remove arch specific code from compiled_side_exits(). We can now run `TestKeywordArguments`. Since `Insn::Store` doesn't need splitting now, users enjoy lower register pressure. Downside is, using `Assembler::SCRATCH_REG` as a base register is now sometimes an error, depending on whether `Insn::Store` also needs to use the register. It seems a fair trade off since `SCRATCH_REG` is not often used, and we don't put it as a base register anywhere at the moment.
2025-07-24ZJIT: Remove redundant test exclusionsStan Lo
2025-07-23ZJIT: Add multiple exclude targetsStan Lo
2025-07-17ZJIT: Fix fixnum folding for negative values (#13942)Stan Lo
Use `fixnum_from_isize` instead of `fixnum_from_usize` in `fold_fixnum_bop` to properly handle negative values. Casting negative `i64` to `usize` produces large unsigned values that exceed `RUBY_FIXNUM_MAX`.
2025-07-16ZJIT: Remove unneeded test exclusionsStan Lo
After several ZJIT fix PRs, the number of failing/crashing tests for ZJIT has dropped significantly. This removes the unneeded test exclusions.
2025-07-15ZJIT: Start testing against `/test/ruby/` and update all ZJIT related ↵Stan Lo
testing targets/docs (#13791) * ZJIT: Add test exclusions for ZJIT * ZJIT: Update test targets and documentation - Rename `zjit-test-all` to `zjit-check` - Add `zjit-test-all` target to zjit.mk to run all Ruby tests with ZJIT enabled excluding known failing tests - Update documentation and CI workflow to reflect the new targets