Skip to content
Windows x86_64

Windows x86_64 #836

Sign in to view logs

Windows x86_64

Windows x86_64 #836

Triggered via schedule October 3, 2026 08:52
@asenyaevasenyaev
⁠ 031876b
4.x
Status Failure
Total duration 40m 5s
Artifacts –

build_wheels_windows.yml

on: schedule
Matrix: Build
Matrix: Test
Release
0s
Release
Release_rolling
0s
Release_rolling
Pre-release
0s
Pre-release
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 8 warnings
Build (3.9, x64, 0, 0, 0)
Process completed with exit code 1.
Build (3.9, x86, 1, 0, 0)
Process completed with exit code 1.
Build (3.9, x86, 1, 1, 0)
Process completed with exit code 1.
Build (3.9, x86, 0, 1, 0)
Process completed with exit code 1.
Build (3.9, x86, 0, 0, 0)
Process completed with exit code 1.
Build (3.9, x64, 1, 0, 0)
Process completed with exit code 1.
Build (3.9, x64, 0, 1, 0)
Process completed with exit code 1.
Build (3.9, x64, 1, 1, 0)
Process completed with exit code 1.
Build (3.9, x64, 0, 0, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x86, 1, 0, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x86, 1, 1, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x86, 0, 1, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x86, 0, 0, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x64, 1, 0, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x64, 0, 1, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (3.9, x64, 1, 1, 0)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-python@v4, ilammy/setup-nasm@v1, microsoft/setup-msbuild@v1.1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/