Added Multicast dynamic config #614
marcoSantipython-bindings.yml
on: pull_request
Matrix: Test Python bindings
Matrix: Build & Test on RISC-V (QEMU)
Annotations
33 errors and 14 warnings
|
Test Python bindings (macos-26, 3.10)
Process completed with exit code 1.
|
|
Test Python bindings (macos-26, 3.11)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-15-intel, 3.10)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-15-intel, 3.11)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-26, 3.13)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-15-intel, 3.14)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-26, 3.14)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-26, 3.12)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.12)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.12)
The operation was canceled.
|
|
Test Python bindings (ubuntu-24.04, 3.13)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.13)
The operation was canceled.
|
|
Test Python bindings (ubuntu-24.04, 3.10)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.10)
The operation was canceled.
|
|
Test Python bindings (ubuntu-24.04, 3.11)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.11)
The operation was canceled.
|
|
Test Python bindings (ubuntu-24.04, 3.14)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (ubuntu-24.04, 3.14)
The operation was canceled.
|
|
Test Python bindings (macos-15-intel, 3.13)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-15-intel, 3.13)
The operation was canceled.
|
|
Test Python bindings (macos-15-intel, 3.12)
The strategy configuration was canceled because "python-tests.macos-26_3_10" failed
|
|
Test Python bindings (macos-15-intel, 3.12)
The operation was canceled.
|
|
Build & Test on RISC-V (QEMU) (3.14)
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.14)
The operation was canceled.
|
|
Build & Test on RISC-V (QEMU) (3.10)
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.10)
The operation was canceled.
|
|
Build & Test on RISC-V (QEMU) (3.13)
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.13)
The operation was canceled.
|
|
Build & Test on RISC-V (QEMU) (3.11)
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.11)
The operation was canceled.
|
|
Python Bindings Unit Tests
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.12)
Canceling since a higher priority waiting request for build-python-71 exists
|
|
Build & Test on RISC-V (QEMU) (3.12)
The operation was canceled.
|
|
Test Python bindings (macos-26, 3.10)
curl 8.19.0 is already installed and up-to-date.
To reinstall 8.19.0, run:
brew reinstall curl
|
|
Test Python bindings (macos-26, 3.10)
gcc 15.2.0_1 is already installed and up-to-date.
To reinstall 15.2.0_1, run:
brew reinstall gcc
|
|
Test Python bindings (macos-26, 3.10)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
Test Python bindings (macos-15-intel, 3.13)
curl 8.19.0 is already installed and up-to-date.
To reinstall 8.19.0, run:
brew reinstall curl
|
|
Test Python bindings (macos-15-intel, 3.13)
gcc 15.2.0_1 is already installed and up-to-date.
To reinstall 15.2.0_1, run:
brew reinstall gcc
|
|
Test Python bindings (macos-15-intel, 3.13)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
Test Python bindings (macos-15-intel, 3.12)
curl 8.19.0 is already installed and up-to-date.
To reinstall 8.19.0, run:
brew reinstall curl
|
|
Test Python bindings (macos-15-intel, 3.12)
gcc 15.2.0_1 is already installed and up-to-date.
To reinstall 15.2.0_1, run:
brew reinstall gcc
|
|
Test Python bindings (macos-15-intel, 3.12)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
Build & Test on RISC-V (QEMU) (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: uraimo/run-on-arch-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test on RISC-V (QEMU) (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: uraimo/run-on-arch-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test on RISC-V (QEMU) (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: uraimo/run-on-arch-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test on RISC-V (QEMU) (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: uraimo/run-on-arch-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build & Test on RISC-V (QEMU) (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: uraimo/run-on-arch-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|