Skip to content

Accept "Command produced no output" when shell integration is off#303866

Merged
alexdima merged 1 commit intomainfrom
alexd/redundant-sturgeon
Mar 22, 2026
Merged

Accept "Command produced no output" when shell integration is off#303866
alexdima merged 1 commit intomainfrom
alexd/redundant-sturgeon

Conversation

@alexdima
Copy link
Copy Markdown
Member

Fixes #303865

@alexdima alexdima enabled auto-merge (squash) March 22, 2026 14:19
Copilot AI review requested due to automatic review settings March 22, 2026 14:19
@alexdima alexdima self-assigned this Mar 22, 2026
@vs-code-engineering vs-code-engineering bot added this to the 1.113.0 milestone Mar 22, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the run_in_terminal API integration tests to tolerate the known fallback output "Command produced no output" when terminal shell integration is disabled, addressing a Windows CI flake reported in #303865.

Changes:

  • Loosens the multi-line output assertion for the “shell integration off” test path to accept the "Command produced no output" fallback.
  • Adds a targeted assertion message to help diagnose unexpected outputs when the test fails.

@alexdima alexdima merged commit ca117fb into main Mar 22, 2026
23 checks passed
@alexdima alexdima deleted the alexd/redundant-sturgeon branch March 22, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chat - run_in_terminal - windows - integration test failure

3 participants