Test Explorer does not correctly map output of failing tests

rust-analyzer version: rust-analyzer version: 0.3.2735-standalone (be6975f8f9 2025-12-28) [.vscode\extensions\rust-lang.rust-analyzer-0.3.2735-win32-x64\server\rust-analyzer.exe]

rustc version: rustc 1.92.0 (ded5c06cf 2025-12-08)

editor or extension:

VSCode

Version: 1.107.1 (user setup)
Commit: 994fd12f8d3a5aa16f17d42c041e5809167e845a
Date: 2025-12-17T14:15:14.850Z (1 wk ago)
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

rust-lang.rust-analyzer (extension)
Version: 0.3.2735

relevant settings: N/A

repository link (if public, optional):example repository

code snippet to reproduce:
(see repository above)

Description: When running tests through the test explorer, failing tests are missing their corresponding output.

The output of the specific test is completely empty/blank (furthermore, the path to the test seems to contain placeholders, like ${symbol-module} and ${package} which have not been replaced):

However, the full output does contain the assertions' error message:

Start with the linked example repository and reproduce the failure through VSCode's Test Explorer, then trace how rust-analyzer maps failing-test output to the selected test. Done means the specific test shows its assertion output and its path no longer contains unresolved placeholders such as ${symbol-module} or ${package}.