Skip to content
This repository was archived by the owner on Jul 15, 2023. It is now read-only.

Send test output to a distinct output channel#499

Merged
lukehoban merged 1 commit intomicrosoft:masterfrom
ironcladlou:pr/test-output-channel
Sep 25, 2016
Merged

Send test output to a distinct output channel#499
lukehoban merged 1 commit intomicrosoft:masterfrom
ironcladlou:pr/test-output-channel

Conversation

@ironcladlou
Copy link
Copy Markdown
Contributor

Send Go test output to a dedicated output channel. Re-using the "Go"
channel from the status component causes a lot of confusing
interspersed unrelated output, and the test command often clears the
"Go" channel, obliterating things users might want to see.

Send Go test output to a dedicated output channel. Re-using the "Go"
channel from the status component causes a lot of confusing
interspersed unrelated output, and the test command often clears the
"Go" channel, obliterating things users might want to see.
@ramya-rao-a
Copy link
Copy Markdown
Contributor

@ironcladlou Just a heads up, travis builds most likely will fail due to microsoft/vscode-debugadapter-node#65

@lukehoban
Copy link
Copy Markdown
Member

Looks good.

@lukehoban lukehoban closed this Sep 25, 2016
@lukehoban lukehoban reopened this Sep 25, 2016
@lukehoban lukehoban merged commit 0e5a97f into microsoft:master Sep 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants