Age | Commit message (Collapse) | Author |
|
|
|
It has been unstable for recent builds:
https://ci.appveyor.com/project/ruby/ruby/builds/26531442/job/0ycp7woekqqx97x9
https://ci.appveyor.com/project/ruby/ruby/builds/26531687/job/xui3rctcvi7r49iv
https://ci.appveyor.com/project/ruby/ruby/builds/26532019/job/1q0n46ci4g8dplwx
|
|
|
|
|
|
|
|
|
|
|
|
Closes: https://github.com/ruby/ruby/pull/2323
|
|
transient_heap.h is no longer needed.
|
|
as I already started to use --runner=block introduced in v0.14.20 like:
https://github.com/ruby/ruby/pull/2321#issuecomment-518638663
|
|
Not using official travis_retry.bash, because it's not supporting to
modify backoff seconds.
https://github.com/travis-ci/travis-build/blob/0ad8f1886b2c31994d847e126dc5842b7b3513e3/lib/travis/build/bash/travis_retry.bash
Not using official `travis_apt_get_update` function because it does not
propagate exit status to be used by retries.
https://github.com/travis-ci/travis-build/blob/0ad8f1886b2c31994d847e126dc5842b7b3513e3/lib/travis/build/bash/travis_apt_get_update.bash
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
|
|
The document states that "the limit should be a date object".
|
|
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
|
|
instead of <<. All the other callsites use `push`.
|
|
The target method name is a typo.
|
|
In 614c90fe21cf1d9cf6fb18684187d8c7e2f61de6, I assumed
apt-add-repository has been stable recently, but I saw PR randomly
failed for it today.
This commit only deals with "ubuntu-toolchain-r-test" and does NOT deal
with `llvm-toolchain-xenial-8` intentionally, because what it does
(mainly curl from build.travis-ci.org) seems to be more reliable than
"ubuntu-toolchain-r-test". Also `&clang-8` jobs are basically
allow_failures and it's less important to be stabilized.
|
|
|
|
[Bug #16044]
|
|
* time.c (time_to_r): get rid canonicalize and uncanonicalize
one-denominator rational, by rb_time_unmagnify_to_rational.
|
|
|
|
|
|
Inspired by 346aa557b31fe96760e505d30da26eb7a846bac9
Closes: https://github.com/ruby/ruby/pull/2321
|
|
This reverts commit 1ee88c51b3c319b74b69540e111e4a1c24833cad.
|
|
|
|
RUBY_PLATFORM on JRuby is always "java", so it will not reflect
the host operating system. This regex appears to be the consensus
way to detect Windows based on a search of Ruby code on Github:
https://github.com/search?q=%2Fmswin%7Cmsys%7Cmingw%7Ccygwin%7Cbccwin%7Cwince%7Cemc%2F&type=Code
|
|
|
|
|
|
|
|
|
|
Closes: https://github.com/ruby/ruby/pull/1790
|
|
Closes: https://github.com/ruby/ruby/pull/1425
|
|
version dependent
Fixes [Bug #6785]
|
|
Fixes [Bug #6726]
|
|
The last time we committed this, we were asking the VM to write to the
ep. But VM assertions check if the ENV data is the correct type, which
if it's a T_MOVED pointer it's not the correct type. So the vm
assertions would fail. This time we just directly write to it from the
GC and that bypasses the vm assertion checks.
|
|
|
|
|
|
as it failed https://travis-ci.org/ruby/ruby/jobs/567942969, unlike my
fork CI.
This just rollbacks a minor change in
798474deaf10dbea70c02724b5acf4487bbed660.
|
|
They have been too unstable.
Revert "Extend sleep before sending USR1 in TestProcess"
This reverts commit aaf69a8ba866193863a7eafe5c6044844bd71bc3.
Revert "Extend sleep before sending USR1 in TestProcess"
This reverts commit 076f3fcf11a061394d3d5f8c671512df1e983023.
|
|
|
|
because Travis team does not do it for us:
https://github.com/travis-ci/travis-build/pull/1712
The retried part has failed often even in one day:
https://travis-ci.org/ruby/ruby/jobs/567802384
https://travis-ci.org/ruby/ruby/jobs/567802388
https://travis-ci.org/ruby/ruby/jobs/567695879
https://travis-ci.org/ruby/ruby/jobs/567666931
For doing it easily, this also changes major aliases to
compiler-specific ones, because partially updating `before_install`
logic using `env` key was too hard and we needed to directly write
`before_install` for each package set. As a bonus of it, it may also
skip installing unnecessary packages when just `os: linux` is needed.
I'll revert this if this patch does not contribute to stabilize CI.
|
|
|
|
|
|
JRUBY_VERSION
* RUBY_ENGINE and RUBY_ENGINE_VERSION are defined on every modern Ruby.
* There is no such constant as TRUFFLERUBY_VERSION or RBX_VERSION.
https://github.com/rubygems/rubygems/commit/431d0aefdd
|
|
* If settings constants fail, show that exception instead of getting
another one due to variables being unset and hiding the real cause.
https://github.com/rubygems/rubygems/commit/f38cd67874
|
|
Sometimes it happens to me that my local tests start failing because I
pull some file removals or renames into my local copy, and those are
still present on my last copy of pkg/. In those cases, the test about
`rake package` will fail with something like the following:
````
Failure:
TestRakePackage#test_builds_ok [/home/deivid/Code/rubygems/test/rubygems/test_rake_package.rb:13]:
Expected `rake package` to work, but got errors:
```
cd pkg/rubygems-update-3.1.0.pre1
WARNING: See http://guides.rubygems.org/specification-reference/ for help
rake aborted!
Gem::InvalidSpecificationException: ["test/rubygems/test_rake_package.rb"] are not files
Tasks: TOP => package => gem => pkg/rubygems-update-3.1.0.pre1.gem
(See full trace by running task with --trace)
```
If you have added or removed files, make sure you run `rake update_manifest` to update the `Manifest.txt` accordingly.
Expected: true
Actual: false
````
So, make sure, package is always built from scratch.
https://github.com/rubygems/rubygems/commit/4e2cc9eb26
|
|
https://github.com/rubygems/rubygems/commit/83eced0b39
|
|
https://github.com/rubygems/rubygems/commit/5c3158d975
|
|
https://github.com/rubygems/rubygems/commit/b0588a87b1
|