test: increase timeouts to reduce flakiness on Windows CI (cloudflare…

…#3504)

.vscode/settings.json

@@ -31,6 +31,7 @@
 		"selfsigned",
 		"textfile",
 		"tsbuildinfo",
+		"turborepo",
 		"undici",
 		"unrevoke",
 		"Untriaged",

packages/wrangler/package.json

@@ -83,7 +83,7 @@
 			"<rootDir>/src/__tests__/jest.setup.ts"
 		],
 		"testRegex": "src/__tests__/.*\\.(test|spec)\\.[jt]sx?$",
-		"testTimeout": 30000,
+		"testTimeout": 50000,
 		"transform": {
 			"^.+\\.c?(t|j)sx?$": [
 				"esbuild-jest",

vitest.config.ts

@@ -3,9 +3,16 @@ import { defineConfig } from "vitest/config";
 // This default gets pulled in by all the Vitest runs in the monorepo.
 export default defineConfig({
 	test: {
-		testTimeout: 30_000,
-		hookTimeout: 30_000,
-		teardownTimeout: 30_000,
+		// These timeouts are very large because the Windows CI jobs regularly take up ot 42 secs.
+		// Ideally we should not have such high defaults across all tests, but instead be able to
+		// increase timeouts for certain sets of tests.
+		// But this might need some vitest/turborepo magical incantations and bumping the values
+		// here is a simpler short term fix.
+		// Note that this will not cause tests to pass that should fail. It just means that hanging
+		// tests will take longer to fail than they would before.
+		testTimeout: 50_000,
+		hookTimeout: 50_000,
+		teardownTimeout: 50_000,
 		useAtomics: true,
 	},
 });