Closed jbedard closed 3 months ago
Are there any relevant go docs describing this that are worth linking to?
2 test targets passed
//docs:update_0_test [k8-fastbuild] 60ms //npm/private/test:write_npm_translate_lock_bzlmod_0_test [k8-fastbuild] 327ms
Total test execution time was 387ms. 191 tests (99.0%) were fully cached saving 47s.
All tests were cache hits
5 tests (100.0%) were fully cached saving 631ms.
All tests were cache hits
2 tests (100.0%) were fully cached saving 516ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 6s.
All tests were cache hits
3 tests (100.0%) were fully cached saving 925ms.
All tests were cache hits
3 tests (100.0%) were fully cached saving 925ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 59ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 59ms.
All tests were cache hits
2 tests (100.0%) were fully cached saving 184ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 55ms.
All tests were cache hits
3 tests (100.0%) were fully cached saving 770ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 167ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 59ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 59ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 507ms.
All tests were cache hits
40 tests (100.0%) were fully cached saving 16s.
All tests were cache hits
10 tests (100.0%) were fully cached saving 7s.
All tests were cache hits
10 tests (100.0%) were fully cached saving 4s.
All tests were cache hits
2 tests (100.0%) were fully cached saving 324ms.
All tests were cache hits
2 tests (100.0%) were fully cached saving 562ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 251ms.
Changes are visible to end-users: no
Test plan