luchianmihai/walnux
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
walnux/tools/ci/testlist/arm-09.dat

64 lines
1.3 KiB
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/nucleo-f33*,CONFIG_ARM_TOOLCHAIN_CLANG
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/nucleo-f4*,CONFIG_ARM_TOOLCHAIN_CLANG
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/nucleo-g*,CONFIG_ARM_TOOLCHAIN_CLANG
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/nucleo-l*,CONFIG_ARM_TOOLCHAIN_CLANG
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/olimex-*,CONFIG_ARM_TOOLCHAIN_GNU_EABI
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
# Boards build by CMake
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
CMake,nucleo-f334r8:adc
CMake,nucleo-f334r8:highpri
CMake,nucleo-f334r8:nsh
CMake,nucleo-f334r8:spwm1
CMake,nucleo-f334r8:spwm2
CMake,nucleo-f410rb:nsh
CMake,nucleo-f412zg:nsh
CMake,nucleo-f429zi:netnsh
CMake,nucleo-f429zi:nsh
CMake,nucleo-f446re:adc
# CMake,nucleo-f446re:can
CMake,nucleo-f446re:cansock
CMake,nucleo-f446re:dac
CMake,nucleo-f446re:gpio
CMake,nucleo-f446re:ihm08m1_b16
CMake,nucleo-f446re:ihm08m1_f32
# CMake,nucleo-f446re:lcd
CMake,nucleo-f446re:nsh
CMake,nucleo-f446re:pwm
CMake,nucleo-f446re:qenco
CMake,nucleo-f446re:systemview
boards/stm32: split nucleo-f4x1re into separate boards Split nucleo-f4x1re into nucleo-f401re and nucleo-f411re. These are separate boards and should be in separate directories as it's done for all other nucleo boards in NuttX
2024-11-19 09:41:08 +01:00
CMake,nucleo-f401re:fb
CMake,nucleo-f401re:nsh
CMake,nucleo-f411re:mcp2515-extid
CMake,nucleo-f411re:nsh
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
CMake,nucleo-g431kb:comp
CMake,nucleo-g431kb:nsh
CMake,nucleo-g431kb:pwm
CMake,nucleo-g431rb:adc
# CMake,nucleo-g431rb:can
CMake,nucleo-g431rb:cansock
CMake,nucleo-g431rb:cordic
CMake,nucleo-g431rb:ihm16m1_b16
CMake,nucleo-g431rb:ihm16m1_f32
CMake,nucleo-g431rb:nsh
CMake,nucleo-g431rb:pwm
CMake,nucleo-g431rb:qenco
CMake,nucleo-g474re:nsh
# CMake,nucleo-g474re:usbserial
# CMake,nucleo-l152re:lcd
CMake,nucleo-l152re:nsh
Reference in a new issue Copy permalink