step only saves the cache if the entire job finishes successfully. Step-by-Step Debugging 1. Enable Step Debug Logging
Prune unused caches via the GitHub API or the web UI, and optimize cache paths to exclude unnecessary log directories or temporary text files. 3. Advanced Diagnostic Steps Using the GitHub CLI ( gh )
Bazel caches the results of build actions based on an "action key." This key is a hash that includes: Input file contents (hashes). debug-action-cache
Once you have basic visibility, you can move to advanced diagnostics.
Compilers or code generators that embed the current time into the binary. step only saves the cache if the entire
The deterministic key evaluated identically to a previous run because the lockfile did not change, or the key string lacks a dynamic hash.
These actions can be expensive in terms of computational resources and time. The Debug Action Cache aims to alleviate this problem by caching the results of these actions, allowing developers to quickly retrieve previously computed results. Compilers or code generators that embed the current
# On the self-hosted machine sudo find / -name "node_modules" -path "*/actions-runner/_work/*" -type d