-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Enable bootstrapped builds in VS test insertion YAML #69130
Conversation
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.
Talked with Julien offline about this, and I think I'm going to need a complete explanation of why this needs to be in a separate PR that will slow down all roslyn CI for several days.
Sounds like we'll have to wait til @jaredpar is back, as I'm not able to provide sufficient details. |
How will this slow down roslyn CI? This is the PR official pipeline file. To my understanding that is only used in the following pipeline which is run "on demand" only. https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_build?definitionId=8972&_a=summary |
The file is named |
I also am still unsure why this needs to be checked in. Why does the compiler itself need to be built with the flag? |
We want a speedometer result of VS using roslyn bits using the new codegen. |
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.
We want a speedometer result of VS using roslyn bits using the new codegen.
Bootstrapping is what will cause the roslyn bits to use the new codegen. Without bootstrapping, the roslyn bits would still use the old async codegen.
Thanks. This, and that the file was not standard ci, were the pieces that I was missing.
@jaredpar for review. Thanks |
I agree the name is confusing and I wish there we had a better one. I'm fine with renaming if @dibarbet agrees. |
I'm fine with renaming, but the pipeline is specifically for validating PRs (against VS). Maybe something like |
I'm not planning to rename in this PR (not the intent, I'm just trying to unblock validation of a codegen change), that can be a follow-up. |
Yeah I don't want to change the name here. Just saying it's fine for another PR. |
In order to get speedometer results on an experimental compiler codegen change, we need to temporarily enable bootstrapping.