Fail benchmarks on cache action errors #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-bench-cache-failures"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The benchmark scripts were ignoring cache-action failures in their restore and save helpers. A broken restore or save could still produce benchmark rows, which can make a warm run look valid when the cache path failed.
This makes the Rust, Node, and Go benchmark helpers fail the script when the cache action exits nonzero, while still printing the captured cache-action log for diagnosis.
Tests run: