Tests duplicated in Test Explorer

[oeed]

I'm still fairly new to Rust and Cargo workspace setups, so this is probably a setup issue on my end but I'm not too sure.

Essentially, the tests for all my projects are showing twice:

In the above example issue-worker is a binary and elasticsearch-wrapper a library. I've setup a workspace with this folder structure. I'll be adding additional libraries in the future and want them all grouped together, hence the lib folder.

Cargo.toml [workspace]
issue-worker
  | Cargo.toml [package]
  | src
  | issue-worker.code-workspace
lib
  | elasticsearch-wrapper
      | Cargo.toml [package]
      | src
...
+ other non-Rust folders & files

I have a multi-root VSCode workspace with the 'issue-worker' and 'lib' folders. The reason for this is this workspace is sitting in a mono-repo that also has other non-Rust projects; I only want to see the relevant Rust folders.

// issue-worker.code-workspace
{
  "folders": [{
      "path": "."
    },
    {
      "path": "../lib"
    }
  ]
}

[calebcartwright]

Can you share the contents of your workspace Cargo.toml file?

[oeed]

Sure

workspace:

[workspace]

members = [
  "issue-worker",
  "lib/elasticsearch-wrapper"
]

issue-worker:

[package]
name = "issue-worker"
version = "0.1.0"
authors = ["..."]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
elasticsearch-wrapper = { path = "../lib/elasticsearch-wrapper" }

elasticsearch-wrapper:

[package]
name = "elasticsearch-wrapper"
version = "0.1.0"
authors = ["..."]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
elasticsearch = "~7"
serde = "~1"
serde_json = "~1"

[calebcartwright]

Thanks! Everything looks pretty standard there with the explicit cargo workspace, so that plus the the duplicated rust root node in Explorer is highly indicative of the VS Code multiroot workspace doing some double loading somewhere.

Could you try opening a standalone instance of Code on the cargo workspace root directory?

[oeed]

Yep it appears to not duplicate with just the workspace directory open:

Directory:

Multi-root Workspace:

[raphaelricardo10]

I am studying this project to solve this problem. Someone can help me have a overview?

It think the problem is not that hard to solve.

[calebcartwright]

That'd be great @raphaelricardo10 thanks!

I don't know off hand what the issue is, but my guess is that the activation is being hit for every workspace:

vscode-rust-test-adapter/src/main.ts

Line 27 in b0b6b39

const workspaceFolder = (vscode.workspace.workspaceFolders || [])[0];

The project is obviously very, very light on contributing documentation but it does have the relevant VS Code configurations and npm scripts wired up (debug, testing, etc.) that you should be able to use the VS Code UI directly for such inner dev loop activities

[mlesin]

Is there any progress on this?

[raphaelricardo10]

Not yet. But there is a workaround: not using multiple VSCode workspaces, but a single workspace with cargo.toml file referring to different rust projects. In my case, I have a root project that consumes different rust libraries, and I added them as git submodules to edit them directly from the consumer.

For example:

[workspace]

members = [
    "submodules/project-1",
    "submodules/project-2",
    "submodules/project-n",
]