Test Explorer icons don't update on Windows

[svanimpe]

See the screenshot below.

After running unit tests, the results appear in the Test Results pane, but the icons in the Test Explorer don't update. This did work for me on Linux, but not on Windows.

This is a template library project generated with swift package init.
I'm using v1.11.3 with Swift 6.0.1.

[plemarquand]

Thanks for the report @svanimpe. I'm having trouble reproducing the issue. Could you take a look at the attached screen recording and see if there are any differences in how you're reproducing it?

Also, could you paste in the output of swift -v, as well as whether you're using Windows 10 or 11.

Issue1149.mp4

[svanimpe]

Hi Paul,

I'm doing the exact same thing.

This is with swift-6.0.1-RELEASE on Windows 11.

[plemarquand]

Interesting. One more question then is what version of VS Code are you running?

[svanimpe]

That is 1.94.2

[plemarquand]

I managed to reproduce this using Swift 6.0.1.

The good news is this doesn't reproduce with the 6.1 (trunk development, main) snapshot from Sept 24th. It also doesn't reproduce if you add swift-testing's main branch as a dependency in your Package.swift.

From my investigation on the swift-vscode side, swift-testing version shipped in Swift Windows 6.0.1 is not writing to the JSON event stream. I've reached out to the swift-testing team for more info.

[plemarquand]

OK a bit more information from the swift-testing team. Looks like this Windows regression was fixed by swiftlang/swift#76564 in the 6.0.2 branch (the PR title states 6.0.1, but this is incorrect, it was merged to 6.0.2).

A couple of options to fix this are:

• Wait for the Swift 6.0.2 release
• Use the Swift 6.1 trunk development snapshot
• Declare swift-testing as a dependency in your Package.swift

I'm going to close this as there isn't much vscode-swift can do here. Please feel free to reopen if you are still experiencing this issue with newer Swift toolchains.

[plemarquand]

Actually, I'll keep this open and verify once 6.0.2 is released.

[svanimpe]

OK. I'll just wait for 6.0.2, as this wasn't the only issue I encountered with 6.0.1.

[plemarquand]

@svanimpe 6.0.2 was just released, let me know if you're still seeing the issue: https://www.swift.org/download/

[svanimpe]

I no longer have this issue with 6.0.2