-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XCTest output is not recorded when using CodeLLDB #1100
Labels
bug
Something isn't working
Comments
plemarquand
added a commit
to plemarquand/vscode-swift
that referenced
this issue
Sep 26, 2024
The CodeLLDB extension expects the debug adapter to be called `lldb`. If we are using it and we don't call `registerDebugAdapterTrackerFactory` with `lldb` as the adapter name then we fail to get logs in the debugSessionCallback when running tests. This prevents XCTests results from being parsed, and hides the swift-testing outout. Revert a portion of swiftlang#1024 that always set the debug adapter name to `swift-lldb` and use `lldb` when we're using CodeLLDB as the debug adapter. Issue swiftlang#1100
plemarquand
added a commit
that referenced
this issue
Sep 26, 2024
The CodeLLDB extension expects the debug adapter to be called `lldb`. If we are using it and we don't call `registerDebugAdapterTrackerFactory` with `lldb` as the adapter name then we fail to get logs in the debugSessionCallback when running tests. This prevents XCTests results from being parsed, and hides the swift-testing outout. Revert a portion of #1024 that always set the debug adapter name to `swift-lldb` and use `lldb` when we're using CodeLLDB as the debug adapter. Issue #1100
I will verify this one. |
Verified with and without the patch, the bug is fixed with the patch applied. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using CodeLLDB as the debug adapter XCTest output is not captured and so test results are not recorded. If
swift.debugger.useDebugAdapterFromToolchain
is true then output is captured and tests work as expected.To Reproduce
Create a simple XCTest:
testFoo()
's test icon, Debug TestEnvironment
The text was updated successfully, but these errors were encountered: