sstriker opened a new pull request, #2109:
URL: https://github.com/apache/buildstream/pull/2109

   Closes #2083
   
   ## Summary
   
   Speculative actions speed up rebuilds by pre-populating the action cache 
with adapted versions of previously recorded build actions. When a dependency 
changes, compile and link commands from the previous build are adapted with 
updated input digests and executed ahead of the actual build, so recc gets 
action cache hits instead of executing from scratch.
   
   - **Recording**: subactions captured via recc through `remote-apis-socket` 
during sandbox execution
   - **Generation**: after each build, overlays describe how each subaction's 
inputs relate to source elements and dependency artifacts
   - **Storage**: speculative actions stored on artifact proto under the weak 
cache key (stable across dependency version changes)
   - **Priming**: before each rebuild, stored actions are instantiated with 
current dependency digests and submitted fire-and-forget
   - **Tiered modes**: 
`none`/`prime-only`/`source-artifact`/`intra-element`/`full` — lets users 
control cost vs benefit
   
   See `doc/source/arch_speculative_actions.rst` for the full architecture 
documentation including example scenarios.
   
   ## Dependencies
   
   - Depends on: 
https://gitlab.com/BuildGrid/buildbox/buildbox/-/merge_requests/1080
   
   ## Test plan
   
   - [x] 46 unit tests (generator, instantiator, pipeline integration, weak 
key, modes)
   - [x] 5 integration tests with real sandbox + recc + buildbox-casd
   - [x] Full test suite: 1753 passed, 0 failed
   - [ ] End-to-end with [freedesktop-sdk 
sstriker/recc](https://gitlab.com/sstriker/freedesktop-sdk/-/tree/sstriker/recc?ref_type=heads)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to