aboutsummaryrefslogtreecommitdiffstats
path: root/lib/runtime_tools
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2012-10-22 16:06:32 +0200
committerSiri Hansen <[email protected]>2012-10-30 11:18:41 +0100
commitf6c1c3127f027cd717d01613cd356c5ada35041c (patch)
treeff80989d4bc38693f3d88d0e7ae2a5c2e0f69c78 /lib/runtime_tools
parent0c924848a3f7bae6fe3d4f2b5d4d47277e45665b (diff)
downloadotp-f6c1c3127f027cd717d01613cd356c5ada35041c.tar.gz
otp-f6c1c3127f027cd717d01613cd356c5ada35041c.tar.bz2
otp-f6c1c3127f027cd717d01613cd356c5ada35041c.zip
[common_test] Add option cover_stop
By default, test_server will always stop cover (and thus load back the non cover compiled original beam files) after a test with code coverage analysis is completed. The new option allows the common_test user to specify that cover shall not be stopped. This can be useful if there are processes still running old code, i.e. processes that have not done any fully qualified function call after the cover compilation, since loading the original code then will kill those processes. This is only recommended if the erlang node is to be stopped after the test run, or if cover can be manually stopped.
Diffstat (limited to 'lib/runtime_tools')
0 files changed, 0 insertions, 0 deletions