Capture operation-scoped Bazel profiles - #3339
Draft
karim-alweheshy wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Karim Alweheshy <karim.alweheshy@reddit.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n\n- force Bazel JSON trace output into the proxy operation directory\n- prevent bazelrc settings from redirecting the private operation profile\n- filter diagnostic-only profile and all-action options from publishable receipts and aquery replays\n- secure the finished profile as a regular mode-0600 file on success, failure, or interruption\n\n## Stack\n\n- Base: the live action lifecycle PR\n- This PR is diagnostic plumbing only; profile summarization and presentation remain separate slices\n\n## Validation\n\n- uncached focused launcher test with ignore-all-rc-files\n- bash syntax, ShellCheck, and Buildifier\n- negative coverage for unset profile paths and receipt filtering\n\n## Testing\n\nRun a proxy-enabled operation, verify bazel-profile.json.gz is private to that operation, then bind its invocation UUID to the matching BEP before analysis.