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

Set [Skip-SymbolCheck] suffix in insertion tool #54580

Merged

Conversation

RikkiGibson
Copy link
Contributor

@RikkiGibson RikkiGibson commented Jul 2, 2021

Depends on dotnet/roslyn-tools#1029

Symbol checks are too slow for us to be able to insert as quickly as we'd like. Currently we artificially slow down the insertion by making the insert stage depend on the publish_using_darc stage. This change makes it so we just always skip the symbol check in insertions, which we've judged to be low-risk, and make the insert stage depend only on the build stage. This change makes our insertions show up ~30 minutes faster.

@RikkiGibson RikkiGibson marked this pull request as ready for review July 3, 2021 19:23
@RikkiGibson RikkiGibson requested a review from a team as a code owner July 3, 2021 19:23
@dibarbet
Copy link
Member

dibarbet commented Jul 6, 2021

This change makes it so we just always skip the symbol check in insertions, which we've judged to be low-risk, and make the insert stage depend only on the build stage.

Is there a check at a later point (that also gives us time to fix the issue) telling us if we have a problem with symbols we've previously uploaded?

@RikkiGibson
Copy link
Contributor Author

Is there a check at a later point (that also gives us time to fix the issue) telling us if we have a problem with symbols we've previously uploaded?

Everyone after us who doesn't skip symbol checks will get a check failure in their PRs, which will get blamed on us, I think.

It's also worth noting that symbol publishing can happen at any time, even after the product ships. As long as we retain the symbols for our official builds (e.g. by publishing them as an artifact, as I think we currently do) we can always go back, grab the symbols and publish them.

@dibarbet
Copy link
Member

dibarbet commented Jul 6, 2021

Everyone after us who doesn't skip symbol checks will get a check failure in their PRs, which will get blamed on us, I think.

Good to know

It's also worth noting that symbol publishing can happen at any time, even after the product ships. As long as we retain the symbols for our official builds (e.g. by publishing them as an artifact, as I think we currently do) we can always go back, grab the symbols and publish them.

Yep, was mainly concerned if we broke our symbols somehow and so the symbols we uploaded were incorrect and then didn't realize. But I'm not sure if symbol check does that deep of a validation

@RikkiGibson RikkiGibson merged commit 7103a61 into dotnet:release/dev16.11 Jul 9, 2021
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.

3 participants