-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix the srcBufferLength check #68270
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsShould only get the buffer if it is > 0. Fix failures in superpmi replay.
|
@dotnet/jit-contrib @BruceForstall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
You could trigger the replay job to be sure this fixes (all) the issues.
/azp run runtime-coreclr superpmi-replay |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
I think we should include |
Agreed. Although it's a little uncommon to change superpmi without also changing the JIT/EE GUID.
Seems like this should work (that is, manually triggering the pipeline). Maybe there's some configuration thing we could fix. |
Yes, already triggered it in https://dev.azure.com/dnceng/public/_build/results?buildId=1728724&view=results |
superpmi-replay is clean. |
* fix the srcBufferLength check * trigger superpmi replay job when changes to superpmi tool
Should only get the buffer if it is > 0.
Fix failures in superpmi replay.