aboutsummaryrefslogtreecommitdiffstats
path: root/test/lib
Commit message (Collapse)AuthorAgeFilesLines
* Skip a test that is flaky with RJITTakashi Kokubun2023-11-031-0/+8
| | | | | | | | It's crashing inside the bug reporter after a crash, so not sure why it's crashing. It's not really useful for maintaining RJIT to flag this test failure, so let's just ignore it until we figure out why it fails. https://github.com/ruby/ruby/actions/runs/6752729246/job/18358439166
* Add description to the empty test file [ci skip]Nobuyoshi Nakada2023-08-151-0/+4
|
* * append newline at EOF. [ci skip]git2023-08-151-0/+1
|
* An empty test file for satisfy chkbuild [ci skip]Nobuyoshi Nakada2023-08-151-0/+0
|
* Revert "[ruby/rdoc] Update test libraries from ruby/ruby 2023-04-29"Hiroshi SHIBATA2023-04-294-1224/+0
| | | | This reverts commit 966f0d91e2a86fa1347cdafbe1af47e7350aa4ca.
* [ruby/rdoc] Update test libraries from ruby/ruby 2023-04-29Nobuyoshi Nakada2023-04-284-0/+1224
| | | | | | From https://github.com/ruby/ruby/commit/74028c210c23a13b3168886efcf837b4bf930468 https://github.com/ruby/rdoc/commit/badc518c57
* Revert an accidentally sync.Hiroshi SHIBATA2023-03-271-0/+25
| | | | | | Revert "[ruby/open3] Removed to load jit_support.rb" This reverts commit 67feb782f947046f65951303893713052a19a546.
* [ruby/open3] Removed to load jit_support.rbHiroshi SHIBATA2023-03-271-25/+0
| | | | | | It's removed at https://github.com/ruby/open3/commit/4445b9e2a2dd https://github.com/ruby/open3/commit/41b180deab
* Move yjit_force_enabled? to JITSupportTakashi Kokubun2023-03-111-6/+10
| | | | for consistency
* Remove unused methods from JITSupportTakashi Kokubun2023-03-111-78/+0
|
* RJIT: Break up and enable test_version (#7495)Takashi Kokubun2023-03-101-0/+6
|
* s/mjit/rjit/Takashi Kokubun2023-03-061-8/+8
|
* s/MJIT/RJIT/Takashi Kokubun2023-03-061-6/+6
|
* Stop building mjit_build_dir.soTakashi Kokubun2023-03-061-5/+0
|
* Removed accidentally commits with ruby/readline-extHiroshi SHIBATA2023-02-222-402/+0
| | | | Partly reverted 1ddda4c0d7d2b83658ab149e36e088961ca0b2dc
* [ruby/readline-ext] test_readline.rb only needs EnvUtilHiroshi SHIBATA2023-02-221-761/+0
| | | | https://github.com/ruby/readline-ext/commit/9245965ecd
* [ruby/readline-ext] Import EnvUtils and related test librariesHiroshi SHIBATA2023-02-223-0/+1163
| | | | https://github.com/ruby/readline-ext/commit/f034697a48
* MJIT: Compile methods in batches (#6900)Takashi Kokubun2022-12-101-1/+1
| | | | | | | * MJIT: Compile methods in batches * MJIT: make mjit-bindgen * MJIT: Fix RubyVM::MJIT tests
* YJIT: Run test-all tests without requiring RUN_OPTSAlan Wu2022-11-251-2/+3
| | | | | | | | Most tests in test_yjit.rb use a sub process, so we can run them even when the parent process is not running with YJIT. Run them so simply running `make check` tests YJIT a bit. [Misc #19149]
* Rename --mjit-min-calls to --mjit-call-threshold (#6731)Takashi Kokubun2022-11-141-2/+2
| | | for consistency with YJIT
* Stop testing MJIT on s390xTakashi Kokubun2022-09-051-15/+9
| | | | | It didn't work either. http://rubyci.s3.amazonaws.com/s390x/ruby-master/log/20220905T080003Z.fail.html.gz
* A64 Linux reports aarach64 in RUBY_PLATFORMAlan Wu2022-08-291-1/+1
| | | | This should fix a version string test
* Fix test_rubyoptions.rb for arm64 (https://github.com/Shopify/ruby/pull/396)Takashi Kokubun2022-08-291-1/+1
|
* Fix #5872 for MJIT GitHub ActionsTakashi Kokubun2022-07-101-0/+4
| | | | | If you run tests with RUN_OPTS=--mjit, the test fixes in https://github.com/ruby/ruby/pull/5872 don't work.
* Fix test_rubyoptions for MinGW (#5363)Takashi Kokubun2021-12-271-0/+5
| | | | | | | | | | | | | | | * Fix test_rubyoptions for MinGW follows up a74a2f456ad549025861be80f50cc3f0dd6646dd * Require jit_support * Fix MinGW platform * Handle MinGW UCRT and fix the prefix * Make it more robust
* Prepare for removing RubyVM::JIT (#5262)Takashi Kokubun2021-12-131-1/+1
|
* Rename --jit to --mjit (#5248)Takashi Kokubun2021-12-131-6/+6
| | | | | | | | | | | | | | | * Rename --jit to --mjit [Feature #18349] * Fix a few more --jit references * Fix MJIT Actions * More s/jit/mjit/ and re-introduce --disable-jit * Update NEWS.md * Fix test_bug_reporter_add
* Disable YJIT in MJIT testsAaron Patterson2021-10-201-0/+1
|
* Revert an accidentally commits at df86a13cc150f573b1078779667a1573747d3dbdHiroshi SHIBATA2021-05-174-1157/+0
|
* [ruby/psych] Removed needless platform detectionHiroshi SHIBATA2021-05-171-10/+0
| | | | https://github.com/ruby/psych/commit/57d704fd63
* [ruby/psych] Import test assertions from ruby/rubyHiroshi SHIBATA2021-05-174-0/+1167
| | | | https://github.com/ruby/psych/commit/01dda86681
* Rename RubyVM::MJIT to RubyVM::JITTakashi Kokubun2021-01-131-1/+1
| | | | | | | | because the name "MJIT" is an internal code name, it's inconsistent with --jit while they are related to each other, and I want to discourage future JIT implementation-specific (e.g. MJIT-specific) APIs by this rename. [Feature #17490]
* Guard all accesses to RubyVM::MJIT with defined?(RubyVM::MJIT) &&Benoit Daloze2020-12-041-1/+1
| | | | * Otherwise those tests, etc cannot run on alternative Ruby implementations.
* test/lib/jit_support.rb: Let JIT tests skip on centos8Yusuke Endoh2020-05-121-0/+2
| | | | It has the same issue as RHEL 8. k0kubun said he will fix later
* Split compile and link for MinGW supportTakashi Kokubun2020-05-031-1/+1
| | | | | | | | MinGW test_jit fails with no error message. Perhaps linker flags should not be passed when compilation is happening. Anyway splitting these stages doesn't matter for performance. So let me just split it to fix the issue. Probably this helps Solaris's issue too.
* Debug Solaris's MJIT failureTakashi Kokubun2020-05-031-1/+1
| | | | | | using -Winvalid-pch https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200501T170004Z.fail.html.gz
* Skip pdb corruption on Visual Studio 2015 as wellTakashi Kokubun2020-05-031-5/+5
| | | | | | It turned out that the pdb corruption happens on Visual Studio 2015 as well. https://ci.appveyor.com/project/ruby/ruby/builds/32602953/job/3gj43q18wqeiy729
* Skip Solaris RubyCI TestJIT for nowTakashi Kokubun2020-05-011-1/+1
| | | | | to be investigated later https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200501T160004Z.fail.html.gz
* Skip MinGW TestJIT* and macOS TestJITDebug failuresTakashi Kokubun2020-05-011-1/+1
| | | | | | caused by 818d6d33368a396d9cd3d1a34a84015a9e76c5c8, for now. I'll take a look at them tomorrow.
* Skip JIT tests on riscv64 due to SEGV of cc1Yusuke Endoh2020-04-201-0/+2
|
* The pdb header error is printed at stdoutTakashi Kokubun2020-04-181-2/+2
| | | | https://ci.appveyor.com/project/ruby/ruby/builds/32278754/job/90jmky2jq2k0wjv8
* Compilation error does not impact exit statusTakashi Kokubun2020-04-171-2/+2
| | | | | We failed to ignore https://ci.appveyor.com/project/ruby/ruby/builds/32245902/job/xcfxw67uexxysvni
* Fix logic to detect vs120Takashi Kokubun2020-04-131-2/+2
| | | | | MJIT_CC seems not defined https://ci.appveyor.com/project/ruby/ruby/builds/32161572/job/u5sw8yn4in87heki
* Add missing call in 70b7304f03Takashi Kokubun2020-04-131-1/+1
|
* Ignore AppVeyor vs120's pdb corruptionTakashi Kokubun2020-04-131-0/+12
| | | | | | | | We tried to fix this like https://github.com/ruby/ruby/pull/3029, but it didn't work. The failure has never been helpful for developing MJIT, and currently it's not prioritized to be fixed. Until we try to figure out the root cause on AppVeyor vs120, let's optionally disable testing when the random corruption happens.
* Optimize exivar access on JIT-ed getivarTakashi Kokubun2020-03-301-0/+1
| | | | | | | | | | | | | | | | | | JIT support of dd723771c11. $ benchmark-driver -v --rbenv 'before;before --jit;after --jit' benchmark/mjit_exivar.yml --repeat-count=4 before: ruby 2.8.0dev (2020-03-30T12:32:26Z master e5db3da9d3) [x86_64-linux] before --jit: ruby 2.8.0dev (2020-03-30T12:32:26Z master e5db3da9d3) +JIT [x86_64-linux] after --jit: ruby 2.8.0dev (2020-03-31T05:57:24Z mjit-exivar 128625baec) +JIT [x86_64-linux] Calculating ------------------------------------- before before --jit after --jit mjit_exivar 57.944M 53.579M 54.471M i/s - 200.000M times in 3.451588s 3.732772s 3.671687s Comparison: mjit_exivar before: 57944345.1 i/s after --jit: 54470876.7 i/s - 1.06x slower before --jit: 53579483.4 i/s - 1.08x slower
* Propagate JIT skip to all testsTakashi Kokubun2020-03-061-1/+7
|
* test/lib/jit_support.rb: The path to icc was changedYusuke Endoh2020-03-041-1/+1
|
* test/lib/jit_support.rb: Update the regexp for iccYusuke Endoh2019-12-051-1/+1
| | | | MJIT_CC is always an absolute path.
* Prefer using MJIT_CC for JIT support checkTakashi Kokubun2019-12-041-1/+1
| | | | | because Solaris might have CC=cc and we'd like to check full path MJIT_CC=/opt/developerstudio12.5/bin/cc instead.
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-13 00:25:50 +0000