Age | Commit message (Collapse) | Author |
|
|
|
|
|
As `make test-tool` does not use gems, and no Rubygems stuffs is
needed, so moved such things to test/runner.rb. Also no longer
nees `--test-target-dir` option.
|
|
|
|
Raise the proper exception when that option is not given but
non-option argument is.
|
|
And `make test-tool` includes `make test-testframework`.
This change may be arguable because I'm unsure who is an intended user
of `make check`: a normal user, or Ruby-core developer. Normal users
don't have to run `make test-tool` for testing their installation, but
Ruby committers should run it before they commit anything.
In this case, I'd be conservative; `make check` includes `test-tool`.
If normal users often report a failure of `make test-tool`, then we can
consider to split `make check` for two sets of target users.
|
|
tool/test/runner.rb had been copied from test/runner.rb.
test/runner.rb was for `make test-all`, and tool/test/runner.rb was for
`make test-testframework` and `make test-tool`.
But I want to avoid the code clones.
This change makes tool/test/runner.rb support --test-target-dir option
which allows tool/test/runner.rb to run `make test-all`.
Now we can remove test/runner.rb.
|
|
|
|
because v0.14.18 was actually not working with `make run`.
In `make run`, `Gem` is defined but `Gem::Version` isn't.
v0.14.19 checks `defined?(Gem::Version)` instead of `defined?(Gem)`.
|
|
This is to make `make run` with benchmark/lib/load.rb work for ko1
https://github.com/benchmark-driver/benchmark-driver/compare/v0.14.17...v0.14.18
|
|
|
|
|
|
|
|
|
|
1f99274ccf31ba1f2a4b3ac20a9c6cdc5ae81152 was indenting details with a
hard tab, but other lines are using spaces.
|
|
similar to 364f43ab7fc5920247fc73423c1428208cf78a4a and
13cb9e6bd2c88d04fc9b21b8f8c1d192c67cd5a2
|
|
|
|
Currently it is completely the same as "make check".
I think it is not worth mentioning now.
|
|
|
|
because we're not writing ChangeLog anymore.
|
|
We've added some more things recently. It seems not worth having almost
the same two entries there anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They are moved under the tool directory now.
|
|
direcotry.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 4c0e21add7c87b70df27fbff81d8f192a467556d
because we're not using /bin/bash.
See 11d3986d6557eb3cfcecbdd0ef6e21b18c7c960b and
1b2b0e1f244b3e71812fa9859e8b87150ea30434 to know its context.
In short, 4c0e21add7c87b70df27fbff81d8f192a467556d does not work on
Ubuntu.
|
|
Since 72ad092960c413b6a5687c552747b20a5ed78b22, we cannot run full `make benchmark`
because default BENCH_RUBY is miniruby and it fails to require 'time'.
Using miniruby for benchmark by default seems reasonable for some cases,
but now it's just bothering for people running full `make benchmark`.
|
|
|
|
This reverts commit 05bc14d81a1d7f6af826a92371aeff0c3fb2a67e.
We have decided that the cost of reintroducing support for 1.8
BASERUBY outweighs the benefit. If you are still using 1.8 and want
to build master/trunk, build and install the latest release, and use
that as BASERUBY.
|
|
|
|
|
|
is yes.
We ignored the failure status of file2lastrev.rb on 73da429c36c, but it
was for an environment without BASERUBY. I think we should skip running
file2lastrev.rb on HAVE_BASERUBY=no, and run it and check the status on
HAVE_BASERUBY=yes.
Otherwise we may have an ignored arbitrary error of file2lastrev.rb on
HAVE_BASERUBY=yes environment.
|
|
|
|
Unicode version 12.1.0 was officially released on May 7th, 2019.
There were no changes at all from the "real" beta
published shortly after the new era name "Reiwa" was announced.
So we can switch UNICODE_BETA back to NO.
common.mk: switch UNICODE_BETA back to NO
tool/downloader.rb: add additional conditions to avoid an error
when moving from beta to final
|
|
|
|
|
|
[Misc #15859]
|
|
|
|
|
|
to run tool/sync_default_gems.rb
|