JIT: fix interaction of PGO and jitstress#47876
Merged
AndyAyersMS merged 1 commit intodotnet:masterfrom Feb 5, 2021
Merged
Conversation
We always need to run the profile data phase so that jit stress can inject random profile counts if it so chooses. Also, clean up a few dumping nits -- don't dump the profile query status until we get around to trying to incorporate counts; summarize schema records before asserting that we must have block counts, etc. Closes dotnet#47839
Member
Author
|
cc @dotnet/jit-contrib Will kick off CI stress runs shortly (pri0 jitstress1 passes locally) |
BruceForstall
approved these changes
Feb 4, 2021
Member
Author
|
/azp run runtime-coreclr jitstress |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
Author
|
Two OOMs in x86 jitstress test, seem unrelated (#10002 ?). Will ignore. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
We always need to run the profile data phase so that jit stress can inject
random profile counts if it so chooses.
Also, clean up a few dumping nits -- don't dump the profile query status until
we get around to trying to incorporate counts; summarize schema records before
asserting that we must have block counts, etc.
Closes #47839