FIX: Tasks on MacOS agents not completing but marked as succeeded. #5092
Conversation
This file contains 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
…ocesstreekillattempt arg
…o and isprocrunning check for all OS options
…ub.com/microsoft/azure-pipelines-agent into users/sahilbhatt/debug_monitor_tracing
tarunramsinghani
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Some pipelines using MacOS agents reported tasks not completing but still being marked as succeeded. Disabling resource utilization warnings seemed to mitigate this issue.
An analysis of various debug logs indicated that the problem was due to the resource utilization warnings' implementation in MacOS, where multiple CPU and memory info processes were being invoked simultaneously.
Changes made:
Validations done:
The issue did not reproduce on running a test pipeline on a self-hosted MacOS agent using the above-mentioned changes.
Note: This is the same as the closed PR: #5079. Re-opened as a new PR due to some issues during CI checks.