Can't debug multiple test files in VS Code using deno test

[jaredkrinke]

On 1.17, when I debug deno test --inspect-brk in VS Code, I'm only able to hit breakpoints in the first test file it runs. E.g. if I have two test files and set breakpoints in both, I only hit breakpoints in the first file.

If I always explicitly specify the test file as an argument, then I'm able to debug my test successfully.

Here's a repository with a minimal setup to reproduce (including launch.json file):
https://github.com/jaredkrinke/repro-deno-debug-two-files

Deno version:

deno 1.17.0 (release, x86_64-pc-windows-msvc)
v8 9.7.106.15
typescript 4.5.2

Steps to reproduce

1. Open in VS Code
2. Put breakpoints on the console.log lines in both one.test.ts and two.test.ts
3. Fit F5 to start debugging with the provided launch.json
4. Hit the first breakpoint
5. Hit F5 to continue to the next breakpoint

Expected

The next breakpoint should be hit.

Actual

Debug session ends.

Note: I always hit the same breakpoint, and it's in the file that comes first alphabetically, so I suspect Deno is enumerating the files and running them sequentially in separate contexts, but for whatever reason, I can only debug the first context.

Workaround

To debug a particular test, just add that test's file name to the arguments in launch.json.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[jaredkrinke]

FYI: This still happens on Deno 1.19.0.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[jaredkrinke]

Just to avoid this bug getting closed automatically because it's stale, I'll note that this still happens on Deno 1.21.0.

[bartlomieju]

FYI I'm investigated this issue and had a talk with @cjihrig to discuss how Node.js handles this; additionally I'll talk with VSCode team to discuss how to improve this behavior. Will act on this soon.

[jespertheend]

I'm running into some wonky behaviour too, I think it might be the same issue. Though in my case the process just exits without even reporting any test results. Not sure why I'm only running into this now because I'm pretty sure I've used breakpoints in multiple files before.

[raigorx]

No being able to debug in a developer environment is catastrophic I have the same issue deno 1.35.1