Repository navigation
Keep compiler rollouts out of the deployment smoke test - #817
Open
thomashoneyman wants to merge 2 commits into
Open
thomashoneyman wants to merge 2 commits into
thomashoneyman wants to merge 2 commits into
Conversation
thomashoneyman
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The VM smoke test was passing with background job failures; its
preludefixture only listed the older test compiler, so starting the server triggered a registry-wide compiler rollout. Those jobs then tried to download packages from an HTTP mock that the deployment smoke test does not run, but it didn't fail. Cleaned it up so we don't run the rollout.