| Age | Commit message (Collapse) | Author |
|---|
|
|
|
So that rubygems can find them as gems. However, the `--install-dir`
option of `gem install` seems to exclude prerelease gems, even already
installed in that directory, from the dependencies for some reasons;
use the `GEM_HOME` environment variable instead.
Now net-imap 0.5.0 depends on json gem.
Notes:
Merged: https://github.com/ruby/ruby/pull/11969
|
|
supported
Notes:
Merged: https://github.com/ruby/ruby/pull/11887
|
|
This caused an issue when `defined?` was in the `if` condition. Its
instructions weren't appended to the instruction sequence even though it was compiled
if a compile-time known logical short-circuit happened before the `defined?`. The catch table
entry (`defined?` compilation produces a catch table entry) was still on the iseq even though the
instructions weren't there. This caused faulty exception handling in the method.
The solution is to no add the catch table entry for `defined?` after a compile-time known logical
short circuit.
This shouldn't touch much code, it's only for cases like the following,
which can occur during debugging:
if false && defined?(Some::CONSTANT)
"more code..."
end
Fixes [Bug #20501]
Notes:
Merged: https://github.com/ruby/ruby/pull/11554
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11612
|
|
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
|
|
The instance variable @tmpfile was removed in ddcfc9f so check_tempfile_leak
did not work.
Notes:
Merged: https://github.com/ruby/ruby/pull/11498
|
|
Although `pend` in test-unit gem expects the block does not pass if it
is given, our `pend` should ignore the block silently as same as it
just skips the test with no message by default. Add an unused
parameter, to suppress the warning for the block to be ignored.
Notes:
Merged: https://github.com/ruby/ruby/pull/11538
|
|
Fix symlinks to executable as relative paths from `bin` directory.
Notes:
Merged: https://github.com/ruby/ruby/pull/11532
|
|
```
[ 14/191] TestParallel::TestParallel#test_hungup = 11.02 s
1) Failure:
TestParallel::TestParallel#test_hungup [C:/Users/hsbt/DevDrive/github.com/ruby/ruby/tool/test/testunit/test_parallel.rb:211]:
Expected /^Retrying hung up testcases\.+$/ to match "Run options: \n" +
" --seed=35582\n" +
" --ruby\n" +
" \".\\\\ruby.exe -I../../ruby/lib -I.ext/x64-mswin64_140 -I. ../../ruby/tool/runruby.rb --extout=.ext -- --disable-gems\"\n" +
" -j\n" +
" t1\n" +
" --worker-timeout=1\n" +
"\n" +
"# Running tests:\n" +
"\n" +
"[1/1] 50340=test4test_hungup.\n" +
"C:/Users/hsbt/DevDrive/github.com/ruby/ruby/tool/lib/test/unit.rb:418:in 'Process.kill': Invalid argument (Errno::EINVAL)\n" +
```
Notes:
Merged: https://github.com/ruby/ruby/pull/11430
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11315
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11315
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11311
|
|
We can handle uri, time and others without `make test-all` dependencies now.
|
|
|
|
|
|
RJIT doesn't spawn subprocesses so there should now be no need to
special case it.
|
|
|
|
This reverts commit 5a332940ed2f809cb17af7e4d068089b6e1fa6ca.
Something does not work well on Github Actions.
|
|
|
|
Not only defined in `Test::Unit` or `CoreAssertions`, also show the
caller location of assertion methods defined in the current class or
ancestors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We use the following site for that now:
* https://tools.ietf.org/ or http
* https://datatracker.ietf.org or http
Today, IETF said the official site of RFC is www.rfc-editor.org.
FYI: https://authors.ietf.org/en/references-in-rfcxml
I replaced them to www.rfc-editor.org.
|
|
|
|
|
|
|
|
Displays for each failure which test it actually occurred in. The
output destination follows the --{stdout,stderr}-on-failure option.
|
|
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]
|
