fix: Handle failure to read thread priority gracefully #2015
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
Handle this failure gracefully and only log a thread priority if reading it was successful.
💡 Motivation and Context
Reading the thread priority can return
-1in failure cases and we don't want to store this in the profile payload if we're not able to read a legitimate value. This also fixes a flake with thetestStartTransaction_ProfilingDataIsValidtest which checked for a valid priority and failed about 20% of the time on macOS.💚 How did you test it?
Verify that
testStartTransaction_ProfilingDataIsValidno longer flakes on macOS.📝 Checklist
🔮 Next steps