259 write tests to validate reliability features eg simulated network failures retries e3 #284
+181
−10
Conversation
This file contains 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
…y if the CI is successful
…y if the CI is successful
…y if the CI is successful
…y if the CI is successful
…y if the CI is successful
…e-reliability-features-eg-simulated-network-failures-retries-e3
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.
In
CI.yml:. Added a separate
reliability-testsjob to isolate tests for retry logic and acknowledgment.. Used the
--filter reliabilityflag in thecargo nextest runcommand to run only the reliability-related tests.. Cached the
target/cargo-nextestdirectory to speed up future runs.In
CD.yml:. Added a trigger (
on.workflow_run) to ensure deployment only happens after theCIworkflow completes successfully.. Added an
ifcondition to proceed with deployment only if theCIworkflow's conclusion issuccess.