Definitelytyped: Travis CI build timeout
When submitting PRs for node or other definitions with a lot of dependents, the Travis CI builds fails because the job time limit is exceeded (50 minutes according to Travis documentation ). See for example PR #20185
Loghorn
👍6
All 3 comments
andrewstucki
on 26 Oct 2017
@RyanCavanaugh @andy-ms Any idea how CI for node could be improved? Currently changing something in node definitions is a pain as we either see unrelated fails after dtlint/typescript update and/or CI timeouts.
As CI fails PRs get not merged instead submitters are instructed to fix the CI fail...
see #21253, #20542, #20695, #21012, #21003, #20720 (and maybe more)
Flarna
on 5 Nov 2017
👍4
Just idea: moving to CircleCI 2.0
- faster than Travis (I feel)
- the workflow feature can parallelize job
- the timeout limit is 120 minutes (travis is 50 min)
teppeis
on 6 Nov 2017
Was this page helpful?
0 / 5 - 0 ratings
Related issues
demisx
·
3Comments
alisabzevari
·
3Comments
stevermeister
·
3Comments
jgoz
·
3Comments
variousauthors
·
3Comments
Most helpful comment
@RyanCavanaugh @andy-ms Any idea how CI for node could be improved? Currently changing something in node definitions is a pain as we either see unrelated fails after dtlint/typescript update and/or CI timeouts.
As CI fails PRs get not merged instead submitters are instructed to fix the CI fail...
see #21253, #20542, #20695, #21012, #21003, #20720 (and maybe more)