Repository navigation
[rocprofiler-sdk] fix rejection of maximum valid stochastic sampling interval - #8431
Conversation
❌ PR Check — Action Required
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
|
🚫 Please fix the failed policies before requesting reviews. The following policy checks failed:
The |
|
Thanks for the PR: @samcrater-amd . Please check the comment I added into the Jira. |
1782c70 to
84a0d66
Compare
f30d46e to
0eb5f79
Compare
vlaindic
left a comment
There was a problem hiding this comment.
I'm seeing this in the testing plan: Ran profiler with intervals that were just below, at, and above the maximum supported interval value. but I'm not seeing any automation tests. Should we add them? We could do it as a separate PR (tracked in another JIRA/issue)
0eb5f79 to
627cbc7
Compare
…ed (#10247) ## Motivation [PR8431](#8431) had the unintended effect of also limiting the maximum number of microseconds users could specify when using PC sampling. ## Technical Details Gated clamp behind a check on interval type. ## JIRA ID JIRA ID : AIPROFSDK-913 ## Test Plan ran `rocprofv3-avail info --pc-sampling` to check valid intervals ## Test Result time-based interval was unbounded after fix ## Submission Checklist - [X] Look over the contributing guidelines at https://github.com/ROCm/rocm-systems/blob/develop/CONTRIBUTING.md.



Motivation
Some PCS interval values were not being accepted/rejected properly.
Technical Details
Ensured we were only reporting valid interval ranges, and added log telling user how to find valid ranges on a config failure.
JIRA ID
JIRA ID : AIPROFSDK-913.
Test Plan
Ran profiler with intervals that were just below, at, and above the maximum supported interval value.
Test Result
Profiler accepted maximum interval and rejected others.
Submission Checklist