Accept any error in Function::wrap/wrap_mut/wrap_async
#1693
khvzakmain.yml
on: push
Matrix: Cross-compile to aarch64-unknown-linux-gnu
Matrix: Cross-compile to armv7-unknown-linux-gnueabihf
Matrix: Test
Matrix: Test modules
Matrix: Test modules on Windows
Matrix: Test on wasm32-unknown-emscripten
Matrix: Test on wasm32-wasip2
Matrix: Test with memory limit
Matrix: Test with address sanitizer
Annotations
105 errors and 9 warnings
|
Test with address sanitizer (ubuntu-latest, nightly, lua54)
Process completed with exit code 101.
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua52)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, luajit)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, luau-vector4)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua51)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, luau-jit)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua55)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua55)
The operation was canceled.
|
|
Test with address sanitizer (ubuntu-latest, nightly, luau)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, luau)
The operation was canceled.
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua53)
The strategy configuration was canceled because "test_with_sanitizer.ubuntu-latest_nightly_l_2" failed
|
|
Test with address sanitizer (ubuntu-latest, nightly, lua53)
The operation was canceled.
|
|
Test with memory limit (ubuntu-latest, nightly, luajit)
Process completed with exit code 101.
|
|
Test with memory limit (ubuntu-latest, nightly, lua52)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, lua55)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, luau-jit)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, lua53)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, luau-vector4)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, lua54)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, lua54)
A task was canceled.
|
|
Test with memory limit (ubuntu-latest, nightly, luau)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, luau)
The operation was canceled.
|
|
Test with memory limit (ubuntu-latest, nightly, lua51)
The strategy configuration was canceled because "test_with_memory_limit.ubuntu-latest_nightly_l_6" failed
|
|
Test with memory limit (ubuntu-latest, nightly, lua51)
The operation was canceled.
|
|
Test on wasm32-wasip2 (lua55)
Process completed with exit code 101.
|
|
Test on wasm32-wasip2 (lua52)
The strategy configuration was canceled because "test_wasm32_wasip2.lua55" failed
|
|
Test on wasm32-wasip2 (lua51)
The strategy configuration was canceled because "test_wasm32_wasip2.lua55" failed
|
|
Test on wasm32-wasip2 (lua54)
The strategy configuration was canceled because "test_wasm32_wasip2.lua55" failed
|
|
Test on wasm32-wasip2 (lua53)
The strategy configuration was canceled because "test_wasm32_wasip2.lua55" failed
|
|
Test on wasm32-unknown-emscripten (lua51)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test on wasm32-unknown-emscripten (luau)
The strategy configuration was canceled because "test_wasm32_emscripten.lua51" failed
|
|
Test on wasm32-unknown-emscripten (luau)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, lua55)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, lua55)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test on wasm32-unknown-emscripten (lua55)
The strategy configuration was canceled because "test_wasm32_emscripten.lua51" failed
|
|
Test on wasm32-unknown-emscripten (lua55)
Process completed with exit code 101.
|
|
Test (ubuntu-latest, stable, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, stable, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, lua55)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, lua55)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (ubuntu-latest, nightly, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, stable, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, luajit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, lua52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, lua53)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, luau)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, luau-vector4)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, luajit52)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test on wasm32-unknown-emscripten (lua52)
The strategy configuration was canceled because "test_wasm32_emscripten.lua51" failed
|
|
Test on wasm32-unknown-emscripten (lua52)
The operation was canceled.
|
|
Test (macos-latest, nightly, lua55)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (macos-latest, nightly, lua55)
The operation was canceled.
|
|
Test (windows-latest, stable, lua54)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, lua54)
The operation was canceled.
|
|
Test (windows-latest, stable, luau-jit)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, stable, luau-jit)
The operation was canceled.
|
|
Test (windows-latest, nightly, lua55)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, lua55)
The operation was canceled.
|
|
Test (windows-latest, nightly, lua51)
The strategy configuration was canceled because "test.windows-latest_stable_lua" failed
|
|
Test (windows-latest, nightly, lua51)
The operation was canceled.
|
|
Test on wasm32-unknown-emscripten (lua53)
The strategy configuration was canceled because "test_wasm32_emscripten.lua51" failed
|
|
Test on wasm32-unknown-emscripten (lua53)
The operation was canceled.
|
|
Test on wasm32-unknown-emscripten (lua54)
The strategy configuration was canceled because "test_wasm32_emscripten.lua51" failed
|
|
Test on wasm32-unknown-emscripten (lua54)
The operation was canceled.
|
|
Clippy (lua55)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (lua52)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (luau-vector4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (luau-jit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (lua53)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (lua54)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (lua51)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (luajit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|
|
Clippy (luau)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: giraffate/clippy-action@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/
|