Skip to content

dx: retry once without the remote cache on remote cache errors - #10115

Draft
TrapsterDK wants to merge 2 commits into
mainfrom
dx-cache-retry
Draft

TrapsterDK wants to merge 2 commits into
mainfrom
dx-cache-retry

Conversation

@TrapsterDK

Copy link
Copy Markdown
Collaborator

Closes #10042

Stacked on #10056 (both touch the dx Bazel invocation); draft until that lands.

  • RestartingRunner runs a failed Bazel build/test/coverage call once more with --remote_cache= --noremote_accept_cached when the build event stream's progress stderr (test output blocks skipped) has an ERROR: line about the remote cache. Detection is dx_bep::stream_remote_cache_error.
  • Enabled for dx build, test, coverage, check. A notice prints at the retry and a stderr summary line counts retried calls.
  • --no-retry turns it off. Docs and --help updated.
  • Tests: fake runner with a failing-cache BEP stream (retry once, no retry without error / on success / with --no-retry), argv rewrite, BEP parsing, flag parsing, help golden.

Checked: //cli/bep:dx_bep_test //cli/plan:dx_plan_test //cli/cli:dx_cli_test pass. Nested-Bazel and consumer tests were not run (CI runs them).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xut2hwESun1HL2eSVd1d5B

@TrapsterDK
TrapsterDK force-pushed the dx-quiet-progress branch 2 times, most recently from 251b44b to 8a2bc03 Compare November 9, 2026 16:29
Base automatically changed from dx-quiet-progress to main November 9, 2026 16:34

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant