runtime-canary #14
Triggered via repository dispatch
July 14, 2026 09:38
MackinnonBuck
MackinnonBuck
runtime-canary
5adb51b
Status
Failure
Total duration
9m 19s
Artifacts
–
sdk-canary.yml
on: repository_dispatch
Resolve runtime inputs
2s
Matrix: test
Publish SDK canary (internal feed)
Annotations
18 errors and 1 notice
|
E2E tests (ubuntu-latest)
Process completed with exit code 1.
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should cancel pending MCP OAuth requests when the host declines:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L265
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should request host-owned replacement tokens across the MCP OAuth lifecycle:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should resolve pending MCP OAuth request with direct RPC:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L92
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should satisfy MCP OAuth using host-provided token:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
Unhandled error:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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.
|
|
E2E tests (macos-latest)
Process completed with exit code 1.
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should cancel pending MCP OAuth requests when the host declines:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L265
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should request host-owned replacement tokens across the MCP OAuth lifecycle:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should resolve pending MCP OAuth request with direct RPC:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L92
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should satisfy MCP OAuth using host-provided token:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
Unhandled error:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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.
|
|
E2E tests (windows-latest)
Process completed with exit code 1.
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should cancel pending MCP OAuth requests when the host declines:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L265
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should request host-owned replacement tokens across the MCP OAuth lifecycle:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should resolve pending MCP OAuth request with direct RPC:
nodejs/test/e2e/mcp_oauth.e2e.test.ts#L92
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
|
|
test/e2e/mcp_oauth.e2e.test.ts > MCP OAuth host auth > should satisfy MCP OAuth using host-provided token:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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
|
|
Unhandled error:
nodejs/test/e2e/harness/sdkTestHelper.ts#L145
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.
|
|
E2E tests (macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
|