Skip to content

ggml-metal: drain lingering residency sets at device free instead of asserting #11

ggml-metal: drain lingering residency sets at device free instead of asserting

ggml-metal: drain lingering residency sets at device free instead of asserting #11

Triggered via pull request June 15, 2026 14:36
Status Cancelled
Total duration 1d 0h 0m 2s
Artifacts

ci.yml

on: pull_request
ggml-ci-x64-cpu-low-perf
4m 21s
ggml-ci-x64-cpu-low-perf
ggml-ci-arm64-cpu-low-perf
3m 57s
ggml-ci-arm64-cpu-low-perf
ggml-ci-x64-cpu-high-perf
4m 34s
ggml-ci-x64-cpu-high-perf
ggml-ci-arm64-cpu-high-perf
3m 34s
ggml-ci-arm64-cpu-high-perf
ggml-ci-arm64-cpu-high-perf-sve
3m 48s
ggml-ci-arm64-cpu-high-perf-sve
ggml-ci-x64-nvidia-cuda
1d 0h
ggml-ci-x64-nvidia-cuda
ggml-ci-x64-nvidia-vulkan-cm
1d 0h
ggml-ci-x64-nvidia-vulkan-cm
ggml-ci-x64-nvidia-vulkan-cm2
1d 0h
ggml-ci-x64-nvidia-vulkan-cm2
ggml-ci-mac-metal
1d 0h
ggml-ci-mac-metal
ggml-ci-mac-vulkan
1d 0h
ggml-ci-mac-vulkan
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 12 warnings
ggml-ci-mac-metal
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
ggml-ci-mac-vulkan
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
ggml-ci-x64-nvidia-cuda
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
ggml-ci-x64-nvidia-vulkan-cm2
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
ggml-ci-x64-nvidia-vulkan-cm
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (windows-latest, static)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-arm64-cpu-high-perf
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-arm64-cpu-high-perf
Cache not found for keys: ccache-ggml-ci-arm64-cpu-high-perf-
ggml-ci-arm64-cpu-high-perf-sve
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-arm64-cpu-high-perf-sve
Cache not found for keys: ccache-ggml-ci-arm64-cpu-high-perf-sve-
ggml-ci-arm64-cpu-low-perf
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-arm64-cpu-low-perf
Cache not found for keys: ccache-ggml-ci-arm64-cpu-low-perf-
build (windows-latest, shared)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-x64-cpu-low-perf
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-x64-cpu-low-perf
Cache not found for keys: ccache-ggml-ci-x64-cpu-low-perf-
ggml-ci-x64-cpu-high-perf
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ggml-org/ccache-action@v1.2.16. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ggml-ci-x64-cpu-high-perf
Cache not found for keys: ccache-ggml-ci-x64-cpu-high-perf-