-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add pgo testing to outerloop #53301
Add pgo testing to outerloop #53301
Conversation
Also update jit-experimental to no longer run PGO or EH WriteThru.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
cc @dotnet/jit-contrib |
Ignore |
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.
I think you should rename the pipelines "runtime-coreclr pgo" and "runtime-coreclr libraries-pgo"
|
||
schedules: | ||
- cron: "0 16 * * 0,6" | ||
displayName: Sun at 8:00 AM (UTC-8:00) |
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.
nit: looks like the 'cron' is Sat and Sun
|
||
schedules: | ||
- cron: "0 0 * * *" | ||
displayName: Mon through Sun at 12:00 AM (UTC-8:00) |
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.
cron "0 0" is midnight UTC, so 4pm PDT?
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.
Will update these.
Libraries failures are unrelated. Linux debug x64 libraries test failure is in post-test reporting.
the other two legs fail this test (seems like a novel failure)
|
71 test failures in libraries tests, 10 in jit tests. |
Scanned through the various failing tests and they're all getting the expected complus settings. |
Not entirely sure why the pgo jobs got retriggered on push .... anybody know? |
Seems unexpected. |
I guess what I'm wondering is if these new pipelines are somehow attached to PRs/Innerloop -- how can I check that? |
My reading of the YAML is that shouldn't happen: it has "trigger: none" and no "pr:" entry. You can go to the AzDO pipeline settings page for your branch: but it just tells you the same thing. Maybe after it gets merged to main the behavior will be different? i.e., AzDO glitch? |
Thanks for double-checking. I'll submit a trial PR after I merge this just to make sure. |
FYI those retriggered runs all failed with
|
Remaining legs unrelated, so I'm going to merge this. |
I think this change might be causing all PRs to fail. I haven't seen a single pass of this build definition and it's running on all PRs: https://dev.azure.com/dnceng/public/_build?definitionId=1002&_a=summary |
Hopefully fixed now, I adjusted the trigger logic. |
Also update jit-experimental to no longer run PGO or EH WriteThru.