Process completed with exit code 1.

AssertionError: expected undefined to match object { …(2) } - Expected: { "reason": "initial", "serverName": "oauth-cancelled-mcp", } + Received: undefined ❯ test/e2e/mcp_oauth.e2e.test.ts:265:33

Error: oauth-lifecycle-mcp did not reach connected; last status was <not listed> ❯ waitForCondition test/e2e/harness/sdkTestHelper.ts:145:11 ❯ waitForMcpServerStatus test/e2e/mcp_oauth.e2e.test.ts:279:5 ❯ test/e2e/mcp_oauth.e2e.test.ts:200:13

Error: Test timed out in 120000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/e2e/mcp_oauth.e2e.test.ts:92:5

Error: oauth-protected-mcp did not reach connected; last status was <not listed> ❯ waitForCondition test/e2e/harness/sdkTestHelper.ts:145:11 ❯ waitForMcpServerStatus test/e2e/mcp_oauth.e2e.test.ts:279:5 ❯ test/e2e/mcp_oauth.e2e.test.ts:62:9

Error: oauth-direct-rpc-mcp did not reach connected; last status was <not listed> ❯ waitForCondition test/e2e/harness/sdkTestHelper.ts:145:11 ❯ waitForMcpServerStatus test/e2e/mcp_oauth.e2e.test.ts:279:5 This error originated in "test/e2e/mcp_oauth.e2e.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should resolve pending MCP OAuth request with direct RPC". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.