Skip to content

feat: automatic checkpoints for models that need it #1052

feat: automatic checkpoints for models that need it

feat: automatic checkpoints for models that need it #1052

Triggered via pull request March 12, 2026 09:26
@giladgdgiladgd
synchronize #573
gilad/qwen3.5
Status Failure
Total duration 1h 48m 16s
Artifacts 9

build.yml

on: pull_request
Resolve next release
0s
Resolve next release
Matrix: build-binaries
Standalone tests
4m 29s
Standalone tests
Model dependent tests
1h 42m
Model dependent tests
Update documentation website - no version release
0s
Update documentation website - no version release
Release
0s
Release
Update documentation website
0s
Update documentation website
Auto-approve documentation website deployment
0s
Auto-approve documentation website deployment
Matrix: build-electron-example
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 14 warnings
Standalone tests
Process completed with exit code 1.
test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts > resolveChatWrapper > should resolve to specialized QwenChatWrapper 2 - Qwen 3: test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts#L880
AssertionError: expected JinjaTemplateChatWrapper{ …(17) } to be an instance of QwenChatWrapper ❯ test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts:880:35
test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts > resolveChatWrapper > should resolve to specialized QwenChatWrapper - QwQ: test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts#L868
AssertionError: expected JinjaTemplateChatWrapper{ …(17) } to be an instance of QwenChatWrapper ❯ test/standalone/chatWrappers/utils/resolveChatWrapper.test.ts:868:35
test/standalone/chatWrappers/QwenChatWrapper.test.ts > QwenChatWrapper > should generate valid context text for 2 sequential function calls: test/standalone/chatWrappers/QwenChatWrapper.test.ts#L264
Error: Snapshot `QwenChatWrapper > should generate valid context text for 2 sequential function calls 1` mismatched - Expected + Received @@ -42,22 +42,30 @@ "What is the time?", new SpecialTokensText("<|im_end|> <|im_start|>assistant "), "I'll fetch some information for you", - new SpecialTokensText("<tool_call>"), - " - {"name": "getTime", "arguments": {"hours": "24", "seconds": true}} - ", + new SpecialTokensText("<tool_call> + <function="), + "getTime> + <parameter=params> + {"hours": "24", "seconds": true}", - new SpecialTokensText("</tool_call>"), + new SpecialTokensText(" + </parameter> + </function> + </tool_call>"), " ", - new SpecialTokensText("<tool_call>"), - " - {"name": "getDate", "arguments": {"timezone": 0}} - ", + new SpecialTokensText("<tool_call> + <function="), + "getDate> + <parameter=params> + {"timezone": 0}", - new SpecialTokensText("</tool_call><|im_end|> + new SpecialTokensText(" + </parameter> + </function> + </tool_call><|im_end|> <|im_start|>user <tool_response> "), ""22:00:00"", new SpecialTokensText(" ❯ test/standalone/chatWrappers/QwenChatWrapper.test.ts:264:29
test/standalone/chatWrappers/QwenChatWrapper.test.ts > QwenChatWrapper > should generate valid context text: test/standalone/chatWrappers/QwenChatWrapper.test.ts#L146
Error: Snapshot `QwenChatWrapper > should generate valid context text 2` mismatched - Expected + Received @@ -39,15 +39,19 @@ <|im_start|>user "), "What is the time?", new SpecialTokensText("<|im_end|> <|im_start|>assistant - <tool_call>"), - " - {"name": "getTime", "arguments": {"hours": "24", "seconds": true}} - ", + <tool_call> + <function="), + "getTime> + <parameter=params> + {"hours": "24", "seconds": true}", - new SpecialTokensText("</tool_call><|im_end|> + new SpecialTokensText(" + </parameter> + </function> + </tool_call><|im_end|> <|im_start|>user <tool_response> "), ""22:00:00"", new SpecialTokensText(" ❯ test/standalone/chatWrappers/QwenChatWrapper.test.ts:146:30
Model dependent tests
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - macOS arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - macOS arm64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build binaries - macOS arm64
cmake 4.2.3 is already installed and up-to-date. To reinstall 4.2.3, run: brew reinstall cmake
Standalone tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - macOS x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - macOS x64
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build binaries - macOS x64
cmake 4.2.3 is already installed and up-to-date. To reinstall 4.2.3, run: brew reinstall cmake
Build binaries - Ubuntu (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.15. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - Ubuntu (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.30. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - Windows (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.15. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build binaries - Windows (2)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Q4iyaQAAAAACd2JEiHnkRrUuue83YP/ZQ0hHRURHRTE3MTQARWRnZQ==
Build binaries - Windows (2)
Failed to restore: Cache service responded with 400
Build binaries - Windows (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, Jimver/cuda-toolkit@v0.2.30. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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
bins-linux-1
155 MB
sha256:e34da8715d31a794dec633c2956dc8d2fc00874b3e6bd7d410dd184168dc0ea3
bins-linux-2
194 MB
sha256:166805904857ac39e80c43ae55dfc0b4daa4fddf0f6363886c5bb93a8462eec1
bins-mac-arm64
1.81 MB
sha256:1d837f757b8c732df81e8522d8fb71b7f1fce20f54a8f32159e1235099f0bd36
bins-mac-x64
7.91 MB
sha256:bf062314d4e771999dedc13caf023cdaa481586c38d4b71fcf55bd593d0d5899
bins-win-1
146 MB
sha256:1ea75b6d8914e90ed6420b4465b67f1d1b3092630c9563a77873bc4ba0420c68
bins-win-2
192 MB
sha256:ec086c70f3238208e3d833915f903acb3615cab0fce9061fbc0d82e6f28cb6d4
build
863 KB
sha256:7e19bfda9773be0ee5ba3bb72962af69c726f537627e000c7d436ab90f868274
build-templates
32.6 KB
sha256:59b815877db48de02f1ff372094f8b05ff3f26d0a36e830f847919ae4e84a664
llama.cpp
263 MB
sha256:5146670c449c3b5345beeee614c91e72d846d76afbfa0e1dde785e10b218ec8c