AC6 SDS-Examples build test #16
ReinhardKeilAnnotations
16 errors and 28 warnings
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, DebugPlay, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, ReleaseRec, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, DebugRec, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, DebugRec, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, ReleasePlay, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, ReleaseRec, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, DebugPlay, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, DebugPlay, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, ReleaseRec, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, DebugRec, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, DebugRec, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, ReleasePlay, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, ReleasePlay, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, ReleasePlay, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, ReleaseRec, AppKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/AppKit'. No such file or directory
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, DebugPlay, DevKit)
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/SDS-Examples/SDS-Examples/./Alif/DevKit'. No such file or directory
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, DebugPlay, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, ReleaseRec, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, DebugRec, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, DebugRec, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, ReleasePlay, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, ReleaseRec, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, DebugPlay, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, DebugPlay, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, ReleaseRec, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AE722F80F55D5LS, DebugRec, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, DebugRec, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, ReleasePlay, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AVH-SSE-300, ReleasePlay, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, ReleasePlay, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/AppKit, AppKit, SDS, AVH-SSE-300, ReleaseRec, AppKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./Alif/DevKit, DevKit, SDS, AE722F80F55D5LS, DebugPlay, DevKit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, AVH-SSE-300, ReleasePlay, B-U...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, STM32U585AIIx, DebugPlay,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, AVH-SSE-300, DebugPlay, B...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, AVH-SSE-300, DebugPlay, B-U585I)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, STM32U585AIIx, ReleasePla...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, AVH-SSE-300, ReleasePlay,...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, STM32U585AIIx, DebugPlay, B-U...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, STM32U585AIIx, DebugRec, B-U5...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, STM32U585AIIx, DebugRec, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, STM32U585AIIx, ReleaseRec, B-...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/KeywordSpotting, KeywordSpotting, SDS, STM32U585AIIx, ReleasePlay, B...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
CI (AC6, ./ST/B-U585I-IOT02A/MotionRecognition, MotionRecognition, SDS, STM32U585AIIx, ReleaseRec...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 | |
|---|---|---|---|
|
AC6_build_KeywordSpotting_SDS.DebugPlay+AVH-SSE-300.B-U585I
Expired
|
1.37 MB |
sha256:f61fc240063514fc6fbc60f13ffa4d6622b44ce9b38d8ba2707e3d4b6d00a526
|
|
|
AC6_build_KeywordSpotting_SDS.DebugPlay+STM32U585AIIx.B-U585I
Expired
|
2.18 MB |
sha256:138496442d0097f9f27dcf09aef68dfad00e7e9efc5530ce9c22156e7f5759b5
|
|
|
AC6_build_KeywordSpotting_SDS.DebugRec+STM32U585AIIx.B-U585I
Expired
|
2.2 MB |
sha256:dfed4e16c9498043dd219c10e00648bb079a1bc8cf29cefeab32430923a55a4c
|
|
|
AC6_build_KeywordSpotting_SDS.ReleasePlay+AVH-SSE-300.B-U585I
Expired
|
1.44 MB |
sha256:9b87aea4c187f2222832b3f16f9f867d58c3da3812af889d01775c9ac8d6c1db
|
|
|
AC6_build_KeywordSpotting_SDS.ReleasePlay+STM32U585AIIx.B-U585I
Expired
|
2.34 MB |
sha256:fd85d48befe9ed5a1e8ca80e52088d43ca9114a3c9bcaf3f26d7ff309f1c3bac
|
|
|
AC6_build_KeywordSpotting_SDS.ReleaseRec+STM32U585AIIx.B-U585I
Expired
|
2.37 MB |
sha256:03601e61e00de50c448ff44c1e35a28022045a432d617da12d9b2aa1e829abbb
|
|
|
AC6_build_MotionRecognition_SDS.DebugPlay+AVH-SSE-300.B-U585I
Expired
|
1.12 MB |
sha256:15368beec2f4c30608a62afe6d4f55b435c1bf14f9fcfb063e3bee6550f8d22c
|
|
|
AC6_build_MotionRecognition_SDS.DebugPlay+STM32U585AIIx.B-U585I
Expired
|
2.05 MB |
sha256:187f17309c1c614d0aa0cd40057e91d0d0771c0f73fd1d3560a5595e98b5a2f7
|
|
|
AC6_build_MotionRecognition_SDS.DebugRec+STM32U585AIIx.B-U585I
Expired
|
2.16 MB |
sha256:8a86a8c0c53d5e07237e55b845d8f95fedde7162633a001135dacb1e65eae69d
|
|
|
AC6_build_MotionRecognition_SDS.ReleasePlay+AVH-SSE-300.B-U585I
Expired
|
1.2 MB |
sha256:58c3b01af45a50a628917a1fe98d6dc3bf4440cd00be175d2fc2e3b0f14ce5ef
|
|
|
AC6_build_MotionRecognition_SDS.ReleasePlay+STM32U585AIIx.B-U585I
Expired
|
2.16 MB |
sha256:76c54d9bb7e66d71e6a4a0f27e76af6a0e9f93f3a55adedc9c898b6327f45185
|
|
|
AC6_build_MotionRecognition_SDS.ReleaseRec+STM32U585AIIx.B-U585I
Expired
|
2.26 MB |
sha256:ca7c07d599733a325056e45326645f79f4e105a251e3dada2cb149fa2ec7f4bc
|
|