test: optimize total Travis run time #27182
Conversation
1d940ba
to
f3b8644
Compare
|
This configuration can potentially finish in 6 + 5 minutes P.S. Success |
(Ab)using the ccache to transfer binaries between compile and test jobs
Maybe update the OP? Stages haven't been eliminated. |
9d4dae1
to
92eb382
Compare
|
Travis run now covers addons as well. minimal time approx 4(compile) + 5.5(test) minutes. |
|
Current With just just With So I'd call this a win. |
https://travis-ci.com/nodejs/node/jobs/192591927 ran 2500 tests. |
Ah it's Lines 502 to 506 in 25df3c1 Lines 472 to 474 in 25df3c1 |
* skip compilation by using cache * split testing into two jobs * DRY with YAML anchors PR-URL: nodejs#27182 Refs: nodejs#27158 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Refs: #27158
Eliminates the stages; they are unnecessary for a typical CI run, and extend the run time by at least 3.5 minutes.Instead of eliminating the compile stage it now caches the binary so the test stage doesn't need to bootstrap the compiler and doesn't need to recompile.
/CC @nodejs/testing @nodejs/build-files @nodejs/python
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes