Fix LZBench timeout and result ownership#762
Merged
Merged
Conversation
Run the benchmark as the VC user and keep its result file in the VC-owned temp directory so ARM64 cleanup does not cross privilege boundaries. Report cancellation as a workload failure instead of a successful execution. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: f3bc03fa-5da5-4a69-94e1-d6adc0cbe5db
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
ericavella
approved these changes
Jul 22, 2026
Signed-off-by: AlexWFMS <alexwill+work@microsoft.com>
ericavella
approved these changes
Jul 22, 2026
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
2 participants
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.
Run the benchmark as the VC user and keep its result file in the VC-owned temp directory so ARM64 cleanup does not cross privilege boundaries. Report cancellation as a workload failure instead of a successful execution.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com
Copilot-Session: f3bc03fa-5da5-4a69-94e1-d6adc0cbe5db