test: disable built-in AI features in integration tests - #1937
Draft
wenyt (wenytang-ms) wants to merge 2 commits into
Draft
wenyt (wenytang-ms) wants to merge 2 commits into
wenyt (wenytang-ms) wants to merge 2 commits into
Conversation
wenyt (wenytang-ms)
changed the title
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
1 participant
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.
Summary
chat.disableAIFeaturesbefore VS Code starts so the core AgentHost remains disabledContext
The Linux, Windows, and macOS jobs in #1936 start VS Code 1.138.0 but never reach the extension test runner before the 30-minute timeout. Disabling the built-in extensions alone does not stop AgentHost because AgentHost is now a core VS Code process. VS Code 1.138 gates AgentHost through
chat.disableAIFeatures, so this draft PR supplies that setting through the isolated test profile.