ci: cover CLI regressions in CPU NumPy checks - #3752
Merged
Merged
Conversation
Signed-off-by: LauraGPT <18321252+LauraGPT@users.noreply.github.com>
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.
Summary
Run the existing CLI regressions in both CPU NumPy compatibility lanes, and trigger that workflow when either
funasr/cli.pyortests/test_cli.pychanges.The gap became visible while reviewing #3750: the CLI tests exist and can catch user-facing output regressions, but no current workflow explicitly selects them or includes their source/test paths. This change reuses the existing Python 3.12, CPU PyTorch 2.10.0, NumPy 1.26.4/2.4.0 environments and artifact reporting.
tests/test_cli.pyalongside all existing suites, and name CLI coverage in the step label.Scope: one existing workflow only. No CLI implementation or test changes; this does not include or resolve #3750, change branch protection, or publish a release.
Validation
bash -n;git diff --checkpasses.Merged as
2ddbd3d9970af621f8bad796a3ab12939218a795. Merge parents and tree were verified against the signed tested headcfc8c47708cf093438bf097a5eab86ac90fcd60a; no runtime code or package release changed.CLI tests exercise the real command module with temporary files and existing model doubles. No model downloads, acoustic inference, GPU execution, or end-to-end recognition-quality claim.