Conversation
Current coverage is 87.42% (diff: 100%)
|
- use only half of the workers by running self-compilation tests after normal tests - only recompile and retest dmd, not druntime/phobos
|
Half an hour, not that much, but still halves the number of jobs we're enqueuing. |
f1b9e3e to
68c4000
Compare
|
Maybe we should also cancel builds if more recent commits have been pushed? I couldn't find a setting for Travis CI (there is one for CircleCI, "Advanced Settings” -> “Auto-cancel builds”), but I guess the only thing that might work is a bot that does this auto-canceling like travis_dedup. Thus deploying travis_dedup to heroku might be a simple solution, depending on our CI load one might need to verify the account there (unverified accounts get 550 hours / month (=23 days), verified 1000 hours / month (=41days), a dyno sleeps after 30 minutes of inactivity and is automatically waked up on incoming requests more . What do you think @MartinNowak? Worth deploying or using option (c) to install the checker & cancel at the beginning of the build? |
I presume that also means that if any of the normal tests fail, the coverage tests are not run? Makes sense. |
No, the coverage stuff runs in parallel on CircleCI independent of what happens w/ Travis-CI. |
Could easily add that functionality to dlang-bot, that already runs 24/7 and gets all the github hooks. |
|
Auto-merge toggled on |
check and cancel redundant Travis-CI builds · MartinNowak/dlang-bot@875d76c |
tests after normal tests
depends on #6022