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 |
BruceForstall
left a comment
There was a problem hiding this comment.
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.