microsoft / microsoft/vscode-cmake-tools

Debug Test is massively slow - 40 secs waiting for promp & it always ask for a Debug Launch Configuration

Open
#3,428 2 comments 3 reactions 0 assignees View on GitHub
Feature: debug/launch
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

- Click on the Debug Test & Select my unit test.
- Starts build the test, even with "cmake.buildBeforeRun": false"?

- Takes ~30-40 secs to show the promp to select a Debug configuration.

It's not a Hello-world or simple project, but a production & enterprise one.
So:
- How could I speed this up?
- How can I avoid to select each time the same debug configuration from a list? Is not possible to let the Debug Test to choose the already selected option? This is really annoying.

Thanks.

### CMake Tools Diagnostics

```shell
Snippet with censored info (NDA/private company data)

[build] Generating changeset header for repo /home/mf/repos/PROJECT/
[build] [111/131] Automatic MOC for target whatever
[build] [112/129] Automatic MOC for target whatever
[build] [113/127] Automatic MOC for target whatever
[build] [114/125] Automatic MOC for target whatever
[build] [115/123] Automatic MOC for target whatever
[build] [116/121] Automatic MOC for target whatever
[build] [117/119] Automatic MOC for target whatever
[driver] Build completed: 00:00:03.953

After this, it shows [cmakefileapi-parser] Read reply folder: /home/borjamf/repos/asdasd/build/asdasd/Debug/.cmake/api/v1/reply
[cmakefileapi-parser] Found index files:

[build] Build finished with exit code 0
[cache] Reading CMake cache file /home/borjamf/repos/whatever/build/asdasd/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file /home/borjamf/repos/acds_shell3/build/rasdasd/Debug/CMakeCache.txt
[cache] Parsing CMake cache string
```

### Debug Log

_No response_

### Additional Information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start from the Debug Test flow and the CMake Tools diagnostics around build completion, CMake file API parsing, and repeated CMakeCache.txt reads. Reproduce the long delay and repeated Debug Launch Configuration prompt, then verify that test debugging starts promptly and reuses the selected configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, vscode
Domain
devtools, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.