getDebugConfiguration doesn't handle runner override

[diorcety]

On VSCode, when running a test using lens snipper, the test is run using cargo test.
The debug use "cargo test --message-format=json --no-run ..." in order to get executable information in order to construct debugger args.

If in .cargo/config.toml the runner is overridden the run is working well unlike the debug.
Indeed "cargo test --message-format=json --no-run ..." doesn't give any information about the runner.

A way to have the runner is to parse the line containing Executable on stderr when using "cargo test -v --no-run"

[Veykril]

If in .cargo/config.toml the runner is overridden the run is working well unlike the debug.

What is the runner here? Can you give an example config.toml?

[diorcety]

Sure:

An example using embedded-test on x86:

[target."x86_64-unknown-linux-gnu"]
runner = "embedded-test-std-runner"

[Veykril]

Ah okay, so I assume the extension might be running things in a different directory which makes cargo not pick up the related config

[diorcety]

No because if I run the test the runner is used (with cargo test called by the extension). But in the case of debug cargo test is only used to get infomation, in which, the runner information is missing.