Skip to content

Optimize CI workflows with dynamic matrix and cache cleanup #260

Optimize CI workflows with dynamic matrix and cache cleanup

Optimize CI workflows with dynamic matrix and cache cleanup #260

Triggered via pull request April 2, 2026 18:44
Status Failure
Total duration 11m 55s
Artifacts

SyntaxKit.yml

on: pull_request
Configure Build Matrix
3s
Configure Build Matrix
Matrix: Build for Android
Matrix: Build on macOS (Full)
Matrix: Build on macOS
Matrix: Build on Ubuntu
Matrix: Build on Windows
Linting
0s
Linting
Documentation Validation
0s
Documentation Validation
Fit to window
Zoom out
Zoom in

Annotations

39 errors and 10 warnings
Build on Windows (windows-2022)
Process completed with exit code 1.
Build on Windows (windows-2025)
Process completed with exit code 1.
Build on Ubuntu (jammy, 6.2, wasm)
No coverage files found (or none succeeded to convert)!
Build on Ubuntu (noble, 6.1)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.0, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.0)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.2, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.1, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.0, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.2)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.0)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.0, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.2, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.1)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.3, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.3, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.3)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.1, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.1, wasm-embedded)
The operation was canceled.
Build on Ubuntu (noble, 6.0, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.0, wasm)
The operation was canceled.
Build on Ubuntu (noble, 6.2, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.2, wasm)
The operation was canceled.
Build on Ubuntu (noble, 6.3)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.3)
The operation was canceled.
Build on Ubuntu (jammy, 6.1, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.1, wasm-embedded)
The operation was canceled.
Build on Ubuntu (noble, 6.3, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.3, wasm)
The operation was canceled.
Build on Ubuntu (noble, 6.1, wasm)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.1, wasm)
The operation was canceled.
Build on Ubuntu (jammy, 6.2)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (jammy, 6.2)
The operation was canceled.
Build on Ubuntu (noble, 6.3, wasm-embedded)
The strategy configuration was canceled because "build-ubuntu.jammy_6_2_wasm" failed
Build on Ubuntu (noble, 6.3, wasm-embedded)
The operation was canceled.
Build for Android (6.2, 34)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.3, 34)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.3, 33)
The process '/usr/bin/sh' failed with exit code 1
Build for Android (6.2, 33)
The process '/usr/bin/sh' failed with exit code 1
Build on Ubuntu (jammy, 6.2, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.1, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.3, wasm)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build on Ubuntu (noble, 6.3, wasm-embedded)
Found .xctest bundles in Wasm build (unexpected - Wasm builds should produce .wasm files)
Build for Android (6.2, 34)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build for Android (6.3, 34)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build for Android (6.3, 33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build for Android (6.2, 33)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Build on macOS (Full) (ios, macos-26, /Applications/Xcode_26.4.app, iPhone 17 Pro, 26.4, true)
DerivedData cache has been restored with same key: xcode-deriveddata-macOS-26.4-31ae34a0e53690a9961677e5977a663f15f94818f2762f060af770ee9eab5480-c29e8fe3ad9e6b54d130db1dbd8327ae480ddcb9ff7e541be9f79dda53080a96-false-5cc15c3cf0195526e824fa01855f77f4f0225839