Not a supported test executable (Catch2 on remote ssh)

Checklist

• The issue is about this extension and NOT about a fork.
• Check the known issues list.
• The latest version of the extension was used.

Describe the bug I have a simple Catch2 test suite that runs fine from command line and vscode tasks. However its test cases don’t get listed in Test Explorer. Here is a sample run of it with “-l”:

{workspace-root} $ build/Tests -l
All available test cases:
  Load library and register callbacks
      [init]
1 test case

Desktop

• Extension Version: latest
• VS Code Version: latest
• Catch2 / Google Test / DOCTest Version: Catch2 v2.12.1
• OS Type and Version: Ubuntu 18 LTS
• Using remote-ssh/docker/wsl?: Yes, remote-ssh

Log (optional but recommended)

[2020-05-15 12:48:20.146] [DEBUG] Not a test executable: /home/$USER/{workspace-root}/build/Tests reason: [Error: Not a supported test executable: /home/$USER/{workspace-root}/build/Tests
 output: 
        at /home/$USER/.vscode-server/extensions/matepek.vscode-catch2-test-adapter-3.2.0/out/dist/main.js:23:34044
        at async e.ExecutableConfig.load (/home/$USER/.vscode-server/extensions/matepek.vscode-catch2-test-adapter-3.2.0/out/dist/main.js:23:27220)
        at async Promise.all (index 0)
        at async o.load (/home/$USER/.vscode-server/extensions/matepek.vscode-catch2-test-adapter-3.2.0/out/dist/main.js:22:29374)]
[2020-05-15 12:48:20.146] [INFO] load finished 0

[matepek]

Assuming that “this” means this issue(201): yes, this can cause symptoms like that.

[gatopeich]

Okay I found the issue: there was a dynamic linked library with a relative path. It could only run from the workspace root dir.