[sexenteen]

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

Follow-up to #11963, as suggested there: utest_run can already repeat a test case
(utest_run testcaseA 10), but the automatic run used by CI always runs the cases exactly once,
so a test case that leaks memory or threads still passes.

This adds a loop count to the automatic run and prints the memory/thread state after every loop,
so the CI log shows whether used memory or the thread list grows from one loop to the next.

你的解决方案是什么 (what is your solution)

1. components/utilities/Kconfig: new option RT_UTEST_AUTO_RUN_LOOP (int, 1..100, default 1,
   depends on RT_UTEST_USING_AUTO_RUN), so the default behaviour is unchanged.
2. components/utilities/utest/utest.c:
   • utest_auto_run() uses the option as tc_loop (still 1 when it is not set);
   • after each loop it prints loop x/N runtime info and executes free and ps
     (rt_memory_info() is printed when finsh is not enabled).
3. .github/workflows/utest_auto_run.yml:
   • new workflow_dispatch input utest_loop (default 1);
   • the build step appends CONFIG_RT_UTEST_AUTO_RUN_LOOP=<n> when the input is greater than 1;
   • the log-monitor timeout scales with the loop count (loop * 20 minutes) so a multi-loop run
     does not hit the previous fixed 20 minute limit.

Only 3 files are touched (+65/-1), and nothing changes unless the loop count is set.

请提供验证的bsp和config (provide the config and bsp)

• BSP: bsp/qemu-vexpress-a9
• .config: CONFIG_RT_USING_CI_ACTION=y, CONFIG_RT_USING_UTESTCASES=y,
  CONFIG_RT_UTEST_SELF_PASS=y, CONFIG_RT_UTEST_MAILBOX=y, CONFIG_RT_UTEST_AUTO_RUN_LOOP=3
  (temporarily for the verification; not part of this PR)
• action: https://github.com/sexenteen/rt-thread/actions/runs/41670048498

Verification, booting the image and letting the automatic run go through three loops:

[I/utest] [==========] [ utest    ] loop 1/3
...
[I/utest] [  PASSED  ] [ result   ] 2 tests.
[I/utest] [==========] [ utest    ] finished
[I/utest] [==========] [ utest    ] loop 1/3 runtime info
total    : 66332784
used     : 42888
maximum  : 47632
available: 66289896
thread           pri  status      sp     stack size max used ...
tshell            20  suspend ...
utest             20  running ...
[I/utest] [==========] [ utest    ] loop 2/3
...
[I/utest] [==========] [ utest    ] loop 2/3 runtime info
used     : 42888
...
[I/utest] [==========] [ utest    ] loop 3/3 runtime info
used     : 42888

used stays at 42888 across the three loops, i.e. the mailbox test case does not leak here, and
the thread list is identical after every loop.

Not covered: only qemu-vexpress-a9 was exercised locally, and the workflow change itself is
verified by the utest_auto_run job of this PR.
]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用clang-format 源码格式化工具确保格式符合RT-Thread代码规范 This PR has been formatted with clang-format and complies with RT-Thread code specification
• 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

[github-actions]

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

---

🛠 操作步骤 | Steps

1. 前往 Actions 页面 | Go to the Actions page
   点击进入工作流 → | Click to open workflow →

2. 点击 Run workflow | Click Run workflow

• Use workflow from 保持默认分支（通常为 master）
  Keep the default branch (usually master) in Use workflow from
• 在 branch 输入框填写 PR 分支 feat/utest-auto-run-loop
  Enter PR branch feat/utest-auto-run-loop in the branch field
• 设置需排除的文件/目录（目录请以"/"结尾）
  Set files/directories to exclude (directories should end with "/")

3. 等待工作流完成 | Wait for the workflow to complete
   格式化后的代码将作为独立提交推送至你的分支。
   The formatting changes will be pushed to your branch as a separate commit.

完成后，提交将自动更新至 feat/utest-auto-run-loop 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the feat/utest-auto-run-loop branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

[github-actions]

📌 Code Review Assignment

🏷️ Tag: components

Reviewers: @Maihuanyi

Changed Files (Click to expand)

• components/utilities/Kconfig
• components/utilities/utest/utest.c

🏷️ Tag: workflow

Reviewers: @Rbb666 @kurisaW @supperthomas

Changed Files (Click to expand)

• .github/workflows/utest_auto_run.yml

---

📊 Current Review Status (Last Updated: 2026-11-04 00:02 CST)

• ⌛ @Maihuanyi Pending Review
• ⌛ @Rbb666 Pending Review
• ⌛ @kurisaW Pending Review
• ⌛ @supperthomas Pending Review

---

📝 Review Instructions

1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
   Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

2. 确认审核通过后评论 LGTM/lgtm
   Comment LGTM/lgtm after confirming approval

3. PR合并前需至少一位维护者确认
   PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

[github-actions]

MemBrowse Memory Report · Explore what changed →

No memory changes detected for:

• at32f415-start
• esp32-c3
• gd32105r-start
• hc32f334
• hpmicro-hpm5100evk
• hpmicro-hpm5301evklite
• infineon-psoc6
• k230
• loongson-ls1cdev
• nordic-nrf51822
• nuvoton-m487
• nxp-lpc1114
• qemu-virt64-aarch64
• raspberry-pico-rp2040
• renesas-ra2l1
• simulator
• stm32f407-rt-spark
• stm32l475-atk-pandora-llvm
• wch-ch32v208w-r0
• x86
• xuantie-e901plus

---

_{Catch memory regressions in CI with MemBrowse. Free for open source.}