-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Settings Editor is not launching in PGO tests #16960
Comments
Unpackaged build fresh off of #16954 (the first PR I clicked on with a finished CI run), on a win10 vm. So, it's not that. |
notes
abridged:
etc
|
The PGO builds trail the nightlies by one night - so the bad data would have been produced one or more nights previously in the instrumentation pipeline |
The last PGO build that successfully instrumented TSE was 0.0.2403.2501. The first one that failed was 0.0.2403.2601; evidenced by this message:
|
All new in -26.
|
Test instrumentation builds:
I wasn't the murderer, hooray |
This was fixed by #16993 |
The nightly canary build failed to PGO TerminalSettingsEditor due to no counts, which suggests that it didn't get exercised in last night's PGO run. That further hints that it may not have opened.
The PGO agents run Windows 10, I think? And they launch in unpackaged mode. May be a good place to start the investigation!
The text was updated successfully, but these errors were encountered: