Skip to content

feat(qt5): add qt5serialport and qt5serialbus packages #166

feat(qt5): add qt5serialport and qt5serialbus packages

feat(qt5): add qt5serialport and qt5serialbus packages #166

Triggered via pull request April 5, 2026 07:31
Status Failure
Total duration 6h 59m 29s
Artifacts 20

multi-arch-test-build.yml

on: pull_request
Matrix: Feeds Package Test Build / build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
Feeds Package Test Build / Test powerpc_8548
Process completed with exit code 2.
Feeds Package Test Build / Test powerpc_464fp
Process completed with exit code 2.
Feeds Package Test Build / Test mipsel_24kc
Process completed with exit code 2.
Feeds Package Test Build / Test arm_cortex-a9_vfpv3-d16
Process completed with exit code 2.
Feeds Package Test Build / Test mips_24kc
Process completed with exit code 2.
Feeds Package Test Build / Test i386_pentium-mmx
Process completed with exit code 2.
Feeds Package Test Build / Test arm_cortex-a15_neon-vfpv4
Process completed with exit code 2.
Feeds Package Test Build / Test aarch64_generic
Process completed with exit code 2.
Feeds Package Test Build / Test x86_64
Process completed with exit code 2.
Feeds Package Test Build / Test riscv64_generic
Process completed with exit code 2.
Feeds Package Test Build / Test powerpc_8548
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test powerpc_464fp
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test mipsel_24kc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test arm_cortex-a9_vfpv3-d16
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test mips_24kc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test i386_pentium-mmx
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test arm_cortex-a15_neon-vfpv4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test aarch64_generic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Feeds Package Test Build / Test riscv64_generic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/setup-buildx-action@v3, docker/setup-qemu-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/

Artifacts

Produced during runtime
Name Size Digest
aarch64_generic-PR72-e909e23-logs
1.32 MB
sha256:dd3872693cd21cdb4f4e4816ca85d0f0bb6828df1eb5ea6c8ddfb9beab6830a0
aarch64_generic-PR72-e909e23-packages
64.5 MB
sha256:552473c00c9b0eb45d3c1a3fa103c61ee37015e1a49a32e783b86198ec337ff7
arm_cortex-a15_neon-vfpv4-PR72-e909e23-logs
1.72 MB
sha256:9c5d12c536516f3ee889f4549f31d7e90b7eaf37e02e8f3e745bf721a8667860
arm_cortex-a15_neon-vfpv4-PR72-e909e23-packages
59.7 MB
sha256:884c051a4f345c95bf9769d82a62c1eaaba551498d9eaa7effe8bd87b009dec8
arm_cortex-a9_vfpv3-d16-PR72-e909e23-logs
1.71 MB
sha256:abb6002dabc2fdce6d7a2a02ee77c992bd4764da09ca591fa02e098596c5a970
arm_cortex-a9_vfpv3-d16-PR72-e909e23-packages
59.9 MB
sha256:4e47bfc00ada829f39de2063a4e10cdb627ca55b348d69153820d7a54947b4f1
i386_pentium-mmx-PR72-e909e23-logs
1.3 MB
sha256:4666c09943ad72049dfabadd0bb8f66ffdac8e9afcb17f9070df915751287edc
i386_pentium-mmx-PR72-e909e23-packages
68.4 MB
sha256:1d8669b9ecaa97911a4706570fa9985689e6d65b9fc4346a81ad3a27b63223eb
mips_24kc-PR72-e909e23-logs
1.14 MB
sha256:bc3ae59742887a8d434ce5a5357d4d1b05e203fa684dd153a841102e4f662c59
mips_24kc-PR72-e909e23-packages
62.4 MB
sha256:ed0433f037c51d39642f0da012bc9748a8ace332d6f64ffb12c6fe133c964d85
mipsel_24kc-PR72-e909e23-logs
1.21 MB
sha256:1608ff8ed32579fcf70c7b1c0e1c5d7666d911692907c584192ec34b3d6dae64
mipsel_24kc-PR72-e909e23-packages
61 MB
sha256:6195357e0622395f2881f938abfa5dc6fdbc516bf94c4da5c47100ae62e80809
powerpc_464fp-PR72-e909e23-logs
953 KB
sha256:0741bb7ecafe84ebb8686c82466d1d7bdfee1b138dba957fec98ec3423acc831
powerpc_464fp-PR72-e909e23-packages
336 KB
sha256:46e823603841830a4eeaa139711d135185a5fefa5d47d3aa8a90403627f68158
powerpc_8548-PR72-e909e23-logs
950 KB
sha256:5d5714d24d1a868cd6eb2dd141f2aa7586af3446d9bed926c1b4e4b6e94a05f5
powerpc_8548-PR72-e909e23-packages
336 KB
sha256:f80278174933fe574f1c23815294aea942af7443a11f3feffbf81bd4c8cafcfe
riscv64_generic-PR72-e909e23-logs
1.26 MB
sha256:0cf33011dd1f95e3df5feb0745d1902b8583f5b1127900f6d83656cedd5b09ae
riscv64_generic-PR72-e909e23-packages
66.6 MB
sha256:481e5ff2efc4eac403eb01347e5d5c185037781c5e66d056b1b307b957f16f5a
x86_64-PR72-e909e23-logs
1.3 MB
sha256:93e21f248842fb8e0ab77787383867dd6e2157e8513d60d6145616487c4e6f45
x86_64-PR72-e909e23-packages
66 MB
sha256:6040576cae230b7ce4b15bc24da4230e97a94d5e42db5315f10f3299007bfc8d