`Run w/ Coverage` is broken

[MahdiBM]

Describe the bug

The extension expects .build/debug/codecov/default.profdata, but only produces .build/debug/codecov/*.profraw files when you use Run w/ Coverage.

This error is thrown right after each Run w/ Coverage:

Error: ENOENT: no such file or directory, open '.../swift-endpoint/.build/debug/codecov/default.profdata'

I worked around it like so:

while true; do 
  profraw=$(ls .../swift-endpoint/.build/debug/codecov/*.profraw 2>/dev/null | head -n1) 
  if [[ -n "$profraw" ]]; then
    ln -sf "$profraw" .../swift-endpoint/.build/debug/codecov/default.profdata 
  fi 
done

Creates a symlink from the produced *.profraw file to the default.profdata file as soon as the *.profraw is created.
Then when the extension looks for the default.profdata it does actually find it.

With this, things seem to be back to normal, which means it's just the extension looking for the wrong file.

To Reproduce
Use Run w/ Coverage.

Expected behavior
A clear and concise description of what you expected to happen.

Environment

• OS: macOS 26.1
• Swift version: 6.2.1
• Visual Studio Code version:
• vscode-swift version: 2.14.0

Diagnostics Bundle
The diagnostics bundle can help determine the root cause of bugs much quicker. To share this information execute the >Swift: Capture Diagnostics Bundle command and attach the archive to the bug report.

Select the "Minimal" bundle to only share the Swift extension's log and your configured swift. settings. Select the "Full" bundle if you're comfortable sharing the SourceKit-LSP diagnostic bundle and LLDB-DAP logs, which may contain source code

Additional context
Add any other context about the problem here.

[plemarquand]

I'm having trouble reproducing this with 6.2.1. My simple test case produces both the .profraw and .prodata files as expected, and coverage data shows up.

If you take a look at the Terminal tab after doing "Run w/ Coverage", what is the command there? Do you see the --enable-code-coverage flag? Were there any build errors during compilation?

[MahdiBM]

Well I can't reproduce it anymore either. Though I haven't updated anything after that, so not sure why it was happening before but not right now.

[MahdiBM]

I assume the codecov flag was there otherwise why would it produce profraw files? Does it create those files regardless of the codecov flag?

[plemarquand]

Those files will stick around across builds but could become stale if they were produced against old code and not produced later when they should be, so I wanted to double check.