-
Notifications
You must be signed in to change notification settings - Fork 431
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
CTest tests don't run in parallel from the testing pane #3322
Comments
@snehara99 Was this resolved by #3271 ? |
No, we allowed the parallel tests from the status bar and the Project Status View, but not from the Test Explorer yet. We decided to approach that separately as a feature. |
Commenting on this issue since the referenced issues are closed. Where is the option "Run CTest" in the status bar? Recently items have moved to the CMake pane on the left, and I don't see this option either in the CMake pane or in the status bar. EDIT: replying to my own comment, maybe this is useful for others too. It's very subtle. In the CMake pane you need to hover over the "Test" node. This shows up a small flask icon that you need to click. Clicking this icon will run tests in parallel. See the screen shot below. |
@geertj thanks for the hint! However in my case the tests, even when launched with your method, are not run in parallel. Have you got the same pb with latest vscode version (vscode version: 1.86.0, cmake tools version: v1.16.32)? |
@geertj i finally succeed in but i had to upgrade to the pre-release version of cmake tools and then add explicitly the number of jobs in the |
@gcampbell-msft should not this issue be closed since #3577 has been merged? |
@gcampbell-msft i think the label |
@hippo91 Thank you very much for your reply! This label: fixed (release pending) has been added by gcampbell. |
As originally reported in #3091, CTest aren't running in parallels when started from the testing pane, using the button "Run tests" with the double-play-like icon.
In #3091 this was fixed if run by pressing "Run CTest" in the status bar, and possibly through other paths, but specifically not through the testing pane. As instructed by @snehara99 I'm opening a new issue to address this specific use case.
The text was updated successfully, but these errors were encountered: