Fix Cody tests by hardcoding VS Code version #53224
Merged
Conversation
This file contains 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
github-actions
bot
added
the
team/code-exploration
|
Codenotify: Notifying subscribers in CODENOTIFY files for diff f4607dc...38b6e2d.
|
|
Codenotify: Notifying subscribers in OWNERS files for diff f4607dc...38b6e2d.
|
Closed
valerybugakov
approved these changes
Jun 9, 2023
ErikaRS
pushed a commit
that referenced
this pull request
Jun 22, 2023
As of the latest VS Code update, we see our extension test not working properly across both the integration and E2E setups. This seems to be an upstream problem and was also reported here: microsoft/vscode-test#221 This PR hardcodes these setups to use the previous version. ## Test plan - CI passes again <!-- All pull requests REQUIRE a test plan: https://docs.sourcegraph.com/dev/background-information/testing_principles -->
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.
As of the latest VS Code update, we see our extension test not working properly across both the integration and E2E setups. This seems to be an upstream problem and was also reported here: microsoft/vscode-test#221
This PR hardcodes these setups to use the previous version.
Test plan