Unix build

fix(tablex): mapn could run very long if no args #299

Sign in to view logs

Triggered via pull request April 6, 2026 18:27

Tieske

synchronize #521

mapn

Status Success

Total duration 2m 36s

Artifacts –

unix_build.yml

on: pull_request

Matrix: test

Annotations

1 error, 5 warnings, and 20 notices

test (windows-latest, 5.5, msvc)

Process completed with exit code 1.

test (windows-latest, 5.5, msvc)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/

test (windows-latest, 5.1, msvc)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/

test (windows-latest, 5.4, msvc)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/

test (windows-latest, 5.3, msvc)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/

test (windows-latest, 5.2, msvc)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/

test (ubuntu-24.04, 5.3)

gh-actions-lua: Cache restored: lua:5.3.6:linux:x64:

test (ubuntu-24.04, luajit-openresty)

gh-actions-lua: Cache restored: lua:luajit-openresty:linux:x64:

test (ubuntu-24.04, 5.2)

gh-actions-lua: Cache restored: lua:5.2.4:linux:x64:

test (ubuntu-24.04, 5.1)

gh-actions-lua: Cache restored: lua:5.1.5:linux:x64:

test (ubuntu-24.04, 5.5)

gh-actions-lua: Cache restored: lua:5.5.0:linux:x64:

test (ubuntu-24.04, luajit)

gh-actions-lua: Cache restored: lua:luajit-2.1:linux:x64:

test (ubuntu-24.04, 5.4)

gh-actions-lua: Cache restored: lua:5.4.8:linux:x64:

test (macos-latest, luajit-openresty)

gh-actions-lua: Cache restored: lua:luajit-openresty:darwin:arm64:

test (macos-latest, luajit)

gh-actions-lua: Cache restored: lua:luajit-2.1:darwin:arm64:

test (macos-latest, 5.3)

gh-actions-lua: Cache restored: lua:5.3.6:darwin:arm64:

test (macos-latest, 5.1)

gh-actions-lua: Cache restored: lua:5.1.5:darwin:arm64:

test (macos-latest, 5.2)

gh-actions-lua: Cache restored: lua:5.2.4:darwin:arm64:

test (windows-latest, 5.5, msvc)

gh-actions-lua: Cache restored: lua:5.5.0:win32:x64:

test (macos-latest, 5.4)

gh-actions-lua: Cache restored: lua:5.4.8:darwin:arm64:

test (macos-latest, 5.5)

gh-actions-lua: Cache restored: lua:5.5.0:darwin:arm64:

test (windows-latest, luajit, mingw)

gh-actions-lua: Cache restored: lua:luajit-2.1:win32:x64:

test (windows-latest, 5.1, msvc)

gh-actions-lua: Cache restored: lua:5.1.5:win32:x64:

test (windows-latest, 5.4, msvc)

gh-actions-lua: Cache restored: lua:5.4.8:win32:x64:

test (windows-latest, 5.3, msvc)

gh-actions-lua: Cache restored: lua:5.3.6:win32:x64:

test (windows-latest, 5.2, msvc)

gh-actions-lua: Cache restored: lua:5.2.4:win32:x64: