aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Replaced accessors of `Struct` with `invokebuiltin`Nobuyoshi Nakada2020-06-164-30/+45
|
* Add static modifier for rb_int_ceil & rb_int_floor (#3217)S.H2020-06-161-4/+4
|
* Update without touch-unicode-filesNobuyoshi Nakada2020-06-165-17/+4
|
* Just update sources in CI without fetchingNobuyoshi Nakada2020-06-168-10/+32
| | | | | Also install external libraries only, extract-gems does not work unless base ruby is available.
* * 2020-06-16 [ci skip]git2020-06-161-1/+1
|
* Updated builtin type namesNobuyoshi Nakada2020-06-161-2/+2
| | | | Fixnum and Bignum have been unified to Integer already.
* Exit with non-zero status on disabled gem system update.Josef Šimánek2020-06-152-3/+5
|
* Add Gem.disable_system_update_message to disable gem update --system if needed.Josef Šimánek2020-06-153-0/+28
|
* Remove encoding magic commentsDavid Rodríguez2020-06-1511-13/+0
| | | | They are no longer needed since ruby 2.0.
* Deprecate `Gem::Util.silent_system`David Rodríguez2020-06-152-2/+15
| | | | There's better tools for this job.
* Replace `Gem::Util.silent_system` with better toolsDavid Rodríguez2020-06-152-5/+8
|
* Remove modelines for consistencyDavid Rodríguez2020-06-151-1/+0
| | | | No other files in the repo include this.
* Remove random codeDavid Rodríguez2020-06-151-3/+0
|
* Use space inside block braces everywhereDavid Rodríguez2020-06-1599-469/+469
| | | | To make rubygems code style consistent with bundler.
* Fix ruby-head failing testsDavid Rodríguez2020-06-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In `ruby-head` (where system rubygems already has the `XDG` standard implementation), some tests currently depend on the presence of a `~/.gem` folder in the home of the user that runs the tests. If that file is present, tests pass, otherwise they don't. For example, the following passes if you have a `~/.gem` folder but fails otherwise with: ``` $ rake TESTOPTS="--name=/TestGemCommandsGenerateIndexCommand#test_execute$\|TestGemCommandsUpdateCommand#test_execute_user_install/ -v" Run options: "--name=/TestGemCommandsGenerateIndexCommand#test_execute$|TestGemCommandsUpdateCommand#test_execute_user_install/" -v --seed 17318 # Running: TestGemCommandsGenerateIndexCommand#test_execute = 0.02 s = . TestGemCommandsUpdateCommand#test_execute_user_install = /rubygems/test/rubygems/test_gem_commands_update_command.rb:412: warning: instance variable @user_install not initialized 0.04 s = F Finished in 0.095337s, 20.9783 runs/s, 20.9783 assertions/s. 1) Failure: TestGemCommandsUpdateCommand#test_execute_user_install [/rubygems/test/rubygems/test_gem_commands_update_command.rb:414]: user_install must be set on the installer 2 runs, 2 assertions, 1 failures, 0 errors, 0 skips rake aborted! Command failed with status (1) Tasks: TOP => default => test (See full trace by running task with --trace) ``` This is because the very initial `require` of the default `did_you_mean` gem that ruby does on startup runs _before_ the global `setup` hook of our tests run. During this require `Gem.data_home` and its value is memoized to a path in the real users home (not the fake user's home that our tests setup, since that code hasn't run yet). Then that memoized value is used when looking for the default folders to look for gems, and since there's no `~/.gem` folder, its value is actually used as part of the `Gem.user_dir` folder in `Gem::Specification.dirs` (this is how we've approached backwards compatibility for the `XDG` feature). That means dummy test gems with the `--user-install` flag are installed to global, real locations and everything is messed up. This commit fixes the issue by resetting the `Gem.data_home` value in case it has already been memoized.
* Revert "Revert "[rubygems/rubygems] Remove unneeded global teardown""David Rodríguez2020-06-1511-9/+32
| | | | This reverts commit ac2c07e98373bb62be618001c897fa9d5809d8a4.
* Revert "Revert "[rubygems/rubygems] Remove unneeded teardown""David Rodríguez2020-06-151-6/+0
| | | | This reverts commit ceacb06311cf150cd3682b277bbe6cf7e7bbbc30.
* Prefer String#each_byte when using a blockNobuyoshi Nakada2020-06-151-1/+1
|
* tool/lib/minitest/unit.rb: Reproducible shuffle of test suitesYusuke Endoh2020-06-151-1/+12
| | | | | | | | | | | ... based on CRC32 of names of the test suites. Formerly, `make test-all` randomized the order of the test suites by using `Array#shuffle`. It also shows `--seed N` to reproduce the order, but it was not reproducible when a suite set is different. This change sorts the suites by CRC32 hash of the suite names with a salt generated by the seed.
* Accommodate process title spec to ruby-core setupDavid Rodríguez2020-06-151-3/+3
| | | | | | I'm guessing the commands under ruby-core setup are very long, so the title gets truncated. Use a shorter title, since the test doesn't really care.
* Fix most exec specsDavid Rodríguez2020-06-154-15/+18
| | | | | | | | | The `gem_command` helper was failing to require `support/hax.rb`, which takes care of making sure rubygems actually picks up the right `ruby` executable under ruby-core setup (`ENV["RUBY"]`). This caused binstubs to be generated with a wrong shebang, and that caused `bundle exec` to not work. The error message was pretty confusing though due to https://bugs.ruby-lang.org/issues/16952.
* A help message to `tool/sync_default_gems.rb`David Rodríguez2020-06-151-8/+15
|
* Use filesystem encoding in do_GET of filehandlerKazuhiro NISHIYAMA2020-06-151-0/+5
| | | | | | | | | | | | | | | | | | | | Try to fix 404 error on mswinci. https://rubyci.org/logs/mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-master/log/20200614T225859Z.fail.html.gz ``` 1) Failure: WEBrick::TestFileHandler#test_cjk_in_path [D:/tmp/mswin-build20200615-24932-11ykstf/ruby/test/webrick/utils.rb:72]: exceptions on 2 threads: webrick log start: [2020-06-15 09:48:29] ERROR `/あ.txt' not found. webrick log end. <"200"> expected but was <"404">. --- <[]> expected but was <["[2020-06-15 09:48:29] ERROR `/\xE3\x81\x82.txt' not found.\n"]>. ```
* Try using longer read_timeout for --jit-waitTakashi Kokubun2020-06-141-7/+4
| | | | | | | | failure on TestFTP. When we skip a test, the place to hang (long wait for compilation) just moves to another test and it doesn't seem to finish. http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/3003055
* * 2020-06-15 [ci skip]git2020-06-151-1/+1
|
* Remove non-US-ASCII characters [ci skip]Nobuyoshi Nakada2020-06-141-2/+2
|
* Support arguments of singleton methodNobuyoshi Nakada2020-06-141-0/+1
|
* Fixed up rest, keywords, keyword rest and block argumentsNobuyoshi Nakada2020-06-141-2/+9
|
* Make __builtin_cexpr! and __builtin_cstmt! work againTakashi Kokubun2020-06-131-2/+17
| | | | | | | | | | | with Ripper. a3e6f52c17061f012c4e638b3343b57752ed7603 introduced __builtin_cexpr! and __builtin_cstmt!, but nobody has used them and then they broke on 79292b30884ebcd8be028a7f3c9ccafd7759f2ae by undefined `params`. This patch fixes the undefined `params`, but still we're not using them yet.
* Add ubuntu-20.04 and rename to ubuntu-18.04 from ubuntu-latestKazuhiro NISHIYAMA2020-06-141-1/+1
|
* apinfo/fpinfo should always be non-NULLKazuki Tsujimoto2020-06-141-12/+8
|
* Introduce find pattern [Feature #16828]Kazuki Tsujimoto2020-06-1410-10/+449
|
* push_pktbl is needed for hash pattern, not for array patternKazuki Tsujimoto2020-06-141-3/+2
|
* * 2020-06-14 [ci skip]git2020-06-141-1/+1
|
* Skip test_getbinaryfile_command_injection on --jit-waitTakashi Kokubun2020-06-131-0/+2
| | | | | | | | | | Timeout-based test often fails with --jit-wait as a false positive. Like other tests in the TestFTP, let me skip this as well. http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/3001181 http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/3000134 http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/2999923 http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/2998857
* Extracted argument forwarding staffsNobuyoshi Nakada2020-06-131-47/+58
|
* [ripper] use Ripper DSLNobuyoshi Nakada2020-06-131-3/+3
|
* [ci skip] Enhanced RDoc for Array (#3219)Burdette Lamar2020-06-131-19/+59
| | | | | | | | Methods: #join #inspect/#to_s #to_a
* Suppress warnings [Feature #15973]Nobuyoshi Nakada2020-06-134-6/+6
|
* Added install-dbgNobuyoshi Nakada2020-06-134-3/+43
| | | | Scripts to run the interpreter via debugger.
* [ci skip] Enhanced Rdoc for Array (#3216)Burdette Lamar2020-06-121-46/+160
| | | | | | | | | | | Methods: #insert #each #each_index #reverse_each #length #empty?
* * 2020-06-13 [ci skip]git2020-06-131-1/+1
|
* Update example code in Enumerator#chunk documentation [ci skip]Jeremy Evans2020-06-121-1/+1
| | | | | | | | | The code assumed that /usr/share/dict/words did not use mixed case, and it does at least on a few operating systems. From CryptoRAT (Luke Elliot) Fixes [Bug #16957]
* Revert "[ruby/fileutils] Make verbose output go to stdout instead of stderr"Nobuyoshi Nakada2020-06-122-6/+6
| | | | | | This reverts commit 7cddb844e6d51f954c6669341b9cc656bd7d3492, because the test of rake 13.0.1 is depending on the previous behavior.
* [ruby/fileutils] Fix #install with "X" mode optionNobuyoshi Nakada2020-06-122-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `FileUtils#install` methed raises an unexpected `TypeError`, when called with `mode:` option which has `"X"`. ``` $ ruby -rfileutils -e 'FileUtils.install("tmp/a", "tmp/b", mode: "o+X")' /opt/local/lib/ruby/2.7.0/fileutils.rb:942:in `directory?': no implicit conversion of File::Stat into String (TypeError) from /opt/local/lib/ruby/2.7.0/fileutils.rb:942:in `block (3 levels) in symbolic_modes_to_i' from /opt/local/lib/ruby/2.7.0/fileutils.rb:933:in `each_char' from /opt/local/lib/ruby/2.7.0/fileutils.rb:933:in `each' from /opt/local/lib/ruby/2.7.0/fileutils.rb:933:in `inject' from /opt/local/lib/ruby/2.7.0/fileutils.rb:933:in `block (2 levels) in symbolic_modes_to_i' from /opt/local/lib/ruby/2.7.0/fileutils.rb:931:in `each' from /opt/local/lib/ruby/2.7.0/fileutils.rb:931:in `each_slice' from /opt/local/lib/ruby/2.7.0/fileutils.rb:931:in `block in symbolic_modes_to_i' from /opt/local/lib/ruby/2.7.0/fileutils.rb:926:in `each' from /opt/local/lib/ruby/2.7.0/fileutils.rb:926:in `inject' from /opt/local/lib/ruby/2.7.0/fileutils.rb:926:in `symbolic_modes_to_i' from /opt/local/lib/ruby/2.7.0/fileutils.rb:973:in `fu_mode' from /opt/local/lib/ruby/2.7.0/fileutils.rb:883:in `block in install' from /opt/local/lib/ruby/2.7.0/fileutils.rb:1588:in `block in fu_each_src_dest' from /opt/local/lib/ruby/2.7.0/fileutils.rb:1604:in `fu_each_src_dest0' from /opt/local/lib/ruby/2.7.0/fileutils.rb:1586:in `fu_each_src_dest' from /opt/local/lib/ruby/2.7.0/fileutils.rb:877:in `install' from -e:1:in `<main>' ``` In spite of that `symbolic_modes_to_i` considers the `File::Stat` `path` case at the beginning, in `"X"` case, `path` is passed to `FileTest.directory?` method which requires a `String`. In such case, the mode in `path` should be examined instead. https://github.com/ruby/fileutils/commit/af675af6b2
* [ruby/fileutils] Make verbose output go to stdout instead of stderrJeremy Evans2020-06-122-6/+6
| | | | | | | | | Verbose output is not error output, and should be sent to stdout and not stderr. Fixes Ruby bug 4436 https://github.com/ruby/fileutils/commit/563a383025
* prevent memory allocation for GC testsKoichi Sasada2020-06-121-3/+7
| | | | | | | | We observed test failures on test_latest_gc_info with random order CI. http://ci.rvm.jp/results/trunk-random1@phosphorus-docker/2998078l0ll To solve it, use a pre-allocated hash object and rehearsal.
* .gdbinit: struct RHash::basic is not a pointer卜部昌平2020-06-121-3/+3
|
* .gdbinit: as.heap.aux.shared no longer exist卜部昌平2020-06-121-1/+1
| | | | Maybe 182ae1407b3f6597cdbf6872f788c1ed3aa22a35 missed it.
* Make mutating the result of SortedSet#to_a not affect the setJeremy Evans2020-06-112-1/+4
| | | | Fixes [Bug #15834]
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-21 20:07:26 +0000