runtime-canary #40
Triggered via repository dispatch
August 13, 2026 09:13
MackinnonBuck
MackinnonBuck
runtime-canary
811adc0
Status
Failure
Total duration
8m 44s
Artifacts
–
sdk-canary.yml
on: repository_dispatch
Resolve runtime inputs
3s
Matrix: test
Publish SDK canary (internal feed)
31s
Annotations
30 errors and 1 warning
|
test/e2e/tools.e2e.test.ts > Custom tools > clears context from a terminal tool and starts the seeded turn:
nodejs/test/e2e/tools.e2e.test.ts#L48
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/e2e/tools.e2e.test.ts:48:5
|
|
test/e2e/mcp_and_agents.e2e.test.ts > MCP Servers and Custom Agents > MCP Servers > should accept MCP server configuration on session resume:
nodejs/test/e2e/mcp_and_agents.e2e.test.ts#L102
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/e2e/mcp_and_agents.e2e.test.ts:102:9
|
|
test/e2e/factory.e2e.test.ts > forwards every declared subagent option to the runtime:
nodejs/test/e2e/factory.e2e.test.ts#L107
AssertionError: expected { …(3) } to match object { status: 'completed', …(1) }
(1 matching property omitted from actual)
- Expected
+ Received
{
"result": {
- "didThrow": false,
+ "didThrow": true,
},
"status": "completed",
}
❯ test/e2e/factory.e2e.test.ts:107:24
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/factory.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (ubuntu-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
test/e2e/tools.e2e.test.ts > Custom tools > clears context from a terminal tool and starts the seeded turn:
nodejs/test/e2e/tools.e2e.test.ts#L48
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/e2e/tools.e2e.test.ts:48:5
|
|
test/e2e/mcp_and_agents.e2e.test.ts > MCP Servers and Custom Agents > MCP Servers > should accept MCP server configuration on session resume:
nodejs/test/e2e/mcp_and_agents.e2e.test.ts#L102
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/e2e/mcp_and_agents.e2e.test.ts:102:9
|
|
test/e2e/factory.e2e.test.ts > forwards every declared subagent option to the runtime:
nodejs/test/e2e/factory.e2e.test.ts#L107
AssertionError: expected { …(3) } to match object { status: 'completed', …(1) }
(1 matching property omitted from actual)
- Expected
+ Received
{
"result": {
- "didThrow": false,
+ "didThrow": true,
},
"status": "completed",
}
❯ test/e2e/factory.e2e.test.ts:107:24
|
|
E2E tests (macos-latest):
nodejs/test/e2e/factory.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (macos-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest)
Process completed with exit code 1.
|
|
test/e2e/mcp_and_agents.e2e.test.ts > MCP Servers and Custom Agents > MCP Servers > should accept MCP server configuration on session resume:
nodejs/test/e2e/mcp_and_agents.e2e.test.ts#L102
Error: Test timed out in 60000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/e2e/mcp_and_agents.e2e.test.ts:102:9
|
|
test/e2e/factory.e2e.test.ts > forwards every declared subagent option to the runtime:
nodejs/test/e2e/factory.e2e.test.ts#L107
AssertionError: expected { …(3) } to match object { status: 'completed', …(1) }
(1 matching property omitted from actual)
- Expected
+ Received
{
"result": {
- "didThrow": false,
+ "didThrow": true,
},
"status": "completed",
}
❯ test/e2e/factory.e2e.test.ts:107:24
|
|
E2E tests (windows-latest):
nodejs/test/e2e/factory.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
E2E tests (windows-latest):
nodejs/test/e2e/tools.e2e.test.ts#L0
No cached response found for POST /chat/completions.
|
|
e2e gate bypassed
Publishing SDK canary despite a non-passing e2e gate (test job result: failure) via publish-force. Triggered by 'MackinnonBuck' through 'repository_dispatch'. The e2e signal was bypassed; build + feed-only guards still apply.
|