summaryrefslogtreecommitdiff
path: root/tool
AgeCommit message (Collapse)Author
2019-08-28Revert "Treat RUBY_REVISION as an integer on old rubies"Nobuyoshi Nakada
This reverts commit 6454808c52fff445ff09fefb0fb96988f82aaa3c. It is no longer needed, as `VCS::SVN#get_revisions` now returns `Integer` as revision numbers, and `short_revision` should deal with it.
2019-08-28`revision` might be an IntegerNAKAMURA Usaku
2019-08-28tool/merger.rb: fix tag existence check with subversion.nagachika
2019-08-28Ensure the last and changed revisions as IntegersNobuyoshi Nakada
2019-08-28Treat RUBY_REVISION as an integer on old rubiesNAKAMURA Usaku
2019-08-27Short revision of SVN should be an IntegerNobuyoshi Nakada
2019-08-27Pick lib/readline.rb from ruby/relineaycabta
2019-08-26Limit ChangeLog entriesNobuyoshi Nakada
Since the previous release date, when the starting message is not found.
2019-08-25`local_path?` is a class method [ci skip]Nobuyoshi Nakada
2019-08-25tool/lib/vcs.rb: explicitly fail when notes/commits is not availableYusuke Endoh
2019-08-25Revert workaroundKazuhiro NISHIYAMA
2019-08-25Simplified f13a00f5b4 [ci skip]Nobuyoshi Nakada
2019-08-25Export all commits as ChangeLog when no starting commit is found [ci skip]Nobuyoshi Nakada
2019-08-25Add workaround (2nd try)Kazuhiro NISHIYAMA
https://rubyci.org/logs/rubyci.s3.amazonaws.com/gentoo/ruby-master/log/20190824T153002Z.fail.html.gz ``` /home/gentoo/chkbuild/tmp/build/20190824T153002Z/ruby/tool/lib/vcs.rb:577:in `export_changelog': cannot find the beginning revision of the branch (RuntimeError) from ./tool/make-snapshot:353:in `block in package' from ./tool/make-snapshot:351:in `chdir' from ./tool/make-snapshot:351:in `package' from ./tool/make-snapshot:523:in `block in <main>' from ./tool/make-snapshot:523:in `collect' from ./tool/make-snapshot:523:in `<main>' ```
2019-08-24Add workaround for some CIsKazuhiro NISHIYAMA
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian8/ruby-master/log/20190824T093005Z.fail.html.gz ``` branches: * trunk remotes/origin/trunk ``` and ``` fatal: Remote branch master not found in upstream origin ```
2019-08-24Add debug printKazuhiro NISHIYAMA
matser branch not found on some CIs https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian9/ruby-master/log/20190824T063005Z.fail.html.gz ``` fatal: Remote branch master not found in upstream origin ```
2019-08-24Try to fix `make dist` error on chkbuildKazuhiro NISHIYAMA
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian9/ruby-master/log/20190823T213004Z.fail.html.gz https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian8/ruby-master/log/20190824T003006Z.fail.html.gz
2019-08-23Ensure all default gems have an gem folderDavid Rodríguez
Even if they don't ship with any executables. This makes rbinstall behaviour consistent with rubygems `gem install --default` command. Notes: Merged: https://github.com/ruby/ruby/pull/2085
2019-08-20Removed unused literal assignments [ci skip]Nobuyoshi Nakada
2019-08-20Subjects may contain a comma [ci skip]Nobuyoshi Nakada
2019-08-20Fix some bundler specs (#2380)David Rodríguez
* These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
2019-08-19Omit version.h when mergingNAKAMURA Usaku
2019-08-18Use master branch instead of trunk.Hiroshi SHIBATA
2019-08-18Ignore tags on default gems from ruby core repository.Hiroshi SHIBATA
2019-08-18Gem::ConfigMap is deprecated nowHiroshi SHIBATA
2019-08-18Fix copy path of ruby/reline's testaycabta
2019-08-14Move some assertions to CoreAssertions. (#2354)SHIBATA Hiroshi
They are used by default gems like forwardable. * assert_raise_with_message * assert_warning * assert_warn Notes: Merged-By: hsbt <hsbt@ruby-lang.org>
2019-08-13Detect VCS from the current directory by default [ci skip]Nobuyoshi Nakada
2019-08-13Push commits notes too [ci skip]Nobuyoshi Nakada
2019-08-12Include commits notes in ChangeLogNobuyoshi Nakada
2019-08-12We did not have tool/ before checkoutTakashi Kokubun
anyway we don't need authorization here. Also retry does not seem to work in the original version, so let's extend this with retries as a separate github action later.
2019-08-12Stop relying on actions/checkoutTakashi Kokubun
because it randomly fails on authorization like: https://github.com/ruby/ruby/runs/190887455 Also the backoff seems too short. Maybe we need tool/travis_retry.sh for this too. Cloning ruby/ruby does not need authorization. We don't need to use actions/checkout.
2019-08-11Use `end_with?` instead of Regexp with missing escapeKazuhiro NISHIYAMA
2019-08-09complement `test_` prefix.Koichi Sasada
`make test-all TESTS=name` can specify running test files by name. name can be dirname ('dir/') or a file ('.../test_foo.rb'). This patch complement `test_` prefix for a test. So we only need to specify `TESTS=ruby/hash` which means `TESTS=ruby/test_hash.rb`.
2019-08-08Aliases capture_output to capture_io for test-unit compatiblity.Hiroshi SHIBATA
2019-08-07Added separator for failing commits from default gems.Hiroshi SHIBATA
2019-08-07Skip merge commit created by bundlerbot.Hiroshi SHIBATA
2019-08-07Refactor .travis.yml by introducing travis_retry.shTakashi Kokubun
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>
2019-08-05Moved FailDesc to EnvUtil.failure_descriptionNobuyoshi Nakada
So EnvUtil does not depends on test/unit.
2019-08-04Fix release post output for tool/format-releaseMarcus Stollsteimer
Different entries should be separated by an empty line. Closes: https://github.com/ruby/ruby/pull/2137
2019-08-03Move assert_ruby_status and assert_throw to CoreAssertions for default gems.Hiroshi SHIBATA
2019-08-03Added more attributes [ci skip]Nobuyoshi Nakada
2019-08-03Refine error messageNobuyoshi Nakada
Highlight failed command and suggest installing the command. [Bug #16042]
2019-08-02It can be share to use CoreAssertions for default gems.Hiroshi SHIBATA
ref. https://github.com/ruby/logger/pull/35
2019-07-31backtrace can be nil.Koichi Sasada
Surprisingly, on SystemStackError#backtrace can return nil.
2019-07-31Revert "add debug code"Koichi Sasada
This reverts commit e83ec207cd5fda973c41d6629d8504b515522b12.
2019-07-31add debug codeKoichi Sasada
2019-07-30Separate VCS::GIT#upstreamNobuyoshi Nakada
2019-07-27tool/merger.rb: execute 'svn update' after 'svn ci' to update revision info ↵nagachika
on working copy.
2019-07-27Skip the some of commits when sync default gems from upstream.Hiroshi SHIBATA
* Skip failed to sync commits because it needs to pick manually. * Skip empty commit.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-08 02:13:38 +0000