| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
Upgrade IRB to https://github.com/ruby/irb/commit/41ea43a4a732e094acfa1b0fc1473fdcda9e6227
Mostly backport changes.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes [Bug #15720]
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This commit adds compaction support for:
* Fibers
* Continuations
* Autoload Constants
|
|
|
|
|
|
| |
* test/lib/test/unit/assertions.rb (assert_cpu_usage_low): apply
the timeout scale to measuring period. this assertion is very
runtime environment dependent.
|
|
|
|
|
|
| |
* test/lib/test/unit/assertions.rb (Test::Unit::Assertions):
promoted MIN_HZ and MIN_MEASURABLE as constants, which should be
constant through the process.
|
|
|
|
|
|
|
|
|
|
|
| |
* test/lib/test/unit.rb (Test::Unit::TimeoutOption): renamed
SubprocessOption.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#setup_options):
prefer `--timeout-scale` option.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#non_options):
prefer `ENV["RUBY_TEST_TIMEOUT_SCALE"]`.
|
| |
|
|
|
|
| |
https://hackerone.com/reports/605262
|
| |
|
| |
|
|
|
|
|
|
|
| |
CPU usage 1% causes occesional test failure. Try to use 5%.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/gentoo/ruby-master/log/20190604T153002Z.fail.html.gz
https://rubyci.org/logs/rubyci.s3.amazonaws.com/gentoo/ruby-master/log/20190610T153002Z.fail.html.gz
|
| |
|
|
|
|
|
|
|
| |
Sometimes ruby/spec fails when trying to specify local_host and
local_port for TCPSocket.open.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris11s-sunc/ruby-master/log/20190610T192504Z.fail.html.gz
|
|
|
|
| |
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190610T071910Z.log.html.gz
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
02155da7bad37bd1c8adadd486d2d16eac7af43b got a claim about sacrificing
ability to compare arbitrary `RUBY_DESCRIPTION`s without converting
timezones.
Because most of the people would be familiar with timezone conversion
with UTC but it'd be harder when it comes to JST, this commit just
changes the timezone in f42588f754d5885ec30631e5008c383f3ef905d8 to UTC.
Another bonus in using UTC is that we can use a shorter variant of
ISO 8601 format like "2019-06-10T14:26:24Z" (the last Z part).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using the same timezone for all commits is convenient when just looking
dates in RUBY_DESCRIPTION, but usually we also check `git log` when
we're interested in the order of commits.
`git log` shows times in committer's timezone and forcing RUBY_RELEASE_DATE
to JST makes it harder to find a corresponding commit from `git log`.
Because this label is only used in development, I believe there's no
strict requirement to use traditional timezone for release here.
Also when building Ruby after committing from a non-JST timezone, I'd be
surprised to see a strange time (in a different timezone) for my very new
commit in `ruby -v`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By the way, this is already improved by nobu:
```
$ benchmark-driver benchmark/irb_exec.yml --rbenv '2.6.3;2.7.0-preview1;before;after' -v
2.6.3: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]
2.7.0-preview1: ruby 2.7.0preview1 (2019-05-31 trunk c55db6aa271df4a689dc8eb0039c929bf6ed43ff) [x86_64-linux]
before: ruby 2.7.0dev (2019-06-10T21:13:14+09:00 master 973fd18f11) [x86_64-linux]
after: ruby 2.7.0dev (2019-06-10T21:18:56+09:00 master 976c689ad4) [x86_64-linux]
Calculating -------------------------------------
2.6.3 2.7.0-preview1 before after
irb_exec 11.868 5.872 6.297 10.278 i/s - 30.000 times in 2.527776s 5.108997s 4.764167s 2.918821s
Comparison:
irb_exec
2.6.3: 11.9 i/s
after: 10.3 i/s - 1.15x slower
before: 6.3 i/s - 1.88x slower
2.7.0-preview1: 5.9 i/s - 2.02x slower
```
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
```
$ benchmark-driver benchmark/irb_exec.yml --rbenv '2.6.3;2.7.0-preview1'
Calculating -------------------------------------
2.6.3 2.7.0-preview1
irb_exec 11.844 5.171 i/s - 30.000 times in 2.532887s 5.801960s
Comparison:
irb_exec
2.6.3: 11.8 i/s
2.7.0-preview1: 5.2 i/s - 2.29x slower
```
|
| |
|
| |
|
|
|
|
|
| |
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/archlinux/ruby-master/log/20190609T153804Z.fail.html.gz
* Thanks @naruse for the tip.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
|
|
|
|
|
|
|
|
|
| |
These arguments were previously documented as supported, but not
actually supported.
Patch from Toru Iwase
Fixes [Bug #15900]
|
| |
|
| |
|
| |
|
|
|
|
| |
I cannot tell the order just by commit hashes.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
With the SDK of Xcode 10.2.1, `API_AVAILABLE` and so on macros are
not defined in <os/availability.h> when using a compiler other
than clang (which has `__has_feature` and `__has_attribute`), but
`__API_AVAILABLE` macro and so on are defined, which are also
defined in <Availability.h>.
I suspect this is a bug of the SDK.
|
|
|
|
|
| |
* lib/rubygems/commands/unpack_command.rb: 'rubygems/package' is
required here, to fix broken `gem unpack` command.
|
| |
|
|
|
|
|
|
| |
This reverts commit b76630f73e8362d3072bfa7178471ddc5d21c235.
It fails with `make test-bundler BUNDLER_SPECS=runtime/setup_spec.rb:1204`
|
| |
|
| |
|
| |
|