[LLVM] Bump to 14e04edf0 #1532
build_llvm.yml
on: pull_request
Matrix: build
Build llvm-mlir wasm
1h 48m
Matrix: call-build-eudsl / build-eudsl
call-deploy-pip-page
/
deploy
Matrix: call-build-python-bindings / build-mlir-python-bindings
Matrix: call-build-eudsl / release-eudsl
Matrix: call-build-eudsl / test-eudsl-llvmpy
Matrix: call-build-eudsl / test-eudsl-tblgen
call-build-python-bindings
/
...
/
Build eudsl-python-extras sdist
14s
Matrix: call-build-python-bindings / release-mlir-python-bindings
call-build-python-bindings
/
Test mlir-python-bindings wasm
10m 32s
Matrix: call-build-python-bindings / test-mlir-python-bindings
call-build-eudsl
/
...
/
deploy
call-build-python-bindings
/
...
/
Release eudsl-python-extras
Matrix: call-build-python-bindings / call-build-eudsl-python-extras / test-eudsl-python-extras
call-build-python-bindings
/
...
/
deploy
call-build-python-bindings
/
...
/
deploy
Annotations
146 warnings
|
build-llvm-mlir manylinux_aarch64
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, actions/checkout@v4.2.2, actions/upload-artifact@v4, aminya/setup-cpp@v1, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-llvm-mlir manylinux_aarch64
Volume mount /:/ghhost is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
|
|
Build llvm-mlir wasm
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 llvm-mlir wasm
No files were found with the provided path: llvm-install. No artifacts will be uploaded.
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<unsigned long, llvm::Function *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<unsigned int, llvm::MDNode *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<mlir::OpOperand>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<mlir::detail::ParallelDiagnosticHandlerImpl::ThreadDiagnostic>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<const void *, (anonymous namespace)::AliasInitializer::InProgressAliasInfo>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<const llvm::RuntimeLibcallImpl *>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::directive::Spelling>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::TrackingStatistic *>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<std::pair<float, llvm::BPFunctionNode *>>' is deprecated [-Wdeprecated-declarations]
|
|
Build llvm-mlir wasm
'get_temporary_buffer<llvm::BPFunctionNode>' is deprecated [-Wdeprecated-declarations]
|
|
build-llvm-mlir macos_arm64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-llvm-mlir macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
build-llvm-mlir windows_amd64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-llvm-mlir manylinux_x86_64
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, actions/checkout@v4.2.2, actions/upload-artifact@v4, aminya/setup-cpp@v1, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-llvm-mlir manylinux_x86_64
Volume mount /:/ghhost is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
|
|
call-build-eudsl / Build eudsl macos_arm64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Build eudsl macos_arm64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
call-build-eudsl / Build eudsl windows_amd64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Build eudsl windows_amd64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64:
projects/eudsl-llvmpy/src/eudslllvm_ext.cpp#L117
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
adding 'int' to a string does not append to the string [-Wstring-plus-int]
|
|
call-build-eudsl / Build eudsl ubuntu_aarch64
format specifies type 'unsigned int' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_wasm32
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings macos_arm64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings macos_arm64
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64:
projects/eudsl-llvmpy/src/eudslllvm_ext.cpp#L117
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
temporary bound to reference member of allocated object will be destroyed at the end of the full-expression [-Wdangling-field]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
'LLVMStructType' is deprecated: Use of the global context is deprecated, use LLVMStructTypeInContext instead [-Wdeprecated-declarations]
|
|
call-build-eudsl / Build eudsl ubuntu_x86_64
cibuildwheel: Invalid skip selector: 'pp*'. This selector matches a group that wasn't enabled. Enable it using the `enable` option or remove this selector. This selector will have no effect.
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_x86_64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_x86_64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_aarch64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_aarch64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_x86_64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_aarch64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy macos_arm64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_x86_64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy windows_amd64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_aarch64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy windows_amd64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_aarch64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy windows_amd64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_aarch64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen ubuntu_aarch64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test llvmpy ubuntu_aarch64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen macos_arm64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-eudsl / Test tblgen windows_amd64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_aarch64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings windows_amd64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
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, actions/checkout@v4.2.2, actions/setup-python@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, dawidd6/action-download-artifact@v11, szenius/set-timezone@v2.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / Build mlir-python-bindings ubuntu_x86_64
unknown option after ‘#pragma GCC diagnostic’ kind [-Wpragmas]
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Build eudsl-python-extras sdist
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras windows_amd64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras windows_amd64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras windows_amd64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_aarch64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_aarch64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_x86_64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras ubuntu_aarch64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras windows_amd64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings windows_amd64 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings windows_amd64 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / call-build-eudsl-python-extras / Test eudsl-python-extras macos_arm64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, dawidd6/action-download-artifact@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings windows_amd64 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings windows_amd64 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings macos_arm64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_aarch64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_aarch64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.14t
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings ubuntu_x86_64 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings wasm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.2.2, actions/download-artifact@v4, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
eudsl_ccache_log_macos_arm64
|
444 KB |
sha256:b213a20d950ee65309f387dbaa044fd689f0112fb2a964c8f4f5ffed3f6efdd4
|
|
|
eudsl_ccache_log_ubuntu_aarch64
|
219 KB |
sha256:05c7a15f692d5192f041bdd78985b1a2cf6bfc257988e3f468b3a2c55ad377a5
|
|
|
eudsl_ccache_log_ubuntu_x86_64
|
194 KB |
sha256:0f2162ab13a67bdc27087c430bb41184cc45db1a6ee6296bed5cc26495cd1f2d
|
|
|
eudsl_ccache_log_windows_amd64
|
231 KB |
sha256:e73a0020cfd702d1645c72e912a33439fc48f269a0b32e7c9b2651ea23b5b9a8
|
|
|
eudsl_macos_arm64_artifact
|
84.5 MB |
sha256:3f2abafda1cd7a5e1365477b9a5891b5b72661ab1c78b30bc5df16f9f9336d7c
|
|
|
eudsl_python_extras_sdist_artifact
|
122 KB |
sha256:035381561decf591b2bc234ced5537cec8dd6f569ada4514720670f2e013db50
|
|
|
eudsl_ubuntu_aarch64_artifact
|
102 MB |
sha256:6de94598d27a9d0db4697f20f2d1678a3ebfacd40a754b952898d99e17ac945e
|
|
|
eudsl_ubuntu_x86_64_artifact
|
106 MB |
sha256:41f6b84e7961ff61567e038897d2366a5f4934995831aeeb3dfd4cca7e044a10
|
|
|
eudsl_windows_amd64_artifact
|
65 MB |
sha256:828959c1fc059bee7462c63f4b548c4c65065df72e39f094f38ecbed4dedf567
|
|
|
llvm_ccache_log_macos_arm64
|
7.24 MB |
sha256:621ded9d3b8862ab7be5bc522a305620f1f31cb428ced95381e1a032036a3bd9
|
|
|
llvm_ccache_log_manylinux_aarch64
|
4.3 MB |
sha256:3139b0650bdd8f94a7673137ee9f6d50eda109608a85de8ade7d8990d6f46b53
|
|
|
llvm_ccache_log_manylinux_x86_64
|
5.89 MB |
sha256:e9eb8aa6c167c6f5291665ce147d8586a185fed089224aed0c36b00a4bc53d2f
|
|
|
llvm_ccache_log_mlir_wasm32
|
3.06 MB |
sha256:195a4104c17a547f05badce7221098809f3b32c3f8f5e5e2b9d3eee306c24a6e
|
|
|
llvm_ccache_log_windows_amd64
|
7.47 MB |
sha256:4e6932e6f282c07ec5fad7ec298e2c78c12b6ea90766d1f99bf52e977244b414
|
|
|
mlir_macos_arm64_artifact
|
722 MB |
sha256:001af41a865bb4bbf09ab2c02f9fa0c1f888fdbf691f5bace72ab015f31bbac6
|
|
|
mlir_manylinux_aarch64_artifact
|
748 MB |
sha256:4ca3546cf0294b055252773d2846ab9108215f86ddfee497ce06491ab41759f4
|
|
|
mlir_manylinux_x86_64_artifact
|
746 MB |
sha256:3b82b1c4b0e88ef4cfb7a3805e3c7d7cc57fa94b9e204fdec8d008b32b0f542d
|
|
|
mlir_native_tools_macos_arm64_artifact
|
88.9 MB |
sha256:926f6d05941dc1b7261e9d5351930c21368a1776dc4963a24be60cc093c7a9f6
|
|
|
mlir_native_tools_manylinux_aarch64_artifact
|
101 MB |
sha256:73262a119e1158c33c16edc5136119ea2ac8f2a3533469993e1e6628bfa440de
|
|
|
mlir_native_tools_manylinux_x86_64_artifact
|
103 MB |
sha256:310199c8953467ca6680ddc72c499f2273e3d3e29fde1c6ec7cfcab05a2db746
|
|
|
mlir_native_tools_windows_amd64_artifact
|
61.6 MB |
sha256:a16bebc9c96ad9ee55f7655559f8a97e07db3169a3e9184218320eae0609bc1a
|
|
|
mlir_python_bindings_macos_arm64_artifact
|
399 MB |
sha256:5151fb52cb0ef6c8ebc01b59c5745b399d3fc971c2e0dfabb58b40fb8366985d
|
|
|
mlir_python_bindings_ubuntu_aarch64_artifact
|
452 MB |
sha256:112b0027aa22869721deaa1a91b49325d2847123d3923444a34f8d6a42c10a12
|
|
|
mlir_python_bindings_ubuntu_wasm32_artifact
|
44.9 MB |
sha256:afa4a101a7a94cc40d07f0998ff38f91d5f716001b239cea8b2242ed8b39fa46
|
|
|
mlir_python_bindings_ubuntu_x86_64_artifact
|
481 MB |
sha256:82daf4538bc4694716084ece640736b5c9e935a48801a962573a5c2e5df89f96
|
|
|
mlir_python_bindings_windows_amd64_artifact
|
334 MB |
sha256:9f84a0aa0f8dabc66aa1199c380b99787f87166d82014e60633e57e07d8a7d94
|
|
|
mlir_wheel_macos_arm64_artifact
|
618 MB |
sha256:5454e16afb6eb6f39651d37a4e159ba46035b391d5ce88eb5d92ecaa8f7c03f3
|
|
|
mlir_wheel_manylinux_aarch64_artifact
|
640 MB |
sha256:f5b55a4809a72d5683c827bae657b0f185a46a9041f37213a37b69cd42dd21ca
|
|
|
mlir_wheel_manylinux_x86_64_artifact
|
645 MB |
sha256:e4c4bde227cbef1f7a431c077521304881ef4e675df3053954cb0f7ee5010669
|
|
|
mlir_wheel_ubuntu_wasm32_artifact
|
181 MB |
sha256:737bf46edb272d1f5e21bd32a36ea59d63c4f2591b646b3f0c3b98aa4c21468e
|
|
|
mlir_wheel_windows_amd64_artifact
|
455 MB |
sha256:390edb92f9572dc2048e72fae12bb337dd6e62f75c97741b7272b85e2949671c
|
|
|
mlir_windows_amd64_artifact
|
517 MB |
sha256:6575ff4d210c59db2fe76140e263fbdd39b8b79e838a95547fbf3eab38110922
|
|