| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
test-unit depends on power_assert that the recent versions require
ruby 3.1 or later. While test-unit rescues syntax error at loading
power_assert for old ruby versions, warnings for experimental features
are not suppressed, and `assert_separately` fails because stderr is
not empty, by default. Since adding `required_ruby_version` to
power_assert causes the installation with old rubygems to fail, we
just ignore warnings for experimental features totally.
|
|
|
|
|
|
|
|
When a process with multiple threads is forked, LSAN outputs warning
messages to stderr like:
==276855==Running thread 276851 was not suspended. False leaks are possible.
We should ignore messages like this in tests.
|
|
|
|
|
|
-test-/asan should always be available.
|
|
|
|
For most tests (except two), we don't need to change Encoding.default_internal
in assert_raise_with_message. We're trying to run the test suite across
multiple Ractors and modifying Encoding.default_internal can cause other
concurrently running tests to fail.
|
|
|
|
|
|
It is checked against the given `list`, do not print the same output
twice.
Notes:
Merged: https://github.com/ruby/ruby/pull/13624
|
|
https://github.com/ruby/test-unit-ruby-core/pull/9
https://github.com/ruby/test-unit-ruby-core/pull/10
|
|
`Proc` does not have `encoding` method.
Also, make `assert_raise_with_message` accept a `Proc` as the expected
pattern, as well.
Notes:
Merged: https://github.com/ruby/ruby/pull/12923
|
|
Similar to `Test::Unit::assert_raise`, but allows sub classes too.
Notes:
Merged: https://github.com/ruby/ruby/pull/12625
|
|
Single `Integer` argument means an exact match to the major version.
Notes:
Merged: https://github.com/ruby/ruby/pull/11604
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11583
|
|
Remove `.ceil` from base time calculation that makes 10x gap.
This will make the assertion more strict and also less flaky.
Notes:
Merged-By: kou <kou@clear-code.com>
|
|
ASAN greatly increases the memory footprint of Ruby, so these static
thresholds are not appropriate. There's no real need to run these tests
under ASAN.
[Bug #20274]
|
|
strscan, ipaddr and some default gems still support Ruby 2.4.
After this, I extract this CoreAssertions to their repositories.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8419
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8313
|
|
Some symbol argument might not be accepted by Process.clock_gettime.
Notes:
Merged: https://github.com/ruby/ruby/pull/7773
|
|
To prevent influence from other processes.
Notes:
Merged: https://github.com/ruby/ruby/pull/7661
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7661
|
|
Increase the timeout limit when variance at rehearsal is small.
Notes:
Merged: https://github.com/ruby/ruby/pull/7661
|
|
|
|
So that `assert_raise` inside the block works.
|
|
|
|
`pattern_list` may contain string since d903e7672637.
|
|
* Calculate each timeout from the ratio of each factor to the first
factor.
|
|
* Use an `Enumerable` as factors, instead of three arguments.
* Include `assert_operator` time in rehearsal time.
* Round up max expected time.
Notes:
Merged: https://github.com/ruby/ruby/pull/7554
|
|
This reverts commit cae4342dd559e34c1ce6219593f77f0ad80286da.
This is failing a lot of CIs and nobody is actively looking into fixing
it. Let me revert this until we have a solution to it.
|
|
* Use an `Enumerable` as factors, instead of three arguments.
|
|
* Add `rehearsal` keyword argument
* Stop repeating with the same factor
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7506
|
|
This file is copied to default gems, which might support older
versions.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7462
|
|
|
|
https://github.com/ruby/openssl/commit/0d4cd8b9ca
|
|
Revert 806583c093ecc2d67830f0a8f0d94decf0ed71e5
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6252
|
|
|
|
https://github.com/ruby/date/commit/c55004715a
|
|
Issue only occurs in JRuby 9.3.0.0 and Windows and the full
console output is:
log rotation inter-process lock failed. D:\log.txt -> D:\log.txt.0: The process cannot access the file because it is being used by another process.
log writing failed. closed stream
log writing failed. closed stream
...
https://github.com/ruby/logger/commit/19fc734638
|
|
The gem doesn't even install on old rubies, but since the gemspec claims
it's supported, `gem install pathname` will try to install it and print
an error.
This commit doesn't fix the above issue. The only way to fix it would be
to restore support and release a new version that actually supports old
rubies. However, such a change has been proposed and ignored for a long
time.
So this issue proposes to leave that broken but at least bring the
gemspec manifest and the CI matrix in sync to hopefully avoid this issue
from happening again in the future.
https://github.com/ruby/pathname/commit/3ee010b538
|