Practise the standard verbs for configuring Bazel's build graph cache.
0 / 5 completed
1 / 5
Fill in: 'We ___ a remote cache for the build graph so a colleague's already-built target is reused instead of every developer recompiling the same dependency from scratch.'
We 'configure a cache' — the standard collocation for setting up shared storage for build outputs. The other options aren't idiomatic here.
2 / 5
Fill in: 'Declaring a build action with a hidden, undeclared input file can ___ the cache silently serving a stale output whenever that file changes without a rebuild being triggered.'
We say an undeclared input will 'leave' the cache serving stale output — the standard, natural collocation for the resulting bug. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the build graph's action count after a BUILD file refactor, since an unexpectedly large jump often means a target is depending on far more than it should.'
We 'inspect' an action count — the standard, simple collocation for examining a build metric after a structural change. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the cache hit rate across CI builds weekly, since a dropping ratio usually means a target's inputs have started changing more often than the cache design assumed.'
We 'track a hit rate' — the standard, simple collocation for following a caching-effectiveness metric over time. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the remote cache deliberately after a toolchain upgrade, so a build artefact produced under the old compiler isn't mistakenly reused under the new one.'
We 'invalidate a cache' — the standard, established collocation for deliberately discarding entries that are no longer valid. The other options aren't the recognised term here.