test: optimize total Travis run time

[refack]

• skip compilation by using cache
• split testing into two jobs
• DRY with YAML anchors

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), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

[nodejs-github-bot]

Lite-CI: https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/3230

[refack]

This configuration can potentially finish in 6 + 5 minutes 🚀

P.S. Success

[richardlau]

(Ab)using the ccache to transfer binaries between compile and test jobs ✔️💡.

[richardlau]

Try to cut down the total time for a Travis CI sanity test.

Eliminates the stages; they are unnecessary for a typical CI run, and extend the run time by at least 3.5 minutes.
For PRs that change V8, the first successful run of "Compile V8" will hydrate the cache, so subsequent runs should complete in < 50 minutes

Maybe update the OP? Stages haven't been eliminated.

[refack]

Travis run now covers addons as well. minimal time approx 4(compile) + 5.5(test) minutes.

[refack]

@nodejs/testing @nodejs/build-files PTAL

[refack]

Current master:

With just just parallel for JS coverage (was an in intermediate step)

With default:

So I'd call this a win.

[richardlau]

Current master:

With just just parallel for JS coverage (was an in intermediate step)

With default:

So I'd call this a win.

🤔
https://travis-ci.com/nodejs/node/jobs/192593470 ran 2615 tests.

https://travis-ci.com/nodejs/node/jobs/192591927 ran 2500 tests.
https://travis-ci.com/nodejs/node/jobs/192591928 ran 111 tests.
2500 + 111 = 2611 tests... Any idea what accounts for the discrepency?

[richardlau]

🤔
https://travis-ci.com/nodejs/node/jobs/192593470 ran 2615 tests.

https://travis-ci.com/nodejs/node/jobs/192591927 ran 2500 tests.
https://travis-ci.com/nodejs/node/jobs/192591928 ran 111 tests.
2500 + 111 = 2611 tests... Any idea what accounts for the discrepency?

Ah it's doctool.

node/Makefile

Lines 502 to 506 in 25df3c1

	test-ci: | clear-stalled build-addons build-js-native-api-tests build-node-api-tests doc-only
	out/Release/cctest --gtest_output=tap:cctest.tap
	$(PYTHON) tools/test.py $(PARALLEL_ARGS) -p tap --logfile test.tap \
	--mode=$(BUILDTYPE_LOWER) --flaky-tests=$(FLAKY_TESTS)\
	$(TEST_CI_ARGS)$(CI_JS_SUITES)$(CI_NATIVE_SUITES)$(CI_DOC)

node/Makefile

Lines 472 to 474 in 25df3c1

	CI_NATIVE_SUITES ?= addons js-native-api node-api
	CI_JS_SUITES ?= default
	CI_DOC := doctool