| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixed new Struct-related keyword argument warnings
|
| |
|
|
|
|
| |
Fixing a bug on Windows introduced in v0.15.0
|
|
|
|
|
| |
It got some nice features for better support of
benchmark_driver-output-charty, Windows, ridk, and rbenv.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Rules which have used CPPFLAGS will need XCFLAGS or INCFLAGS now.
|
|
|
|
|
| |
INCFLAGS is not included in CPPFLAGS on mswin, not to be exported
to rbconfig.rb.
|
|
|
|
|
|
| |
Flags for ruby core such as warning and `_FORTIFY_SOURCE` macro
are not necessary to make fake.rb, except for `RUBY_EXPORT` macro
which prevents to include ruby/backward.h.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
| |
thread.c requires gc.h on mswin build. Sorry.
|
|
|
|
|
|
|
|
| |
debug utility macro rp() (rp_m()) and bp() are introduced.
* rp(obj) shows obj information w/o any side-effect to STDERR.
* rp_m(m, obj) is similar to rp(obj), but show m before.
* bp() is alias of ruby_debug_breakpoint(), which is registered
as a breakpoint in run.gdb (used by `make gdb` or make gdb-ruby`).
|
| |
|
|
|
|
|
| |
just fix CI failure
https://travis-ci.org/ruby/ruby/jobs/569625233
|
|
|
|
|
| |
as I already started to use --runner=block introduced in v0.14.20 like:
https://github.com/ruby/ruby/pull/2321#issuecomment-518638663
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|