Skip to content

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

feat(qt5): add qt5serialport and qt5serialbus packages

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

Triggered via pull request April 11, 2026 03:54
Status Failure
Total duration 16h 40m 49s
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 i386_pentium-mmx
Process completed with exit code 2.
Feeds Package Test Build / Test x86_64
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 mipsel_24kc
Process completed with exit code 2.
Feeds Package Test Build / Test aarch64_generic
Process completed with exit code 2.
Feeds Package Test Build / Test mips_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 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 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 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 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 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 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 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 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 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-5009a77-logs
1.87 MB
sha256:dfb800e71beedb27c51bb40857bd6c39c78a2b8967ba73b8d3cb3b1c3f2919c9
aarch64_generic-PR72-5009a77-packages
284 MB
sha256:cd6063cdaab323622e482a44cc1798a0883a89877e7054506a08dc89883ef9da
arm_cortex-a15_neon-vfpv4-PR72-5009a77-logs
2.28 MB
sha256:eaa6ee3e9cd72f23078fa574284136ace916c5c80950707d73e5e635eebf2335
arm_cortex-a15_neon-vfpv4-PR72-5009a77-packages
256 MB
sha256:bdd0343b8bf6776089a463002012ee574827d95fb082161868cc08413c28f211
arm_cortex-a9_vfpv3-d16-PR72-5009a77-logs
2.28 MB
sha256:60e0f396a162b04f1b513783645975da4bca6c98d19e3fa7c3c01d6884f8c1e3
arm_cortex-a9_vfpv3-d16-PR72-5009a77-packages
257 MB
sha256:672519fb39c107c76562b3864697e9d30c0affcda25c4202d71cabf055945222
i386_pentium-mmx-PR72-5009a77-logs
1.79 MB
sha256:dc87013e63e41ab88b5439798b830d0d86a0b105ed2d482c01eaacfc8bab880a
i386_pentium-mmx-PR72-5009a77-packages
237 MB
sha256:68ae021f01ba8792ee8fbcf5d58aad19fc108546c2eda6eae62e8c19b986e3d9
mips_24kc-PR72-5009a77-logs
1.74 MB
sha256:c4e31f72a67225f9902c1a23bc183b8c8b3bc239301cd9f32becda97a64c467f
mips_24kc-PR72-5009a77-packages
208 MB
sha256:2a0f9b1ff75ba0779f98dde778577694281ecb753285d8e182b70f9b2016054a
mipsel_24kc-PR72-5009a77-logs
1.75 MB
sha256:f931fb4ab50cf2c345ca2fe3048b80cbe904034f05115e3a1f8a58c0c7a7278f
mipsel_24kc-PR72-5009a77-packages
204 MB
sha256:56eb566577c262bb4b03a5dc232007b360b1af24b51a385b39673cfe57e102ef
powerpc_464fp-PR72-5009a77-logs
1.33 MB
sha256:cdf1dfea65e3afa2c883bc8d3500702acd533645eaae6a14c2dc5f0d57e7f8e3
powerpc_464fp-PR72-5009a77-packages
15.7 MB
sha256:f7df6684e8acb9250c1ec1639bb283ccc6208b6a432ace6aa152c4d80781bbcf
powerpc_8548-PR72-5009a77-logs
1.33 MB
sha256:c8e6ff3c94962c2bb426cfd16d460939c9bd1317703c41b0ddab190db2f1a47b
powerpc_8548-PR72-5009a77-packages
15.8 MB
sha256:3c849345e81227ca27abf3514a4f5fe5289596a5e9e5600bdc43541faca6cb78
riscv64_generic-PR72-5009a77-logs
1.7 MB
sha256:d1901bcf76669f8d3c9f21662f8d1455e54c72a521853eb3dce279433727fb7f
riscv64_generic-PR72-5009a77-packages
226 MB
sha256:4f36bfb13559b8fadb8c3d53d72f19bc8e5e6976cfb02199630c541785056298
x86_64-PR72-5009a77-logs
1.79 MB
sha256:7aeacff632de2e952d4f7c956284e61547578eb25c65fae366c1be10393d45a7
x86_64-PR72-5009a77-packages
231 MB
sha256:c9442a5942f0533af7cf3e65487e63f2760de40a62d7e948dec64506f8144d67