-
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
Nightly Test: Test Explorer Suite - Debugs specified XCTest test failed on Test Insiders / Linux (6.0 - jammy) #1317
Comments
Another failure in: https://github.com/swiftlang/vscode-swift/actions/runs/12858610127/job/35847958476 (Linux nightly main jammy) Test logs
|
Strangely, when I all the integration tests together, the test gets stuck after the swift build stage (when run in Dev Containers for 5.10, since many jobs are now failing consistently on 5.10 as well (for example: https://github.com/swiftlang/vscode-swift/actions/runs/12890321891/job/35942486703?pr=1285)).
However, when I run just that test, it seems to have no problem passing. It does seem like the CodeLLDB extension was update recently (vadimcn/codelldb@v1.11.2...master) so perhaps that could be the cause of flakiness since not much should have changed with Swift 5.10 recently. Will try to post a PR to move this test to the nightly runs so we can keep an eye on it and not generate false positives for other submissions. |
This test case seems to get stuck frequently on swift 5.10 now. Move it to nightly for now so that we can avoid creating false positives. Issue: swiftlang#1317
This test case seems to get stuck frequently on swift 5.10 now. Move it to nightly for now so that we can avoid creating false positives. Issue: #1317
It seems like setting the
or on Linux may fail with something like:
Until the extension and/or its dependencies are fixed, it looks like the following temporary workaround options are possible:
|
Test failed with:
Link to failed run: https://github.com/swiftlang/vscode-swift/actions/runs/12778956212/job/35622742552
The text was updated successfully, but these errors were encountered: