JianyuWang0623 opened a new issue, #7:
URL: https://github.com/apache/nuttx-ntfc-testing/issues/7
## Summary
#6 (merged, commit d0f0710b23e90b69d6d718403681c928dbf743a3 on `main`)
dropped
the obsolete `CONFIG_INIT_ENTRYPOINT=nsh_main` hard requirement from
`ntfc.yaml`, so that configs whose init entry point is `init_main` (nxinit)
can also run the `Nuttx_System` NTFC suite.
However, `apache/nuttx`'s CI (`.github/workflows/build.yml`, `Linux (sim-01)`
job) clones this repo pinned to the `release-0.0.1` tag:
git clone -b release-0.0.1 https://github.com/apache/nuttx-ntfc-testing
&& break
`release-0.0.1` currently still points to
`6ec96fd91840f221e55f5652ceb78d7bdc0a01d3`,
which predates the #6 merge. As a result, apache/nuttx#19984 (switching
`sim:citest` to `init_main`/nxinit) still fails CI with:
OSError: Missing kconfig dependency: ['CONFIG_INIT_ENTRYPOINT',
'nsh_main']
## Request
Could a maintainer please cut a new tag/release `release-0.0.2` pointing at
the current `main` HEAD (`d0f0710b23e90b69d6d718403681c928dbf743a3`, which
includes #6)? Once published, a follow-up PR will update `apache/nuttx`'s
`build.yml` to reference `release-0.0.2` instead of `release-0.0.1`.
(Alternative: force-move the existing `release-0.0.1` tag to the new commit
instead of cutting a new one — either approach unblocks the downstream PR;
happy to go with whichever the maintainers prefer.)
--
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]
