This is an automated email from the ASF dual-hosted git repository.
xiaoxiang781216 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/nuttx-ntfc-testing.git
The following commit(s) were added to refs/heads/main by this push:
new d0f0710 testing/system: drop CONFIG_INIT_ENTRYPOINT=nsh_main
requirement
d0f0710 is described below
commit d0f0710b23e90b69d6d718403681c928dbf743a3
Author: wangjianyu3 <[email protected]>
AuthorDate: Mon Aug 31 21:20:23 2026 +0800
testing/system: drop CONFIG_INIT_ENTRYPOINT=nsh_main requirement
The Nuttx_System NTFC suite only performs nsh command/output
comparisons and never inspects the init task name or PID, so
pinning CONFIG_INIT_ENTRYPOINT to nsh_main is an obsolete
constraint that blocks valid configs such as sim:citest
(CONFIG_INIT_ENTRYPOINT=init_main / nxinit). Remove it so the
suite runs under both nsh_main and init_main entry points, and
relax the README requirement accordingly.
Assisted-by: OpenCode:claude-opus-4.8
Signed-off-by: wangjianyu3 <[email protected]>
---
README.md | 3 ++-
ntfc.yaml | 1 -
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 0c7ee74..2c327b6 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,8 @@ NuttX image requirements for tests:
- ``CONFIG_DEBUG_SYMBOLS`` must be set.
-- NSH must be enabled and set as entry point
+- NSH must be enabled (``CONFIG_SYSTEM_NSH``); the init entry point may be
+ either ``nsh_main`` or ``init_main`` (nxinit)
- ``CONFIG_DEBUG_FEATURES=y`` and ``CONFIG_DEBUG_ASSERTIONS=y``
are recommended.
diff --git a/ntfc.yaml b/ntfc.yaml
index 9a49027..f1f521d 100644
--- a/ntfc.yaml
+++ b/ntfc.yaml
@@ -22,4 +22,3 @@ module: "Nuttx_System"
requirements:
- ["CONFIG_DEBUG_SYMBOLS", True]
- ["CONFIG_SYSTEM_NSH", True]
- - ["CONFIG_INIT_ENTRYPOINT", "nsh_main"]
