ci(github): harden Verify CLI run in workflow test.yml#14
Merged
Conversation
Step no longer depends on exact model output. It now runs the CLI once under `timeout 90s`, prints the response, requires non-empty stdout, and fails if the CLI emitted its `Error:` prefix.
remarkablemark
changed the title
Verify CLI run in workflow test.yml
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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
1 participant
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.
What is the motivation for this pull request?
Harden the integration workflow so
Verify CLI runstops failing on nondeterministic model output.What is the current behavior?
The workflow asks the model to repeat an exact token and fails unless the generated response contains that exact string. This makes the CLI run check flaky even when the installed CLI can successfully talk to Ollama.
What is the new behavior?
The workflow now performs a single timed liveness check for
code-ollama run, prints the response, requires non-empty output, and fails only if the CLI emits itsError:prefix.Checklist: