| Age | Commit message (Collapse) | Author |
|
This change fixes intermittent failures of the `core.smp_bind_affinity`
utest across SMP CI targets. The original failure was a flaky assertion on
unbound threads (`thread_inc[x] != thread_tic[x]` in thread_entry), not
incorrect bind_cpu behavior. CI logs already showed T0 binding worked
(thread_inc[0] == thread_tic[0] == 100) while the not_equal check failed.
The root issue is that unbound-thread CPU placement is platform-dependent
and outside the bind_cpu contract. On dual-core RISC-V/ARMv7 CI, an
unbound thread may legitimately run all iterations on core 0 while T0
delays on the same core, so any assertion requiring cross-core migration
(thread_inc != thread_tic, or core_mask with multiple bits) remains flaky.
This patch narrows the test to what bind_affinity actually verifies: T0
bound to core 0 must always execute on core 0. Unbound threads only add
scheduling pressure; their core_mask is printed for observation but not
asserted.
Changes:
- Sample `rt_hw_cpu_id()` and update counters under `rt_sched_lock` to
avoid migration skew between counting and CPU sampling.
- Track `thread_core_mask` for diagnostics; assert only T0 binding via
`thread_inc[0] == thread_tic[0]` and `thread_core_mask[0] == 1`.
- Remove flaky unbound-thread assertions (`thread_inc != thread_tic` and
multi-core core_mask checks).
- Move T0 assertions to the main test thread after all workers finish.
- Use atomic `finsh_flag`; reset counters and `threads[]` in `utest_tc_init`.
- Spin in worker loops after `run_num` until cleanup deletes them (do not
return from thread_entry or use `RT_WAITING_FOREVER` with `rt_thread_delay`).
- Guard `rt_thread_delete` in cleanup with non-NULL checks.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
* utest/msh: supports autocomplete of utest cases for utest_run
* docs/utest: explanation of adding the automatic completion function for utest_run
* fix[utest]: Improvement of annotation description
* remove outdated code
|
|
Many modules' utests currently don't support enabling all
tests at once. Furthermore, some modules' tests are complex,
for example due to their numerous dependencies on other
modules. This makes it nearly impossible to enable all
tests with a single global switch. Consequently, the
previously defined `RT_UTEST_USING_ALL_CASES` has lost
its original meaning.
We recommend deprecating this configuration switch. If a
module needs to enable a group of functional tests through
its own configuration, this local enable all switch should
be implemented by the module itself, and a global RTT enable
switch will no longer be provided.
If such a requirement arises in the future, we recommend
careful design, especially considering how to ensure that
turning on a single switch enables all dependencies for
all involved modules for ease of use.
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
RT_USING_CI_ACTION will select RT_UTEST_USING_AUTO_RUN and RT_UTEST_USING_ALL_CASES
|
|
|
|
|
|
Signed-off-by: Shell <[email protected]>
|
|
We support OFW API to replace fdt old API, and add
IRQ, IO, Platform-Bus, CPUs ... OFW node contorl.
To support work with Device Tree or ACPI in drivers
that use IRQ, we make a programmable interrupt
controller driver's model.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
* Add ADT Kconfig and fix MMU kconfig issue in Cortex-A
* [BSP] enable ADT
|
|
|
|
|
|
|
|
Signed-off-by: WillianChan <[email protected]>
|
|
[ymodem] 修改YMODEM_USING_FILE_TRANSFER功能的开启条件
|
|
目前开启的逻辑存在问题,ymodem的文件传输功能开启的前提是得有完整的文件系统,
但是目前,这个开启逻辑错了。
用户选择YMODEM_USING_FILE_TRANSFER功能后select DFS没有任何意义,因为除了需要依赖DFS之外还要依赖其他的例如FATFS,需要和SDIO适配等等等
正确的做法应该是用户配置好完整的文件系统后,ymodem文件传输才能有机会开启,
因此是depends on DFS 而非select DFS
更改之后,只要用户开启了文件系统,在选定YMODEM时,会自动开启文件传输功能,这也是用户希望看到的,直接一键搞定,不需要再多点一步
|
|
|
|
|
|
Use "ry" to receive files and use "sy file_path" to
send files. Default console uart and you can choose
any other uart if you want.
Signed-off-by: Steven Liu <[email protected]>
|
|
|
|
|
|
|
|
Signed-off-by: MurphyZhao <[email protected]>
|
|
[components/utilities] [utest] 增加 testcase 运行超时时间参数
Signed-off-by: MurphyZhao <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|