From 2bcd6c467e6700b9876e07bcd7baf33115bf73e5 Mon Sep 17 00:00:00 2001
From: Daniel Imms <2193314+Tyriar@users.noreply.github.com>
Date: Wed, 8 Jan 2025 09:16:51 -0800
Subject: [PATCH] Retry executeCommand integration test on failure

It's unclear how this happened and seems like a very rare flake.
---
 .../singlefolder-tests/terminal.shellIntegration.test.ts   | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts b/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts
index 521a41ea865..db48c2593e0 100644
--- a/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts
+++ b/extensions/vscode-api-tests/src/singlefolder-tests/terminal.shellIntegration.test.ts
@@ -212,7 +212,12 @@ import { assertNoRpc } from '../utils';
 		await closeTerminalAsync(terminal);
 	});
 
-	test('executeCommand(executable, args)', async () => {
+	test('executeCommand(executable, args)', async function () {
+		// HACK: This test has flaked before where the `value` was `e`, not `echo hello`. After an
+		// investigation it's not clear how this happened, so in order to keep some of the value
+		// that the test adds, it will retry after a failure.
+		this.retries(3);
+
 		const { terminal, shellIntegration } = await createTerminalAndWaitForShellIntegration();
 		const { execution, endEvent } = executeCommandAsync(shellIntegration, 'echo', ['hello']);
 		const executionSync = await execution;