Skip to content
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

Revert "Push the two-step navigation system further through roslyn." #59949

Closed
wants to merge 1 commit into from

Conversation

RikkiGibson
Copy link
Contributor

@RikkiGibson RikkiGibson commented Mar 4, 2022

#59802 is suspected of introducing RPS regressions.

Last known good: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/383846
First known bad: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/383867
Revert validation: https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build/results?buildId=5837378&view=results

Regressed counters:

  • UWP64.BuildAndDebug - RegressedBeyondThreshold / 0400.Close Solution / CLR_AdjustedMethodsJitted_Total_devenv / Regressed: 731.80 Count (6.14%)

Please advise whether the failures are plausibly connected with this PR, and if so, whether we should revert, or take a follow-up PR to fix, or seek an exception. @genlu @CyrusNajmabadi @jasonmalinowski.

@jasonmalinowski
Copy link
Member

Closing this; at this point the Roslyn PR appears to be a red herring -- either another component broke their ngen, or ngen randomly failed, and that's causing the increase in JIT and change in assembly load.

@jasonmalinowski jasonmalinowski deleted the revert-59802-asyncNavigation4 branch March 4, 2022 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants