fix(ci): release workflow never built @modelforge/contracts before ru… #28
voidstackloopAnnotations
13 errors and 3 warnings
|
build (windows-latest)
Process completed with exit code 1.
|
|
src/model-fit-estimator.test.ts > estimateModelFit > verdict 'unsafe' when the model cannot fit RAM or VRAM under any configuration:
app/src/model-fit-estimator.test.ts#L25
Error: ENOSPC: no space left on device, ftruncate
❯ sparseFile src/model-fit-estimator.test.ts:25:8
❯ src/model-fit-estimator.test.ts:76:27
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { errno: -4055, code: 'ENOSPC', syscall: 'ftruncate' }
|
|
src/audit-log-store.test.ts > audit-log-store > caps retained events instead of growing without bound:
app/src/audit-log-store.test.ts#L40
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".
❯ src/audit-log-store.test.ts:40:5
|
|
src/media.test.ts > media.extractVideoFrames > runs as a user-interactive lease (item 1: media processing here is always a direct chat-attachment action):
app/src/resource-orchestrator.ts#L545
ResourceAdmissionError: Requested 2 CPU threads, but only 1 are safely available.
❯ ResourceOrchestrator.rejectPending src/resource-orchestrator.ts:545:24
❯ ResourceOrchestrator.drain src/resource-orchestrator.ts:348:30
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { status: 'rejected-insufficient-resources', requestId: '2d57d2d7-1168-449c-8726-1a6c66120d32', reasons: [ 'Requested 2 CPU threads, but only 1 are safely available.' ] }
|
|
src/media.test.ts > media.extractVideoFrames > cleans up its own temp directory even after a successful extraction:
app/src/resource-orchestrator.ts#L545
ResourceAdmissionError: Requested 2 CPU threads, but only 1 are safely available.
❯ ResourceOrchestrator.rejectPending src/resource-orchestrator.ts:545:24
❯ ResourceOrchestrator.drain src/resource-orchestrator.ts:348:30
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { status: 'rejected-insufficient-resources', requestId: '8fa734d9-7186-4c0c-ae86-ef9c72c5a736', reasons: [ 'Requested 2 CPU threads, but only 1 are safely available.' ] }
|
|
src/media.test.ts > media.extractVideoFrames > returns the extracted frame(s) as base64 JPEG image data:
app/src/resource-orchestrator.ts#L545
ResourceAdmissionError: Requested 2 CPU threads, but only 1 are safely available.
❯ ResourceOrchestrator.rejectPending src/resource-orchestrator.ts:545:24
❯ ResourceOrchestrator.drain src/resource-orchestrator.ts:348:30
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { status: 'rejected-insufficient-resources', requestId: '047a0102-9b63-47a1-9030-6c9fd91eb3dc', reasons: [ 'Requested 2 CPU threads, but only 1 are safely available.' ] }
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > propagates an abort through the fake module the same way a real generation would:
app/src/llamacpp-manager.test.ts#L452
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:452:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > throws a clear, actionable error instead of an opaque one when tools can't fit even the model's max context:
app/src/llamacpp-manager.test.ts#L438
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:438:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > grows the context past a too-small configured contextLength to fit large tool definitions:
app/src/llamacpp-manager.test.ts#L420
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:420:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > returns a tool call through the same onToken contract every other provider uses:
app/src/llamacpp-manager.test.ts#L401
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:401:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > rebuilds context when persisted history no longer matches the warm conversation:
app/src/llamacpp-manager.test.ts#L386
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:386:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > reuses a warm context for a matching follow-up in the same conversation:
app/src/llamacpp-manager.test.ts#L369
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:369:5
|
|
src/llamacpp-manager.test.ts > chat() end-to-end via the fake node-llama-cpp module > streams tokens through onToken exactly like a real generation would:
app/src/llamacpp-manager.test.ts#L359
Error: Test timed out in 20000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ src/llamacpp-manager.test.ts:359:5
|
|
build (windows-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11d5960a326750d5838078e36cf38b85af677262, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (macos-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11d5960a326750d5838078e36cf38b85af677262, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build (ubuntu-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11d5960a326750d5838078e36cf38b85af677262, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
dist-ubuntu-latest
|
581 MB |
sha256:0dddb5c436cc8230923add61d449d28d2890d6933bafb6cde3e249015ffa7db0
|
|