summaryrefslogtreecommitdiff
path: root/tool
AgeCommit message (Collapse)Author
2019-09-05Add a temporal stack dumper for debugging on trunk-mjitYusuke Endoh
This must be definitely removed after we collect the stack traces :-) http://ci.rvm.jp/results/trunk-mjit@silicon-docker/2245710
2019-09-05Removed -git option of make-snapshotNobuyoshi Nakada
Git is not for direct access to a remote repository. Most of its operations need a local clone.
2019-09-05Separate VCS::DEBUG_OUTNobuyoshi Nakada
2019-09-04Use `git pull` instead of `git fetch` if master branchKazuhiro NISHIYAMA
2019-09-04Check frozen flag on MJIT setinstancevariableTakashi Kokubun
It does not seem to have a significant performance impact, hopefully? ``` $ benchmark-driver -v benchmark.yml --rbenv 'before --jit;after --jit' --repeat-count=24 --output=all before --jit: ruby 2.7.0dev (2019-09-03T21:02:24Z master 77596fb7a9) +JIT [x86_64-linux] after --jit: ruby 2.7.0dev (2019-09-04T01:54:44Z master 7363e22d79) +JIT [x86_64-linux] Calculating ------------------------------------- before --jit after --jit Optcarrot Lan_Master.nes 48.44054595799523 71.67010255902900 fps 71.32797692837639 71.97846863769546 72.51921961607691 78.87360980544105 73.54082925611047 79.80408132389941 74.03503843709451 79.85739528572826 74.04863857926493 79.89850834901381 75.30266276129467 80.34607233076015 75.69063990896244 80.88474397425360 75.70458132587405 81.09234267781642 77.39842764662852 82.13766823612643 77.76922944068329 82.20398304840373 81.17984044023393 82.26722630628272 82.85235776076533 82.71375902781254 83.04906099135320 82.75893420702198 83.10214168136230 82.79668965325972 83.71456007558125 82.85131667916379 84.06658306760725 82.95676565411722 84.25690684305728 83.19972846225775 84.27938663923503 83.28510503845854 84.45467716218090 83.41003730434703 84.51563186125925 83.67773614721280 84.56139892968321 84.02082201151110 84.69819452180658 84.10495346787033 84.78125989622576 84.47867803506055 ``` Note for backporter: test_jit's `success_count` would be 1 in Ruby 2.6, since 2.7 introduced "MJIT recompile" on JIT-ed code cancel. [Bug #16139]
2019-09-03Avoid defining unused instructionsTakashi Kokubun
Notes: Merged: https://github.com/ruby/ruby/pull/2420
2019-09-03Touch tar file itself to make gz file hash stableNobuyoshi Nakada
2019-09-03Touch the toplevel directory tooNobuyoshi Nakada
2019-09-03--date=iso-local does not work with old gitNobuyoshi Nakada
2019-09-03Do not keep tar file by the defaultNobuyoshi Nakada
2019-09-03Align timestamps to make tarball stableNobuyoshi Nakada
2019-09-03Use -z option for git-logNobuyoshi Nakada
2019-09-02Extract git commit log as raw format like git-svn for ChangeLogNobuyoshi Nakada
2019-09-02Set mtime of checked out files to past timeNobuyoshi Nakada
instead of waiting 2 seconds, if possible.
2019-09-02Fixed the directory to be removedNobuyoshi Nakada
2019-09-01Restore pwd for each versionNobuyoshi Nakada
2019-09-01Support packaging different branch/tagNobuyoshi Nakada
2019-09-01Fetch commit notesNobuyoshi Nakada
2019-09-01Resolve symlinks to cache directory under gemsNobuyoshi Nakada
2019-09-01Support git tagsNobuyoshi Nakada
2019-08-31Remove files/directories for git/github which are committed [ci skip]Nobuyoshi Nakada
2019-08-31tool/rbinstall.rb: remove a keyword-argument warningYusuke Endoh
2019-08-30Exclude ripper y.output from packages [ci skip]Nobuyoshi Nakada
2019-08-30Export the last modified revision for tags [ci skip]Nobuyoshi Nakada
2019-08-30Suppress uninitialized instance variable warnings [ci skip]Nobuyoshi Nakada
2019-08-30Support revision in git-svn logNobuyoshi Nakada
2019-08-30Updated comment of VCS#get_revisions [ci skip]Nobuyoshi Nakada
2019-08-307z does not accept gzip's optionsKazuhiro NISHIYAMA
e.g. `GZIP=-9`
2019-08-29Don't pick up lib/readline.rb from ruby/relineaycabta
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-20 01:05:22 +0000