| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://github.com/ruby/prime/commit/230a5af325
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, it would be an infinite loop if passed a non-prime
integer.
Also, Prime.include? should also provide similar results to
Module#include? if passed a Module, so handle that.
For consistency with Enumerable#include?, return false if passed
other object types.
Fixes Ruby Bug 10167.
https://github.com/ruby/prime/commit/55dda6aa7f
|
| |
|
| |
|
|
|
|
|
|
| |
openbsd current seems to behave the same as other OSs.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20200305T063005Z.fail.html.gz
|
| |
|
| |
|
|
|
|
|
|
| |
```
warning C4117: macro name '_INTEGRAL_MAX_BITS' is reserved, '#define' ignored
```
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 87f6154bb4c67ca77ee353bb1fe25a922036c0e5.
It turned out that the change fails to build on macOS
https://rubyci.org/logs/rubyci.s3.amazonaws.com/osx1014/ruby-master/log/20200304T074503Z.fail.html.gz
```
+ make 'TESTS=--hide-skip -v fiddle' RUBYOPT=-w test-all
dyld: lazy symbol binding failed: Symbol not found: _ffi_closure_alloc
Referenced from: /Users/hsbt/Documents/cb/tmp/build/20200304T074503Z/ruby/.ext/x86_64-darwin18/fiddle.bundle
Expected in: flat namespace
dyld: Symbol not found: _ffi_closure_alloc
Referenced from: /Users/hsbt/Documents/cb/tmp/build/20200304T074503Z/ruby/.ext/x86_64-darwin18/fiddle.bundle
Expected in: flat namespace
make: *** [yes-test-all] Abort trap: 6
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit efd641ffab34e433a8d8a7d78914576f2425aa90.
This changeset seems to be needed to suppress a warning on Ubuntu 20.04
https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20200304T033004Z.log.html.gz
```
closure.c:264:5: warning: 'ffi_prep_closure' is deprecated: use ffi_prep_closure_loc instead [-Wdeprecated-declarations]
264 | result = ffi_prep_closure(pcl, cif, callback, (void *)self);
| ^~~~~~
```
I guess there was a reason why the commit was reverted (maybe some CIs
failed?), so try it again.
|
| |
|
|
|
|
|
|
| |
Starting GCC 7, warnings about uninitialized variables are issued around
them. Such warnings could be false positives (all versions of clang do
not warn), but adding initializers there could never be bad things.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
See also
35eb12c06397e770392a41343cbffc4b204e15c9
6f5eb285077d9abf8f97056531996c58674b570c
687308cf0dab0af675e40da2b6ab8ccd5f77c072
b6a2d63eb3dbc31e110e8cb95e054dd71d49a611
|
|
|
|
|
| |
rb_transient_heap_managed_ptr_p is available only when USE_TRANSIENT_HEAP.
Need #if guards.
|
| |
|
| |
|
|
|
|
|
| |
GC.latest_gc_info[:major_by] can return `oldmalloc` because of
last GC status.
|
|
|
|
|
|
| |
`GC.start(full_mark: false)` can run full GC because of last
GC status. Just after major GC, the possibility to run major GC
next time is too small (not a zero, but too small possibility).
|
|
|
|
|
| |
Call GC.verify_internal_consistency only for Gem related test
on i386-solaris.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
As the headings become link anchors, remove less useful notes.
[ci skip]
|
| |
|
|
|
|
|
| |
Check heap consistency after each test to debug.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-master/log/20200303T012406Z.fail.html.gz
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
send() has special method launcher in VM and it has special
method_missing caller. This path doesn't set
ec->method_missing_reason which is used at exception creation,
so setup this information. Without this setting, NoMethodError
exception becomes NameError.
This patch will fix:
http://ci.rvm.jp/results/trunk-random1@phosphorus-docker/2761643
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Explicit `name:` entry was requested by @nobu.
|
|
|
|
|
| |
This target can be a build matrix. Also it does not make sense to test
it on mjit.
|
|
|
|
|
|
| |
One can specify working directory of a step, no by `cd foo` inside of
the run. See also
https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun
|
|
|
|
|
|
|
|
| |
The `branch:` specifier was necessary before, to prevent double-testing
master and trunk. Now that we no longer have trunk, we can slim the
expressions.
See also: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#on
|
|
|
|
| |
They were necessary when developing YAMLs, but not useful any longer.
|