[LLVM] Bump to fb2d6709f #1729
Triggered via pull request
June 10, 2026 02:57
Status
Success
Total duration
3h 21m 40s
Artifacts
32
build_llvm.yml
on: pull_request
Matrix: build
Build llvm-mlir wasm
1h 46m
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
9m 38s
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
151 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 16th, 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/
|
|
build-llvm-mlir manylinux_aarch64:
third_party/llvm-project/llvm/lib/Target/DirectX/DXContainerGlobals.cpp#L342
unused variable 'MMI' [-Wunused-variable]
|
|
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 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 16th, 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/
|
|
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 16th, 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/
|
|
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 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 16th, 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/
|
|
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 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<std::pair<const llvm::Init *, const llvm::Init *>>' 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 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 16th, 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/
|
|
build-llvm-mlir manylinux_x86_64:
third_party/llvm-project/llvm/lib/Target/DirectX/DXContainerGlobals.cpp#L342
unused variable 'MMI' [-Wunused-variable]
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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-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 16th, 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/
|
|
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.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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
call-build-eudsl / Test tblgen 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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-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 16th, 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/
|
|
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
‘buf’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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
‘buf’ may be used uninitialized [-Wmaybe-uninitialized]
|
|
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 16th, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings 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 16th, 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/
|
|
call-build-python-bindings / Test mlir-python-bindings 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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
|
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 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
eudsl_ccache_log_macos_arm64
|
460 KB |
sha256:4dc7a49f28f50fe0062e3c8ab1d586e709faca04c5aff712be26fc9efcee3a64
|
|
|
eudsl_ccache_log_ubuntu_aarch64
|
203 KB |
sha256:ae4f525b01ecf7e037cff15be70b7619cf296ddcb950a613eb1a50ad87224693
|
|
|
eudsl_ccache_log_ubuntu_x86_64
|
160 KB |
sha256:da85531e9999b7087b64712c0a2966b32d44968ffb0a94ea70856473c1ac3a30
|
|
|
eudsl_ccache_log_windows_amd64
|
249 KB |
sha256:04be2586016f6f774e1f53c4a63f6d2155235c7a71f96afab87ba01120a80a26
|
|
|
eudsl_macos_arm64_artifact
|
87.4 MB |
sha256:0ad0c9ea1ea3199a7e522f02788c8d1aba3afa29a5a31e601eaa91f9ecaefbe4
|
|
|
eudsl_python_extras_sdist_artifact
|
122 KB |
sha256:5c8e24bc9e32878e2cc885aa234770f723e4adda690471d3a1bb97b5615bc155
|
|
|
eudsl_ubuntu_aarch64_artifact
|
105 MB |
sha256:daa42dec16b91f1b3fc00684c7209a57a3868db0304304afe5fbb0d7b0be74c1
|
|
|
eudsl_ubuntu_x86_64_artifact
|
109 MB |
sha256:b7445c191100535dd61f17b399cded59efa6c9b8279700d87c74ca8afb228426
|
|
|
eudsl_windows_amd64_artifact
|
66.8 MB |
sha256:98b016067b31b20ff1109f8a5f79374cfdef5ef09c56125b942d82771e65809d
|
|
|
llvm_ccache_log_macos_arm64
|
9.51 MB |
sha256:087e5c7467ff662b84581df7e403ab664dc3c25aaa40000d46d789f8e7b6e166
|
|
|
llvm_ccache_log_manylinux_aarch64
|
4.42 MB |
sha256:9b3d4e85865bf78e1a0b27b371cccda636fc4926be0d9b7345d937e287ab1763
|
|
|
llvm_ccache_log_manylinux_x86_64
|
6.1 MB |
sha256:682808ef6fdb75fc82fa3f1620931a5071f92d34a2a590b220894d0ffbbb9d69
|
|
|
llvm_ccache_log_mlir_wasm32
|
3.13 MB |
sha256:ca30a0d75e32b4ea9c9c71c913c6007ab44c682435d6fcb162d22342bf413f15
|
|
|
llvm_ccache_log_windows_amd64
|
8.54 MB |
sha256:f798b4f26448e0981f31690920a6402065eb8b3920aa0132a93639e2a4b97b5f
|
|
|
mlir_macos_arm64_artifact
|
764 MB |
sha256:9db8f4d341847230698ad04ba809f7ea8e5a58804645af86aaa905cf771a5a35
|
|
|
mlir_manylinux_aarch64_artifact
|
785 MB |
sha256:0f200e12bae650a3747e1fe9f50e9b7e6d6058f000331b66a81ce0004493c953
|
|
|
mlir_manylinux_x86_64_artifact
|
783 MB |
sha256:b5aeaff9eb7429f86fa13d7ec78f629641fb9bba66cd9eb540054ec6992b838e
|
|
|
mlir_native_tools_macos_arm64_artifact
|
95.3 MB |
sha256:ef9f04f7cea58395749ff443050e8c4e1dbf1b8e5ff5682715379d81005a1512
|
|
|
mlir_native_tools_manylinux_aarch64_artifact
|
108 MB |
sha256:72c2f7fd31220761a2ae9a26b171aff07a1309a52f616866d800093fe27e1742
|
|
|
mlir_native_tools_manylinux_x86_64_artifact
|
110 MB |
sha256:9cac73845fe91e09c81b731edadab9c3921594a8006c3d75d198efee0b5ab31f
|
|
|
mlir_native_tools_windows_amd64_artifact
|
66.5 MB |
sha256:aa734643d4a1b002a4ba3c27db2a11b05391f743b51ec76a6f0e7fe351fa184e
|
|
|
mlir_python_bindings_macos_arm64_artifact
|
470 MB |
sha256:75d8ebcfd950a396de0ee795306eefa738e78cb1cd1d48874c13abff2ae803c6
|
|
|
mlir_python_bindings_ubuntu_aarch64_artifact
|
477 MB |
sha256:92caf961ef343a13fa8092eda9e04115a1c758b5f6d74c7cd4d36aea53a41647
|
|
|
mlir_python_bindings_ubuntu_wasm32_artifact
|
35 MB |
sha256:f6ecadc16be32a3726414ccb3161c8c630a6c1c7bef7a317689c8c6bb6ad3450
|
|
|
mlir_python_bindings_ubuntu_x86_64_artifact
|
511 MB |
sha256:ea9caafb45e822a6c381312ace199c2b2dc9d2e7d30d4b0a5af830c58b432f6a
|
|
|
mlir_python_bindings_windows_amd64_artifact
|
357 MB |
sha256:544ae68aae6ef493b1e1139c3d1ceb3e5c2416bf424cd97dd449016c57b1019d
|
|
|
mlir_wheel_macos_arm64_artifact
|
650 MB |
sha256:db61ce4304a1c417438105ff726d874553c50d94c361a8a83ed7c5c8b560f900
|
|
|
mlir_wheel_manylinux_aarch64_artifact
|
671 MB |
sha256:21d7849387cd9558db76734c4ec52e33979960016f8d277f2988130c3107ca05
|
|
|
mlir_wheel_manylinux_x86_64_artifact
|
676 MB |
sha256:4622c6ccaa9c92c4af6868f3cc5c3bb88de4270eb8565fe47da16f5268ab75a2
|
|
|
mlir_wheel_ubuntu_wasm32_artifact
|
190 MB |
sha256:1617b5b4b1dcd49ca3febc42ea72ae2e0f9631ede9ab618842cc8464e706358e
|
|
|
mlir_wheel_windows_amd64_artifact
|
478 MB |
sha256:a7ac14fce6ead94888fbcdd26a29241c169c9b2a4e861d283348d02d4cb68817
|
|
|
mlir_windows_amd64_artifact
|
545 MB |
sha256:21cd33f61b3f3410973b8ad008deb2cf9822c4e9e1facae11d554d7f6e92e615
|
|