Skip to content

runtime-canary

runtime-canary #47

Triggered via repository dispatch August 20, 2026 09:57
@MackinnonBuckMackinnonBuck
runtime-canary 23dcc2e
Status Failure
Total duration 7m 30s
Artifacts

sdk-canary.yml

on: repository_dispatch
Resolve runtime inputs
5s
Resolve runtime inputs
Matrix: test
Publish SDK canary (internal feed)
39s
Publish SDK canary (internal feed)
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
E2E tests (ubuntu-latest)
Process completed with exit code 1.
test/e2e/rpc_server_misc.e2e.test.ts > Miscellaneous server-scoped RPC > should shut down owned runtime: nodejs/test/e2e/rpc_server_misc.e2e.test.ts#L212
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/rpc_server_misc.e2e.test.ts:212:5
E2E tests (ubuntu-latest): nodejs/test/e2e/factory.e2e.test.ts#L0
No cached response found for POST /chat/completions.
E2E tests (macos-latest)
Process completed with exit code 1.
E2E tests (macos-latest): nodejs/test/e2e/factory.e2e.test.ts#L0
No cached response found for POST /chat/completions.
E2E tests (windows-latest)
Process completed with exit code 1.
E2E tests (windows-latest): nodejs/test/e2e/factory.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.