| Age | Commit message (Collapse) | Author |
|
|
|
Check GC.enable'd status before and after test execution.
Write this checker in gc_checker.rb, it was renamed from
gc_compact_checker.rb.
Notes:
Merged: https://github.com/ruby/ruby/pull/4710
|
|
This file contains extended assertions for ruby core which do not
belong to test/unit.
|
|
|
|
|
|
There is no reason to care for minitest gem.
|
|
Some methods are separated into modules in test-unit now.
https://github.com/ruby/stringio/commit/d289848994
|
|
https://github.com/ruby/stringio/commit/74e39858eb
|
|
|
|
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]
|
|
|
|
https://github.com/ruby/date/commit/1ff7fa2d80
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3942
|
|
Also document that both :deprecated and :experimental are supported
:category option values.
The locations where warnings were marked as deprecation warnings
was previously reviewed by shyouhei.
Comment a couple locations where deprecation warnings should probably
be used but are not currently used because deprecation warning
enablement has not occurred at the time they are called
(RUBY_FREE_MIN, RUBY_HEAP_MIN_SLOTS, -K).
Add assert_deprecated_warn to test assertions. Use this to simplify
some tests, and fix failing tests after marking some warnings with
deprecated category.
Notes:
Merged: https://github.com/ruby/ruby/pull/3917
|
|
Instead of suppressing all warnings wholly in each test scripts by
setting `$VERBOSE` to `nil` in `setup` methods.
Notes:
Merged: https://github.com/ruby/ruby/pull/3925
Merged-By: nobu <nobu@ruby-lang.org>
|
|
It's not working
http://ci.rvm.jp/results/trunk-mjit@phosphorus-docker/3288206. I'm
debugging why.
|
|
Because Ruby often fails to dump a C backtrace.
|
|
for CIs like ci.rvm.jp.
|
|
I have no idea what I'm doing, but the previous commit caused lots of CI
failures like https://github.com/ruby/ruby/runs/1496949568 and this
place is the most suspicious.
|
|
CI failures like
http://ci.rvm.jp/results/trunk-mjit@phosphorus-docker/3280458 doesn't
provide any useful information, and it doesn't leave a core file in a CI
environment because a test like `Process.kill(:TRAP, $$)` overwrites in
a next run very quickly.
Thus I'd like to keep core files in /tmp.
|
|
This reverts commit 00f046ef57f9da7f5248f9ef9d55702ddc407bf1.
It was not helpful for an issue I was debugging.
|
|
This patch contains the fowllowing hacks:
(1) Add "--timetable-data=FILE" option for test-all
This option enables to dump timeline event
contains worker, suite, and start/end time.
(2) remove TestJIT in test_jit_debug.rb on parallel test.
it is duplicated test.
(3) move test_jit.rb and test_jit_debug.rb at first
because these two tests are bottleneck of parallel tests.
On my environment, `make test-all TESTS=-j12` reduced the total time
190 seconds -> 140 seconds.
Notes:
Merged: https://github.com/ruby/ruby/pull/3826
|
|
A worker crash happens very often, but we're not sure why.
I'd like to know a backtrace if it's available.
|
|
Regexp literals are frozen, and also dynamically comppiled Regexp
literals (/#{expr}/) are frozen.
Notes:
Merged: https://github.com/ruby/ruby/pull/3676
|
|
|
|
This is not "diff", but show expected and actual results both,
just to get rid of `NoMethodError` when an assertion failed.
|
|
|
|
Run tests in the order given in the command line.
|
|
As well as worker processes do in Test::Unit::Worker#run.
|
|
Instead of letting callers rescue the error always.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3039
|
|
There is a test directory named test/-ext-. Because this directry
starts with a hyphen, we have to cheat test/unit in order for it to
run the tests underneath. TESTS='-- -ext' worked for a long time.
Let's not break that maneuver.
|
|
assert_nothing_raised doesn't show the backtrace if an exception
is thrown in a block. This patch shows this backtrace.
|
|
Now --test-order=random is simply ignored. This patch respect
this option.
Notes:
Merged: https://github.com/ruby/ruby/pull/2932
|
|
`--seed N` option is just ignored so respect this option.
[Feature #16655]
Also making "Run options" display pretty.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2900
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2900
|
|
Auto runner should not run in forked processes in separated tests.
|
|
As SystemExit is ignored, it is just useless.
|
|
Redirect the output of separated child process to
`MiniTest::Unit.output`.
|
|
|
|
To output to the STDOUT of the parent process according to the
parallel test protocol, should send to the `MiniTest::Unit.output`
instead of each own STDOUT.
|
|
|
|
|
|
|
|
|
|
|
|
79eb5e1acac2339c6ec71db723298bdfcd92b233 implemented
RUBY_TEST_GC_COMPACT=1 so why not make it also possible via the command
line argument.
|