Closed plobsing closed 2 months ago
All tests were cache hits
193 tests (100.0%) were fully cached saving 38s.
All tests were cache hits
5 tests (100.0%) were fully cached saving 1s.
All tests were cache hits
2 tests (100.0%) were fully cached saving 236ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 7s.
All tests were cache hits
3 tests (100.0%) were fully cached saving 839ms.
All tests were cache hits
3 tests (100.0%) were fully cached saving 745ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 27ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 27ms.
All tests were cache hits
2 tests (100.0%) were fully cached saving 296ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 112ms.
All tests were cache hits
3 tests (100.0%) were fully cached saving 716ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 192ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 81ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 81ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 713ms.
All tests were cache hits
40 tests (100.0%) were fully cached saving 3s.
All tests were cache hits
10 tests (100.0%) were fully cached saving 2s.
All tests were cache hits
10 tests (100.0%) were fully cached saving 2s.
All tests were cache hits
2 tests (100.0%) were fully cached saving 233ms.
All tests were cache hits
2 tests (100.0%) were fully cached saving 141ms.
All tests were cache hits
1 test (100.0%) was fully cached saving 171ms.
When this attribute is not set in the call to
npm_translate_lock
, the queries return no results, thepackage_json.bzl
file is not directly findable, and users may be very confused.Changes are visible to end-users: no
Test plan
Manually confirmed the queries work after setting this setting but not before. See also https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1724827171385349 .