aboutsummaryrefslogtreecommitdiffstats
path: root/common.mk
Commit message (Collapse)AuthorAgeFilesLines
* Comparable#clamp with a range [Feature #14784]Nobuyoshi Nakada2019-10-161-0/+2
|
* make rb_raise a GVL-only function again卜部昌平2019-10-101-2/+0
| | | | | | Requested by ko1 that ability of calling rb_raise from anywhere outside of GVL is "too much". Give up that part, move the GVL aquisition routine into gc.c, and make our new gc_raise().
* Now error.o needs thread.hNobuyoshi Nakada2019-10-101-0/+1
|
* allow rb_raise from outside of GVL卜部昌平2019-10-101-0/+1
| | | | | | | | | | | | | | | Now that allocation routines like ALLOC_N() can raise exceptions on integer overflows. This is a problem when the calling thread has no GVL. Memory allocations has been allowed without it, but can still fail. Let's just relax rb_raise's restriction so that we can call it with or without GVL. With GVL the behaviour is unchanged. With no GVL, wait for it. Also, integer overflows can theoretically occur during GC when we expand the object space. We cannot do so much then. Call rb_memerror and let that routine abort the process.
* Added dependencies on prerequisite makefilesNobuyoshi Nakada2019-10-051-3/+3
|
* Use benchmark-driver v0.15.6Takashi Kokubun2019-09-191-1/+1
| | | | to fix another keyword argument warning which was added recently.
* Upgrade benchmark_driver to v0.15.5Takashi Kokubun2019-09-131-1/+1
| | | | Fixed new Struct-related keyword argument warnings
* Fixed wrong usage of file2lastrev.rbNobuyoshi Nakada2019-09-071-1/+1
|
* Upgrade benchmark-driver to v0.15.4Takashi Kokubun2019-09-071-1/+1
| | | | Fixing a bug on Windows introduced in v0.15.0
* Upgrade benchmark-driver to v0.15.3Takashi Kokubun2019-09-071-1/+1
| | | | | It got some nice features for better support of benchmark_driver-output-charty, Windows, ridk, and rbenv.
* Explain how to run an individual btest in helpTakashi Kokubun2019-09-031-1/+1
|
* Upgrade benchmark-driver for keyword args warningsTakashi Kokubun2019-09-011-1/+1
|
* Show MFLAGS to check `Set ENV` in .github/workflows/ubuntu.ymlKazuhiro NISHIYAMA2019-08-261-0/+1
|
* CPPFLAGS is not needed for linkNobuyoshi Nakada2019-08-261-1/+1
|
* Moved INCFLAGS to XCFLAGS from CPPFLAGS as well as mswinNobuyoshi Nakada2019-08-261-1/+1
| | | | Rules which have used CPPFLAGS will need XCFLAGS or INCFLAGS now.
* Add INCFLAGS for fake.rbNobuyoshi Nakada2019-08-261-1/+1
| | | | | INCFLAGS is not included in CPPFLAGS on mswin, not to be exported to rbconfig.rb.
* Removed unnecessary flags for fake.rbNobuyoshi Nakada2019-08-261-1/+1
| | | | | | 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.
* Use () instead of {} for nmakeHiroshi SHIBATA2019-08-221-2/+2
|
* `--fomart progress` is default. It's duplicated.Hiroshi SHIBATA2019-08-221-1/+1
|
* Introduce test-bundler-parallel task.Hiroshi SHIBATA2019-08-221-1/+9
|
* Fix some bundler specs (#2380)David Rodríguez2019-08-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Prefer exact ITEM to benchmarkNobuyoshi Nakada2019-08-181-1/+1
|
* gc.h is required on mswin build.Koichi Sasada2019-08-091-0/+1
| | | | thread.c requires gc.h on mswin build. Sorry.
* add rp() and bp() in internal.h.Koichi Sasada2019-08-091-1/+0
| | | | | | | | 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`).
* remove useless include and dependencyKoichi Sasada2019-08-091-1/+0
|
* Add missing dependencyTakashi Kokubun2019-08-091-0/+1
| | | | | just fix CI failure https://travis-ci.org/ruby/ruby/jobs/569625233
* Upgrade benchmark-driver versionTakashi Kokubun2019-08-071-1/+1
| | | | | as I already started to use --runner=block introduced in v0.14.20 like: https://github.com/ruby/ruby/pull/2321#issuecomment-518638663
* Shorten dependency hint [ci skip]Nobuyoshi Nakada2019-07-301-1/+1
|
* Hint for the dependency update [Bug #16000]Nobuyoshi Nakada2019-07-301-0/+1
|
* Separated tool/test/runner.rb and test/runner.rbNobuyoshi Nakada2019-07-251-5/+5
| | | | | | 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.
* Retry to update Unicode timestampNobuyoshi Nakada2019-07-231-1/+1
|
* Only the first argument can be --test-target-dir optionNobuyoshi Nakada2019-07-221-5/+5
| | | | | Raise the proper exception when that option is not given but non-option argument is.
* common.mk: `make check` now includes `make test-tool`Yusuke Endoh2019-07-211-4/+3
| | | | | | | | | | | | | 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: support --test-target-dir optionYusuke Endoh2019-07-211-5/+5
| | | | | | | | | | | 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.
* Update simplecov and doclie to the latest version.Hiroshi SHIBATA2019-07-211-2/+2
|
* Upgrade benchmark-driver.gem againTakashi Kokubun2019-07-201-1/+1
| | | | | | 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)`.
* Upgrade benchmark-driver.gem versionTakashi Kokubun2019-07-201-1/+1
| | | | | 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
* Improve build process and coroutine implementation selection.Samuel Williams2019-07-181-2/+1
|
* Fixed the library path for toolsNobuyoshi Nakada2019-07-161-1/+1
|
* Added help message for test-tool target.Hiroshi SHIBATA2019-07-151-0/+1
|
* Added test-tool target for the test suite of tool/test files.Hiroshi SHIBATA2019-07-151-1/+7
|
* Fix unaligned help outputTakashi Kokubun2019-07-151-1/+1
| | | | | 1f99274ccf31ba1f2a4b3ac20a9c6cdc5ae81152 was indenting details with a hard tab, but other lines are using spaces.
* Stop consuming 2 entries for gorubyTakashi Kokubun2019-07-151-2/+1
| | | | | similar to 364f43ab7fc5920247fc73423c1428208cf78a4a and 13cb9e6bd2c88d04fc9b21b8f8c1d192c67cd5a2
* Added the bundled gems target to make help.Hiroshi SHIBATA2019-07-151-0/+2
|
* common.mk: remove "make exam" from helpYusuke Endoh2019-07-151-1/+0
| | | | | Currently it is completely the same as "make check". I think it is not worth mentioning now.
* Unify documentations of `make benchmark`Takashi Kokubun2019-07-151-5/+1
|
* Drop `make change` and tool/change_maker.rbTakashi Kokubun2019-07-151-4/+0
| | | | because we're not writing ChangeLog anymore.
* Reduce the number of make help entriesTakashi Kokubun2019-07-151-2/+0
| | | | | We've added some more things recently. It seems not worth having almost the same two entries there anymore.
* Mention SPECOPTS variable in make helpTakashi Kokubun2019-07-151-1/+1
|
* Include ruby/assert.h in ruby/ruby.h so that assertions can be thereNobuyoshi Nakada2019-07-141-1/+37
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-28 02:21:43 +0000