aboutsummaryrefslogtreecommitdiffstats
path: root/make
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2015-01-26 11:52:05 +0100
committerBjörn Gustavsson <[email protected]>2015-01-26 16:18:27 +0100
commit8a2f26a103e0538cbe571d2bd8b1eb87cfe42743 (patch)
tree5fadb9fec81499f29d54cd5beaa91b4354e11eea /make
parente2001315febed13f8889ff1a33c046f36a4c8c54 (diff)
downloadotp-8a2f26a103e0538cbe571d2bd8b1eb87cfe42743.tar.gz
otp-8a2f26a103e0538cbe571d2bd8b1eb87cfe42743.tar.bz2
otp-8a2f26a103e0538cbe571d2bd8b1eb87cfe42743.zip
Speed up running of compiler test suites in coverage mode
I have spent too much time lately waiting for 'cover' to finish, so now its time to optimize the running time of the tests suite in coverage mode. Basically, when 'cover' is running, the test suites would not run any tests in parallel. The reason is that using too many parallel processes when running 'cover' would be slower than running them sequentially. But those measurements were made several years ago, and many improvements have been made to improve the parallelism of the run-time system. Experimenting with the test_lib:p_run/2 function, I found that increasing the number of parallel processes would speed up the self_compile tests cases in compilation_SUITE. The difference between using 3 processes or 4 processes was slight, though, so it seems that we should not use more than 4 processes when running 'cover'. We don't want to change test_lib:parallel/0, because there is no way to limit the number of test cases that will be run in parallel by common_test. However, there as test suites (such as andor_SUITE) that don't invoke the compiler at run-time. We can run the cases in such test suites in parallel even if 'cover' is running.
Diffstat (limited to 'make')
0 files changed, 0 insertions, 0 deletions