Age | Commit message (Collapse) | Author |
|
Some of them were passing "by chance" because they used a `bundle
install` command that failed, but the assertion was using the result of
the previous. Others were skipped on bundler 3. Now they all pass in all
versions.
https://github.com/rubygems/rubygems/commit/cedf611e11
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
options
https://github.com/rubygems/rubygems/commit/4d39338670
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
By making them more explicit.
https://github.com/rubygems/rubygems/commit/9979c5a811
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/5e854722e2
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/365b46329b
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/744c03d144
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
Even if no explicit flags were passed to it.
https://github.com/rubygems/rubygems/commit/0598cbb68c
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/5e47879330
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/731b3783f1
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/6395392b83
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/3372b21553
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
This spec was originally written many years ago to verity gems were
properly "remembered" in the lock file. At this point, the test feels a
bit dummy since the first `bundle install` already runs on a "clean
machine".
https://github.com/rubygems/rubygems/commit/dbfefb3f5a
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
This reverts commit 20f06d9e178211a3016133852b72d21ac7bb93ad, reversing
changes made to f2b30cb70df8a518bef0e8a64bbceb86234d922d.
https://github.com/rubygems/rubygems/commit/40802bdb18
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
When bundler specs are run from a ruby tarball (ruby-core does this),
there's no git folder, so `git ls-files` fails.
Support this case by making specs rely on the list of files from the
bundler gemspec instead, and invert the spec that makes sure we ship the
right set of files.
As per the other quality specs, skip them in this case.
https://github.com/rubygems/rubygems/commit/b28d5ec931
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/1cc02930f3
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
This reverts commit 67d2a715ca35090fbb3ab13df5b7348b1807dd47.
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
with build metadata"
This reverts commit fcc8be0198a16cc5fa7d4827be0c781209b70f98.
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/9f15b595ab
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/08374d0e4a
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
And never recommend it inside CLI messages.
This flag represents the default behaviour of `bundle install`, and the
only reason it exists is to "override" previous `--deployment` flag
usages which were silently remembered. So it should be deprecated just
like all the other flags the rely on remembering their values across
invocations.
https://github.com/rubygems/rubygems/commit/40e50b7190
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/b368c7e0c4
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
This spec is run only in bundler 2 mode, and it's testing the
`--deployment` flag specifically.
https://github.com/rubygems/rubygems/commit/a5d91c68b6
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
They seem to be passing?
https://github.com/rubygems/rubygems/commit/a00d1e6896
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
https://github.com/rubygems/rubygems/commit/cea610e197
Notes:
Merged: https://github.com/ruby/ruby/pull/3184
|
|
Missed to commit a staged change.
|
|
As it is referenced only from compile.c, except for MJIT, simply
use the accessor function.
|
|
`RESERVED_HASH_VAL` and `RESERVED_HASH_SUBSTITUTION_VAL` have not
been used directly in hash.c since 72825c35b0d8.
|
|
* match uppercase types which would be global, other than [BDT]
* ignore `RUBY_` prefixed symbols
|
|
To honor the environment variable, keep GITPULLOPTIONS unset by
default, and appended the option to VCSUP.
|
|
Sorry!
|
|
MinGW seems to raise Errno::EACCES instead of EADDRINUSE when bind fails
due to in use.
https://github.com/ruby/ruby/runs/736825846
```
2) Error:
TestSocketAddrinfo#test_connect_from:
Errno::EACCES: Permission denied - bind(2) for 0.0.0.0:49721
D:/a/ruby/ruby/build/.ext/common/socket.rb:54:in `bind'
D:/a/ruby/ruby/build/.ext/common/socket.rb:54:in `connect_internal'
D:/a/ruby/ruby/build/.ext/common/socket.rb:114:in `connect_from'
D:/a/ruby/ruby/src/test/socket/test_addrinfo.rb:379:in `block in test_connect_from'
D:/a/ruby/ruby/src/test/socket/test_addrinfo.rb:374:in `open'
D:/a/ruby/ruby/src/test/socket/test_addrinfo.rb:374:in `test_connect_from'
```
|
|
|
|
Fetched tags by `make up` are not used, in CI environments.
|
|
Only the last commit is used, unless creating the ChangeLog file.
|
|
* Enhanced Rdoc for Hash
* Fix typo in Hash Rdoc
* Enhanced Rdoc for Hash
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3180
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3180
|
|
|
|
This fixes various issues when a module is included in or prepended
to a module or class, and then refined, or refined and then included
or prepended to a module or class.
Implement by renaming ensure_origin to rb_ensure_origin, making it
non-static, and calling it when refining a module.
Fix Module#initialize_copy to handle origins correctly. Previously,
Module#initialize_copy did not handle origins correctly. For example,
this code:
```ruby
module B; end
class A
def b; 2 end
prepend B
end
a = A.dup.new
class A
def b; 1 end
end
p a.b
```
Printed 1 instead of 2. This is because the super chain for
a.singleton_class was:
```
a.singleton_class
A.dup
B(iclass)
B(iclass origin)
A(origin) # not A.dup(origin)
```
The B iclasses would not be modified, so the includer entry would be
still be set to A and not A.dup.
This modifies things so that if the class/module has an origin,
all iclasses between the class/module and the origin are duplicated
and have the correct includer entry set, and the correct origin
is created.
This requires other changes to make sure all tests still pass:
* rb_undef_methods_from doesn't automatically handle classes with
origins, so pass it the origin for Comparable when undefing
methods in Complex. This fixed a failure in the Complex tests.
* When adding a method, the method cache was not cleared
correctly if klass has an origin. Clear the method cache for
the klass before switching to the origin of klass. This fixed
failures in the autoload tests related to overridding require,
without breaking the optimization tests. Also clear the method
cache for both the module and origin when removing a method.
* Module#include? is fixed to skip origin iclasses.
* Refinements are fixed to use the origin class of the module that
has an origin.
* RCLASS_REFINED_BY_ANY is removed as it was only used in a single
place and is no longer needed.
* Marshal#dump is fixed to skip iclass origins.
* rb_method_entry_make is fixed to handled overridden optimized
methods for modules that have origins.
Fixes [Bug #16852]
Notes:
Merged: https://github.com/ruby/ruby/pull/3140
|
|
|
|
|
|
Run lldb just before sending ABRT or KILL signal. Some tests
terminate child processes by TERM signal intentionally.
|
|
According to nobu recursion can be longer than my expectation. Limit
them here.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
VM stack could overflow here. The condition is when a symbol is passed
to a block-taking method via &variable, and that symbol has never been
used for actual method names (thus yielding that results in calling
method_missing), and the VM stack is full (no single word left). This
is a once-in-a-blue-moon event. Yet there is a very tiny room of stack
overflow. We need to check that.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
Was (harmless but) redundant.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
Just cosmetic change to improve readability.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
This commit changes the number of calls of MEMCPY from...
| send | &:sym
-------------------------|-------|-------
Symbol already interned | once | twice
Symbol not pinned yet | none | once
to:
| send | &:sym
-------------------------|-------|-------
Symbol already interned | once | none
Symbol not pinned yet | twice | once
So it sacrifices exceptional situation for normal path.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
Symbol#to_proc and Object#send are closely related each other. Why not
share their implementations. By doing so we can skip recursive call of
vm_exec(), which could benefit for speed.
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|
|
This changeset slightly speeds up on my machine.
Calculating -------------------------------------
before after
Optcarrot Lan_Master.nes 38.33488426546287 40.89825082589147 fps
40.91288557922081 41.48687465359386
40.96591995270991 41.98499064664184
41.20461943032173 43.67314690779162
42.38344888176518 44.02777536251875
43.43563728880915 44.88695892714136
43.88082889062643 45.11226186242523
Notes:
Merged: https://github.com/ruby/ruby/pull/3152
|