| Age | Commit message (Collapse) | Author |
|
|
|
|
|
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
|
|
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.
|
|
Call GC.verify_internal_consistency only for Gem related test
on i386-solaris.
|
|
|
|
Check heap consistency after each test to debug.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20200303T012406Z.fail.html.gz
|
|
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
|
|
MiniTest::Unit (superclass of Test::Unit::Runner) does not has
default seed parameter, but assigned after initializing.
However some tests use MiniTest::Unit without setup of seed option
and it cases unexpected test failures. To solve this issue, add
default seed parameter 42.
|
|
To avoid `srand(0)` effect in the other tests, call `srand($seed)`
at the beginning of each test (setup).
[Feature #16655]
|
|
This reverts commit 7c1553e91db07fed4fed3287b50304f1c69a685d.
It breaks some tests.
|
|
To avoid `srand(0)` effect in the other tests, call `srand($seed)`
at the beginning of each test (setup).
[Feature #16655]
|
|
`--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.
|
|
|
|
|
|
|
|
|
|
|
|
Separate each entries more obviously as `page-delimiter' works
fine.
|
|
|
|
This method returns loop counter for multi-run (0 start).
|
|
|
|
|
|
|
|
|
|
Fixed misspellings reported at [Bug #16437], only in ruby and rubyspec.
|
|
79eb5e1acac2339c6ec71db723298bdfcd92b233 implemented
RUBY_TEST_GC_COMPACT=1 so why not make it also possible via the command
line argument.
|
|
|
|
RUBY_TEST_GC_COMPACT=1 enables GC.compact checker which calls
GC.compact after each test.
|
|
`(ulimit -n 30; make test-tool)` fails with unexplicit message:
"undefined method `write' for nil:NilClass" due to lack of stdout.
This change makes it explicit. [Bug #5577]
|
|
`Exception#full_message` is only defined on ruby 2.5.0 and above.
https://github.com/ruby/fileutils/commit/a8968f41ed
|
|
`exception_details` is not defined anywhere.
This commit fixes the following test crash in ruby 2.4
```
Error: test_assert_output_lines(TestFileUtils): NoMethodError: undefined method `exception_details' for #<TestFileUtils:0x00005556ef699178>
```
And replaces it with an actual test failure:
```
[Test::Unit::CoreAssertions::MiniTest::Assertion] exception expected, not #<NoMethodError: undefined method `full_message' for #<RuntimeError: ok>
Did you mean? message>.
```
https://github.com/ruby/fileutils/commit/2f38ba6e82
|
|
This removes the security features added by $SAFE = 1, and warns for access
or modification of $SAFE from Ruby-level, as well as warning when calling
all public C functions related to $SAFE.
This modifies some internal functions that took a safe level argument
to no longer take the argument.
rb_require_safe now warns, rb_require_string has been added as a
version that takes a VALUE and does not warn.
One public C function that still takes a safe level argument and that
this doesn't warn for is rb_eval_cmd. We may want to consider
adding an alternative method that does not take a safe level argument,
and warn for rb_eval_cmd.
Notes:
Merged: https://github.com/ruby/ruby/pull/2476
|
|
by using ObjectSpace.trace_object_allocations.
`make test-all LEAK_CHECKER_TRACE_OBJECT_ALLOCATION=true` will print not
only leaked fds but also where it was created.
|
|
http://ci.rvm.jp/results/trunk-mjit@silicon-docker/2380788
```
test_all #<Thread:0x000055b6c8e9fca8@/tmp/ruby/v2/src/trunk-mjit/tool/lib/test/unit/parallel.rb:42 run> terminated with exception (report_on_exception is true):
<internal:pack>:134:in `pack': no implicit conversion of false into String (TypeError)
from /tmp/ruby/v2/src/trunk-mjit/tool/lib/test/unit/parallel.rb:160:in `_report'
from /tmp/ruby/v2/src/trunk-mjit/tool/lib/test/unit/parallel.rb:45:in `block in _run_suite'
```
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2635
|
|
According to rdoc, test-unit provides omit instead of skip.
This is a compatibility layer to make it work with both test-unit and
tool/lib/minitest.
|