Skip to content

ci: build for windows arm64 #3625

ci: build for windows arm64

ci: build for windows arm64 #3625

Triggered via pull request April 11, 2026 19:40
@clementb49clementb49
synchronize #1084
winArm
Status Failure
Total duration 12m 20s
Artifacts 4

ci.yml

on: pull_request
Matrix: build_app / build_windows
localization  /  generate_pot
27s
localization / generate_pot
localization  /  upload_on_crowdin
localization / upload_on_crowdin
release  /  create_release
release / create_release
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 10 warnings
build_app / build_windows (x86, windows-2025)
No files were found with the provided path: D:\a\basiliskLLM\basiliskLLM/output_setup/*. No artifacts will be uploaded.
build_app / build_windows (x86_64, windows-2025)
No files were found with the provided path: D:\a\basiliskLLM\basiliskLLM/output_setup/*. No artifacts will be uploaded.
build_app / build_windows (arm64, windows-11-arm)
No files were found with the provided path: C:\a\basiliskLLM\basiliskLLM/output_setup/*. No artifacts will be uploaded.
style / ruff
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/ruff-action@v3. 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_app / build_windows (x86, windows-2025)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Minionguyjpro/Inno-Setup-Action@v1.2.7. 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_app / build_windows (x86, windows-2025)
No file matched to [D:\a\basiliskLLM\basiliskLLM\**\*requirements*.txt,D:\a\basiliskLLM\basiliskLLM\**\*requirements*.in,D:\a\basiliskLLM\basiliskLLM\**\*constraints*.txt,D:\a\basiliskLLM\basiliskLLM\**\*constraints*.in,D:\a\basiliskLLM\basiliskLLM\**\pyproject.toml,D:\a\basiliskLLM\basiliskLLM\**\uv.lock,D:\a\basiliskLLM\basiliskLLM\**\*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
build_app / build_windows (x86, windows-2025)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
build_app / build_windows (x86_64, windows-2025)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Minionguyjpro/Inno-Setup-Action@v1.2.7. 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_app / build_windows (x86_64, windows-2025)
No file matched to [D:\a\basiliskLLM\basiliskLLM\**\*requirements*.txt,D:\a\basiliskLLM\basiliskLLM\**\*requirements*.in,D:\a\basiliskLLM\basiliskLLM\**\*constraints*.txt,D:\a\basiliskLLM\basiliskLLM\**\*constraints*.in,D:\a\basiliskLLM\basiliskLLM\**\pyproject.toml,D:\a\basiliskLLM\basiliskLLM\**\uv.lock,D:\a\basiliskLLM\basiliskLLM\**\*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
build_app / build_windows (x86_64, windows-2025)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
build_app / build_windows (arm64, windows-11-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, cardinalby/git-get-release-action@v1, Minionguyjpro/Inno-Setup-Action@v1.2.7. 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_app / build_windows (arm64, windows-11-arm)
No file matched to [C:\a\basiliskLLM\basiliskLLM\**\*requirements*.txt,C:\a\basiliskLLM\basiliskLLM\**\*requirements*.in,C:\a\basiliskLLM\basiliskLLM\**\*constraints*.txt,C:\a\basiliskLLM\basiliskLLM\**\*constraints*.in,C:\a\basiliskLLM\basiliskLLM\**\pyproject.toml,C:\a\basiliskLLM\basiliskLLM\**\uv.lock,C:\a\basiliskLLM\basiliskLLM\**\*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
build_app / build_windows (arm64, windows-11-arm)
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.

Artifacts

Produced during runtime
Name Size Digest
basiliskLLM.pot Expired
9.2 KB
sha256:d9676cca6cf9d358ad07f6f91cfa9062323f58224375da4f003684752ca80c47
portable_basiliskLLM_0.1a11.dev389+gb25273dde_Windows_arm64 Expired
71.6 MB
sha256:4cf7d4aed5a70200fea9cdf58fc6997f55ab1057743c699207ec9e8f55acf549
portable_basiliskLLM_0.1a11.dev389+gb25273dde_Windows_x64 Expired
73.5 MB
sha256:827dea913f33984dc21d8d059d4dea94ae0ceb13e7f5c76a3768f92e3daf96b1
portable_basiliskLLM_0.1a11.dev389+gb25273dde_Windows_x86 Expired
62.9 MB
sha256:92369cba4ea6db75c36f4c79c2539fbfba17c482d2c529de9cc34ff78e7d77e7