Skip to content

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

feat(qt5): add qt5serialport and qt5serialbus packages

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

Triggered via pull request April 12, 2026 03:44
Status Failure
Total duration 14h 0m 21s
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-a15_neon-vfpv4
Process completed with exit code 2.
Feeds Package Test Build / Test x86_64
Process completed with exit code 2.
Feeds Package Test Build / Test aarch64_generic
Process completed with exit code 2.
Feeds Package Test Build / Test riscv64_generic
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 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 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-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 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 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 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/
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 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/

Artifacts

Produced during runtime
Name Size Digest
aarch64_generic-PR72-d4e10be-logs
1.87 MB
sha256:f3dc56867f5ca6da05e4e44fd129cd68b8e4e5188b504fe442418fab6df5e336
aarch64_generic-PR72-d4e10be-packages
284 MB
sha256:93544ad42adbaddc8aa0186773377edbf5a02cc8a7f2d48095ab702be125e5b2
arm_cortex-a15_neon-vfpv4-PR72-d4e10be-logs
2.29 MB
sha256:f270c0a1811ad18266b015ff26c7dfbdebbb8faa6a755fda68a4acc5e6b71809
arm_cortex-a15_neon-vfpv4-PR72-d4e10be-packages
256 MB
sha256:f39bf05ed79ae38e6ca1b7dc2b027ecf6a35567104afee521ce546450b2d3f51
arm_cortex-a9_vfpv3-d16-PR72-d4e10be-logs
2.28 MB
sha256:312e2727ba02e3e603cb4c046450447ae190e2bd0e58e76a1904457fc486aaf1
arm_cortex-a9_vfpv3-d16-PR72-d4e10be-packages
257 MB
sha256:e01c2d69889827eff57c8dd6071029d13b0a13f00c498f0dd9edb0aa41ab21b6
i386_pentium-mmx-PR72-d4e10be-logs
1.79 MB
sha256:ef50b55224308e14b7802d9694519dfd7d9e41fff2d106a24ccc6f04354e312a
i386_pentium-mmx-PR72-d4e10be-packages
237 MB
sha256:6de4d217c66b6442584dddc34ab0c8a874e7b3bcd2ecc2c444dd644ce9044a45
mips_24kc-PR72-d4e10be-logs
1.73 MB
sha256:f494f755219cd46fff0a9516f7070ba2534a100674e3eb5ab0ba78f182c12d25
mips_24kc-PR72-d4e10be-packages
208 MB
sha256:a850e0343b23a5d181676c34511fbea718de46a8e161a57c10c217cfa5f147c7
mipsel_24kc-PR72-d4e10be-logs
1.69 MB
sha256:ee7dff0cd136356134ce10e43426f6779f88c078b0acfe2c1986d3f4a42195f2
mipsel_24kc-PR72-d4e10be-packages
204 MB
sha256:129371c83314490d492abf1b76c95fc7810fb4699c9ef1fefe077971860b404f
powerpc_464fp-PR72-d4e10be-logs
1.33 MB
sha256:d2cd3026d197d997175fc15fcaebe98efde203eba08f26737b02c1fa37dd4f76
powerpc_464fp-PR72-d4e10be-packages
15.7 MB
sha256:3006bc6b74a852b9c8836c71e315e5d8c32b8dff5fe18ff5bc4780d9e8869a51
powerpc_8548-PR72-d4e10be-logs
1.33 MB
sha256:aa03cb8e51fa70590fadfee9bc6b0a94f74343e592154ffeeea228d37d0bc0cf
powerpc_8548-PR72-d4e10be-packages
15.8 MB
sha256:23fad6dd2909a8d7aae340dddcb16e80146b74a0dcf706b546a271582a39d6c6
riscv64_generic-PR72-d4e10be-logs
1.74 MB
sha256:4d983abcd0733862af66604bc1d8d312babc6d5a42623f1bf0733e36fe39382d
riscv64_generic-PR72-d4e10be-packages
226 MB
sha256:b23f591be8c73046e1c99ea6b9f869d06c16bbe58f926ffdcc91b1d34b0b0996
x86_64-PR72-d4e10be-logs
1.79 MB
sha256:40607a39f652c0dd1a146345c01186cf0fafad9b4883d8c945703442335e88d0
x86_64-PR72-d4e10be-packages
231 MB
sha256:56d4cb409281ed28a70d28658b00c773a378b5302c2b54308cf47fc42db633ef