Skip to content

CI

CI #6595

Triggered via schedule May 15, 2026 05:10
Status Failure
Total duration 3m 31s
Artifacts

ci.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 8 warnings, and 1 notice
windows / setup
Command failed: make ./vc/v.c:1745:2: error: #error VERROR_MESSAGE Header file <sys/mman.h>, needed for module `builtin.closure` was not found. Please install the corresponding development headers. 1745 | #error VERROR_MESSAGE Header file <sys/mman.h>, needed for module `builtin.closure` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:1837:2: error: #error VERROR_MESSAGE Header file <termios.h>, needed for module `term.termios` was not found. Please install the corresponding development headers. 1837 | #error VERROR_MESSAGE Header file <termios.h>, needed for module `term.termios` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:1854:2: error: #error VERROR_MESSAGE Header file <sys/ioctl.h>, needed for module `term.termios` was not found. Please install the corresponding development headers. 1854 | #error VERROR_MESSAGE Header file <sys/ioctl.h>, needed for module `term.termios` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:4850:2: error: #error VERROR_MESSAGE Header file <sys/ptrace.h>, needed for module `os` was not found. Please install the corresponding development headers. 4850 | #error VERROR_MESSAGE Header file <sys/ptrace.h>, needed for module `os` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:5072:2: error: #error VERROR_MESSAGE Header file <sys/utsname.h>, needed for module `os` was not found. Please install the corresponding development headers. 5072 | #error VERROR_MESSAGE Header file <sys/utsname.h>, needed for module `os` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:5106:2: error: #error VERROR_MESSAGE Header file <sys/statvfs.h>, needed for module `os` was not found. Please install the corresponding development headers. 5106 | #error VERROR_MESSAGE Header file <sys/statvfs.h>, needed for module `os` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c: In function 'v_os_execute_set_cloexec': ./vc/v.c:5141:31: error: 'F_GETFD' undeclared (first use in this function) 5141 | int flags = fcntl(fd, F_GETFD, 0); | ^~~~~~~ ./vc/v.c:5141:31: note: each undeclared identifier is reported only once for each function it appears in ./vc/v.c:5143:27: error: 'F_SETFD' undeclared (first use in this function) 5143 | fcntl(fd, F_SETFD, flags | FD_CLOEXEC); | ^~~~~~~ ./vc/v.c:5143:44: error: 'FD_CLOEXEC' undeclared (first use in this function); did you mean 'FD_CLOSE'? 5143 | fcntl(fd, F_SETFD, flags | FD_CLOEXEC); | ^~~~~~~~~~ | FD_CLOSE ./vc/v.c: At top level: ./vc/v.c:5451:2: error: #error VERROR_MESSAGE Header file <sys/ioctl.h>, needed for module `term` was not found. Please install the corresponding development headers. 5451 | #error VERROR_MESSAGE Header file <sys/ioctl.h>, needed for module `term` was not found. Please install the corresponding development headers. | ^~~~~ ./vc/v.c:6521:9: error: unknown type name 'pthread_t'; did you mean '_threadid'? 6521 | typedef pthread_t __v_thread; | ^~~~~~~~~ | _threadid ./vc/v.c:7951:9: error: unknown type name 'pthread_mutex_t' 7951 | pthread_mutex_t closure_mtx; | ^~~~~~~~~~~~~~~ ./vc/v.c:8372:9: error: unknown type name 'pthread_mutex_t' 8372 | pthread_mutex_t mutex; | ^~~~~~~~~~~~~~~ ./vc/v.c:8376:9: error: unknown type name 'pthread_rwlock_t' 8376 | pthread_rwlock_t mutex; | ^~~~~~~~~~~~~~~~ ./vc/v.c:8381:9: error: unknown type name 'pthread_rwlockattr_t' 8381 | pthread_rwlockattr_t attr; | ^~~~~~~~~~~~~~~~~~~~ ./vc/v.c: In function 'builtin__closure__closure_alloc_platform': ./vc/v.c:27461:57: error: 'PROT_READ' undeclared (first use in this function); did you mean
lint / fmt
Process completed with exit code 1.
macos / build
Process completed with exit code 1.
linux / build
Process completed with exit code 1.
macos / setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/save@v3, actions/checkout@v4, vlang/setup-v@v1.3. 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/
macos / setup
Cache save failed.
windows / setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: vlang/setup-v@v1.3. 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/
linux / setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/save@v3, actions/checkout@v4, vlang/setup-v@v1.3. 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/
linux / setup
Cache save failed.
lint / fmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, vlang/setup-v@v1.3. 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/
macos / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, vlang/setup-v@v1.3. 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/
linux / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, vlang/setup-v@v1.3. 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/
windows / setup
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026