test: strengthen Jieli adapter follow-up coverage - #725
Open
maidang-xing wants to merge 4 commits into
Open
maidang-xing wants to merge 4 commits into
maidang-xing wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR 描述/PR description
Extend the Jieli CI workflow for
xb/tuyaopen-jlby preparing the pinned JIELI platform checkout and running the focused platform tests. Tighten build, config, flash-bridge, and UART hello regression coverage; update the AC791/AC792 guide to distinguish historical evidence from outstanding hardware acceptance; remove unrelated AI memory options from the switch_demo default config.Validation:
.venv\Scripts\python.exe -m unittest discover -s tests/platform -t . -p 'test_jieli_*.py'— 48 tests passed;git diff --checkpassed. GitHub runner execution is not yet verified. No real Jieli build or physical-board validation was performed for this PR.代码质量/Code Quality:
在本次拉取请求中,我已考虑以下事项 As part of this pull request, I've considered the following: