PATH env is incorrect for "Run Test" on mac osx

[zhiqiangxu]

rust-analyzer version: v0.3.2319.

When I click "Run Test", I got the error below:

But if I run the same command in the terminal, it works:

Here is where the cargo binary is located:

% which cargo
/Users/alan.xu/.cargo/bin/cargo

So I think the PATH env is incorrect for "Run Test".
(btw, I'm using zsh, and the PATH is set in ~/.zshrc)

[ChayimFriedman2]

Are you sure "Run Test" also executes the command in zsh?

[zhiqiangxu]

Are you sure "Run Test" also executes the command in zsh?

I'm not sure whether "Run Test" is executing it in zsh, zsh is my default shell, so "Run Test" should automatically choose zsh, right?

UPDATE

Is there a way to figure out which shell "Run Test" is running in?

[Veykril]

It's running in the environment that your VSCode is running in

[zhiqiangxu]

It's running in the environment that your VSCode is running in

Is it possible to make it always using the same shell the vscode terminal is using ? As the command is running fine in the terminal but not in "Run Test".

[Veykril]

I am not sure we can do that, maybe we can construct a shell execution here that inherits the vscode terminal shell

rust-analyzer/editors/code/src/tasks.ts

Lines 117 to 135 in 62e7e2b

	export async function targetToExecution(
	definition: TaskDefinition,
	options?: {
	env?: { [key: string]: string };
	cwd?: string;
	},
	cargo?: string,
	): Promise<vscode.ProcessExecution | vscode.ShellExecution> {
	let command, args;
	if (isCargoTask(definition)) {
	// FIXME: The server should provide cargo
	command = cargo || (await toolchain.cargoPath(options?.env));
	args = [definition.command].concat(definition.args || []);
	} else {
	command = definition.command;
	args = definition.args || [];
	}
	return new vscode.ProcessExecution(command, args, options);
	}

?

[zhiqiangxu]

@Veykril I'm still having this issue :

It can't find cargo for "Run Test" or "Debug", but it works in the terminal:

[Veykril]

Well yes, the issue hasn't been closed yet as you can see.

[zhiqiangxu]

Well yes, the issue hasn't been closed yet as you can see.

I once worked around this issue with this tip, but it's not working for another macbook, it's really weird.