diff options
author | Yusuke Endoh <mame@ruby-lang.org> | 2019-07-21 22:30:15 +0900 |
---|---|---|
committer | Yusuke Endoh <mame@ruby-lang.org> | 2019-07-21 22:30:15 +0900 |
commit | 08ea9240437bd866ae1169a91010d7767a22c9c1 (patch) | |
tree | d6c9f6ce372916fa0c23ad00034137a9e5f5049e /defs | |
parent | 24712eeec39f5e9a11cfc2b940358403cda4f2b6 (diff) |
common.mk: `make check` now includes `make test-tool`
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.
Diffstat (limited to 'defs')
0 files changed, 0 insertions, 0 deletions