Aksal/nuttx
3
1
Fork 1
mirror of https://github.com/apache/nuttx.git synced 2026-08-08 22:17:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
nuttx/tools/ci/testlist/arm-12.dat

12 lines
321 B
Text
Raw Normal View History

CI: Split the Build Job arm-05 into multiple smaller jobs CI Build Job `arm-05` (runtime 2 hours) has become the Performance Bottleneck for CI Workflow. That's because `arm-05` builds too many targets for nRF, RP2040, SAM 3, SAM A and SAM D. This PR splits `arm-05` into multiple smaller jobs, to reduce the CI Build Duration. Before the PR: `arm-05` is overloaded, build requires 2 hours - `arm-05` (2 hours): nRF, RP2040, SAM 3, SAM A, SAM D - `arm-06` (56 mins): STM32 [a-m]* After the PR: `arm-05` is offloaded (to `arm-06` and `arm-07`), completes within 1 hour - `arm-05` (47 mins): nRF - `arm-06` (1 hour): Reserve for RP2040 exclusively - `arm-07` (1 hour 15 mins): SAM 3, SAM A, SAM D, STM32 [a-m]* Build Jobs are sorted by Target Name. So we cascade the changes and rename the Build Jobs: `arm-07` becomes `arm-08`, `arm-08` becomes `arm-09` etc. Then `arm-13` becomes a new job `arm-14`. (Which we added to `build.yml`) Performance of `arm-05` is discussed in https://github.com/apache/nuttx/issues/13775 and https://github.com/apache/nuttx/issues/12773
2024-10-09 09:37:07 +08:00
/arm/stm32/stm32f4discovery,CONFIG_ARM_TOOLCHAIN_GNU_EABI
-stm32f4discovery:winbuild
CI: Migrate ci tooling from testing repository to main os repo
2021-04-04 19:55:34 -07:00
CI: Split the Build Job arm-05 into multiple smaller jobs CI Build Job `arm-05` (runtime 2 hours) has become the Performance Bottleneck for CI Workflow. That's because `arm-05` builds too many targets for nRF, RP2040, SAM 3, SAM A and SAM D. This PR splits `arm-05` into multiple smaller jobs, to reduce the CI Build Duration. Before the PR: `arm-05` is overloaded, build requires 2 hours - `arm-05` (2 hours): nRF, RP2040, SAM 3, SAM A, SAM D - `arm-06` (56 mins): STM32 [a-m]* After the PR: `arm-05` is offloaded (to `arm-06` and `arm-07`), completes within 1 hour - `arm-05` (47 mins): nRF - `arm-06` (1 hour): Reserve for RP2040 exclusively - `arm-07` (1 hour 15 mins): SAM 3, SAM A, SAM D, STM32 [a-m]* Build Jobs are sorted by Target Name. So we cascade the changes and rename the Build Jobs: `arm-07` becomes `arm-08`, `arm-08` becomes `arm-09` etc. Then `arm-13` becomes a new job `arm-14`. (Which we added to `build.yml`) Performance of `arm-05` is discussed in https://github.com/apache/nuttx/issues/13775 and https://github.com/apache/nuttx/issues/12773
2024-10-09 09:37:07 +08:00
/arm/stm32/stm32ldiscovery,CONFIG_ARM_TOOLCHAIN_CLANG
tools/ci: migrate some ci build configurations to CMake
2023-07-18 21:40:45 +02:00
CI: Split the Build Job arm-05 into multiple smaller jobs CI Build Job `arm-05` (runtime 2 hours) has become the Performance Bottleneck for CI Workflow. That's because `arm-05` builds too many targets for nRF, RP2040, SAM 3, SAM A and SAM D. This PR splits `arm-05` into multiple smaller jobs, to reduce the CI Build Duration. Before the PR: `arm-05` is overloaded, build requires 2 hours - `arm-05` (2 hours): nRF, RP2040, SAM 3, SAM A, SAM D - `arm-06` (56 mins): STM32 [a-m]* After the PR: `arm-05` is offloaded (to `arm-06` and `arm-07`), completes within 1 hour - `arm-05` (47 mins): nRF - `arm-06` (1 hour): Reserve for RP2040 exclusively - `arm-07` (1 hour 15 mins): SAM 3, SAM A, SAM D, STM32 [a-m]* Build Jobs are sorted by Target Name. So we cascade the changes and rename the Build Jobs: `arm-07` becomes `arm-08`, `arm-08` becomes `arm-09` etc. Then `arm-13` becomes a new job `arm-14`. (Which we added to `build.yml`) Performance of `arm-05` is discussed in https://github.com/apache/nuttx/issues/13775 and https://github.com/apache/nuttx/issues/12773
2024-10-09 09:37:07 +08:00
/arm/stm32/stm32vldiscovery,CONFIG_ARM_TOOLCHAIN_CLANG
tools/ci: migrate some ci build configurations to CMake
2023-07-18 21:40:45 +02:00
CI: Split the Build Job arm-05 into multiple smaller jobs CI Build Job `arm-05` (runtime 2 hours) has become the Performance Bottleneck for CI Workflow. That's because `arm-05` builds too many targets for nRF, RP2040, SAM 3, SAM A and SAM D. This PR splits `arm-05` into multiple smaller jobs, to reduce the CI Build Duration. Before the PR: `arm-05` is overloaded, build requires 2 hours - `arm-05` (2 hours): nRF, RP2040, SAM 3, SAM A, SAM D - `arm-06` (56 mins): STM32 [a-m]* After the PR: `arm-05` is offloaded (to `arm-06` and `arm-07`), completes within 1 hour - `arm-05` (47 mins): nRF - `arm-06` (1 hour): Reserve for RP2040 exclusively - `arm-07` (1 hour 15 mins): SAM 3, SAM A, SAM D, STM32 [a-m]* Build Jobs are sorted by Target Name. So we cascade the changes and rename the Build Jobs: `arm-07` becomes `arm-08`, `arm-08` becomes `arm-09` etc. Then `arm-13` becomes a new job `arm-14`. (Which we added to `build.yml`) Performance of `arm-05` is discussed in https://github.com/apache/nuttx/issues/13775 and https://github.com/apache/nuttx/issues/12773
2024-10-09 09:37:07 +08:00
/arm/stm32/viewtool-stm32f107,CONFIG_ARM_TOOLCHAIN_CLANG
tools/ci/testlist: skip the build of <board>:cxxtest Problems downloading the uClibc++-0.2.5.tar.bz2 package cURL error 60: SSL certificate expired net::ERR_CERT_DATE_INVALID Subject: cxx.uclibc.org Issuer: R10 Expires on: 27 set 2025 This blocks the jobs: - arm-12 - sim-02 Signed-off-by: simbit18 <simbit18@gmail.com>
2025-09-28 14:43:08 +02:00
# cURL error 60 SSL certificate expired
-stm32f4discovery:cxxtest
Reference in a new issue Copy permalink