Repository navigation
test: backend e2e key check (file survives, leak count) - #3
Merged
Merged
Conversation
…e matches grep exit 1 means no match, 0 a leak, anything else fails with grep's stderr in the message. Signed-off-by: Ditah Kumbong <ditah.kumbong@runzivo.dev>
…ch always fails Signed-off-by: Ditah Kumbong <ditah.kumbong@runzivo.dev>
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.
Part of Runzivo/rzv-platform#146
The shared run backend-201645 stopped at the /workspace key check: grep exited 2, which is an error and not a match. The check now (1) requires the provider key file to survive the stop and start, and (2) treats grep exit 1 as clean, 0 as a leak, and anything else as a failure, with grep's stderr shown. Test-only change.