diff options
| author | mame <mame@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-09-02 13:55:12 +0000 |
|---|---|---|
| committer | mame <mame@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2017-09-02 13:55:12 +0000 |
| commit | f34090ca4b6bd35e8f8ef66895285600bc4a7771 (patch) | |
| tree | 6af3742a2aa8f40a8b6ca32b9db14fce889b9411 /string.c | |
| parent | 1e9fad234adbeaf18f8122c713d8318d0ef0639b (diff) | |
test/coverage/test_coverage.rb: run the tests in separated processes
The tests had been disabled under coverage measurement (during
`ENV['COVERAGE']`), since they call `Coverage.result` which stops
coverage measurement.
So, we couldn't measure both C-level and Ruby-level coverage of Ruby
simultaneously.
In short, `./configure --enable-gcov && make exam COVERAGE=true`
misses some coverages.
Now, the test runs in another process. They does not stop coverage
measurement, so we can now enable the tests under coverage measurement.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59724 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'string.c')
0 files changed, 0 insertions, 0 deletions