This is an automated email from the ASF dual-hosted git repository. acassis pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit b3f84ad6b9666180d5623ec00ba4d65733746b9a Author: Marco Casaroli <[email protected]> AuthorDate: Sat Oct 17 20:24:49 2026 +0200 Documentation/ostest: Correct the round-robin test defaults. The round-robin test of ostest uses a range of 30000 and 10 runs by default again. The ostest page still gave the old range default of 10000, and gave no default for the number of runs. Give both defaults, and say when a shorter round-robin test fails. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli <[email protected]> --- Documentation/applications/testing/ostest/index.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/Documentation/applications/testing/ostest/index.rst b/Documentation/applications/testing/ostest/index.rst index 01244b8ca74..5476ffb454f 100644 --- a/Documentation/applications/testing/ostest/index.rst +++ b/Documentation/applications/testing/ostest/index.rst @@ -28,8 +28,14 @@ The behavior of the ``ostest`` can be modified with the following settings in th configurable range, doing that configurable number of times. This value specifies the end of search range and together with number of runs allows to configure the length of this test – it should last at least a few tens of - seconds. Allowed values ``[1; 32767]``, default ``10000``. + seconds. Allowed values ``[1; 32767]``, default ``30000``. - ``CONFIG_TESTING_OSTEST_RR_RUNS`` – During round-robin scheduling test two threads are created. Each of the threads searches for prime numbers in the - configurable range, doing that configurable number of times. + configurable range, doing that configurable number of times. This value + specifies the number of runs. Allowed values ``[1; 32767]``, default + ``10``. A slow board can set this value and + ``CONFIG_TESTING_OSTEST_RR_RANGE`` lower in its defconfig. The test fails + if one thread finishes the first ``CONFIG_TESTING_OSTEST_RR_RUNS`` runs + before the other thread finishes one, for example when all its runs fit + in one time slice (``CONFIG_RR_INTERVAL``).
