Swatantra-66 opened a new pull request, #3809: URL: https://github.com/apache/nuttx-apps/pull/3809
## Summary The round-robin scheduler test in `testing/ostest/roundrobin.c` executes two concurrent threads calculating prime numbers up to `CONFIG_TESTING_OSTEST_RR_RANGE` across `CONFIG_TESTING_OSTEST_RR_RUNS`. With the previous defaults of range 30,000 and 10 runs, each thread performed over 2.25 billion trial-division loop iterations. On resource-constrained microcontrollers (such as Cortex-M0/M3, Raspberry Pi Pico / RP2040, or AVR), this causes OSTest to stall on the `getprime` step for 5+ minutes. This PR: 1. Restores default `CONFIG_TESTING_OSTEST_RR_RANGE` from `30000` to `10000` (re-aligning with the file header note in `roundrobin.c` stating default values target ~30s on Cortex-M3 @ 24MHz, and matching the official documentation in `Documentation/applications/testing/ostest/index.rst`). 2. Reduces default `CONFIG_TESTING_OSTEST_RR_RUNS` from `10` to `4` (and updates the fallback `#define` in `roundrobin.c` accordingly). 4 runs across 2 threads still produce 8 recorded context-switch samples in `g_rr_values`, providing ample opportunity to detect round-robin interleaving while cutting execution time by over 90%. Fixes #3620 ## Impact - Significantly accelerates `ostest` execution on embedded targets and automated test runs. - Prevents 5-minute stalls during release qualification testing on boards like Raspberry Pi Pico. - No breaking change: targets requiring longer stress tests can still customize both options via Kconfig/defconfig. ## Testing - Verified `Kconfig` syntax and options range validation `[1; 32767]`. - Verified `roundrobin.c` fallback preprocessor definitions and compilation consistency. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
