- Notifications
You must be signed in to change notification settings - Fork294
Speed up CI#385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Speed up CI#385
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-io commentedDec 4, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #385 +/- ##======================================= Coverage 90.76% 90.76% ======================================= Files 50 50 Lines 6950 6950 Branches 1328 1328 ======================================= Hits 6308 6308 Misses 483 483 Partials 159 159 Continue to review full report at Codecov.
|
I looked at the master builds for the last 10 rounds and the numbers are kind of all over the place and not consistent. So I'm not sure I see evidence that this will really improve the situation. The specific change here is just reordering the environments which is benign, so I'm going to approve it and land it and we can see how future builds affect the hypothesis. |
For reference, here's the last 10 passing master builds (685-711), latest first: Ran for 20 min 45 sec |
It's usually quicker to have the slower build jobs run first, that way the build isn't waiting as at the end for one or two slow ones to cmoplete.
Taking numbers from a master build, rounding to nearest minutes, gives something like this in theory for five parallel jobs:
In reality:
https://travis-ci.org/hugovk/html5lib-python/builds/310874897
Slowest first, using same numbers:
This PR build:
https://travis-ci.org/hugovk/html5lib-python/builds/309593149