| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
`generic_iv_tbl_compat` has not been utilized since 14d61a94ff01.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit a28c166f787710227c6aac54befd72778f041485.
This change didn't help.
According to odaira, the issue was fixed by increasing `ulimit -s`.
|
|
|
|
|
| |
As `command_rhs` is always a "value expression", `command_asgn`
does not need the same check.
|
| |
|
|
|
|
|
|
| |
This `str2` variable can be non-string (regexp etc.) but the previous
code passed it directly to rb_enc_str_asciionly_p(), which expects its
argument be a string. Let's enforce that constraint.
|
|
|
|
| |
[Feature #16505]
|
|
|
|
| |
[Feature #16505]
|
|
|
|
|
|
|
|
|
| |
We were inefficient in cases where there are a lot of duplicates due to
the use of linear search. Use a hash table instead.
These cases are not that rare in the wild.
[Feature #16505]
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On Arch, sending a signal in a loop seems hardly to yield the execution.
```
1) Error:
TestThreadQueue#test_queue_with_trap:
Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
```
https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-master/log/20200209T120002Z.fail.html.gz
This change allows the test to pass.
|
| |
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/b0b5f709bd
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/8c33abb13c
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/1df99d1481
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/106c31fc1b
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/c0a6303168
|
|
|
|
|
|
| |
individual gem
https://github.com/ruby/readline-ext/commit/efaca4a5f4
|
|
|
|
|
|
|
|
| |
assertions can be there"
This reverts commit 425b2064d394639101854c83a061a0918b33b857.
This cherry-pick was a mistake.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
```
% RBENV_VERSION=2.6.5 ruby -r matrix -e 'Vector[1]*Vector[2] rescue p($!)'
#<ExceptionForMatrix::ErrOperationNotDefined: Operation(*) can't be defined: Vector op Vector>
% RBENV_VERSION=2.7.0 ruby -r matrix -e 'Vector[1]*Vector[2] rescue p($!)'
#<ExceptionForMatrix::ErrOperationNotDefined: Operation(*) can\'t be defined: Vector op Vector>
% RBENV_VERSION=master ruby -r matrix -e 'Vector[1]*Vector[2] rescue p($!)'
#<ExceptionForMatrix::ErrOperationNotDefined: Operation(*) can't be defined: Vector op Vector>
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On s390x, TestFiber#test_stack_size fails with SEGV.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/rhel_zlinux/ruby-master/log/20200205T223421Z.fail.html.gz
```
TestFiber#test_stack_size [/home/chkbuild/build/20200205T223421Z/ruby/test/ruby/test_fiber.rb:356]:
pid 23844 killed by SIGABRT (signal 6) (core dumped)
| -e:1:in `times': stack level too deep (SystemStackError)
| from -e:1:in `rec'
| from -e:1:in `block (3 levels) in rec'
| from -e:1:in `times'
| from -e:1:in `block (2 levels) in rec'
| from -e:1:in `times'
| from -e:1:in `block in rec'
| from -e:1:in `times'
| from -e:1:in `rec'
| ... 172 levels...
| from -e:1:in `block in rec'
| from -e:1:in `times'
| from -e:1:in `rec'
| from -e:1:in `block in <main>'
| -e: [BUG] Segmentation fault at 0x0000000000000000
```
This change tries a similar fix with
ef64ab917eec02491f6bf7233a4031a8c35385e3 and
3ddbba84b5b1f001cd575a48cec56d7ce8e5fbb2.
|
|
|
|
| |
MSpec requires Ruby 2.4 or more recent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Under some Ext4 filesystem settings, a timestamp is limited up to
0x37fffffff (2446-05-10).
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Timestamps
> Therefore, timestamps should not overflow until May 2446.
Actually the spec fails under one of our CI environments, like:
```
1)
File.utime allows Time instances in the far future to set mtime and atime FAILED
Expected 2446 == 559444
to be truthy but was false
```
https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-master/log/20200208T180002Z.fail.html.gz
|
| |
|
|
|
|
| |
https://github.com/ruby/reline/commit/41deb1a3d9
|
| |
|
| |
|
|
|
|
|
|
|
| |
I struggled figuring out which of the pack/unpack functions goes into which direction and the two first sentences were of the documentation were:
* Import an integer into a buffer.
* Export an integer into a buffer.
It sounds like both of them go from a ruby integer to a buffer because both use "into". So I fixed it and went to "Import an integer from a buffer". I find this much more clear.
|
|
|
|
| |
test/did_you_mean/spell_checking/test_class_name_check.rb
|
| |
|
|
|
|
| |
test/psych/visitors/test_to_ruby.rb (#2881)
|
| |
|
|
|
|
|
|
| |
Function pointers are not void*. See also
ce4ea956d24eab5089a143bba38126f2b11b55b6
8427fca49bd85205f5a8766292dd893f003c0e48
|
|
|
|
| |
Against changes of the `assert_separately` prologue code.
|
| |
|
| |
|
|
|
|
| |
Auto runner should not run in forked processes in separated tests.
|
|
|
|
| |
As SystemExit is ignored, it is just useless.
|
|
|
|
|
|
| |
This reverts commit d767da428c28b7b9fec56b383bb32f6f76c6ad26.
It fails with spec/ruby/core/kernel/require_spec.rb:5
|