Repository navigation
test: isolate diary ring coverage from runtime observations - #539
Merged
Merged
Conversation
Signed-off-by: jbernavaprah <webjure@gmail.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.
The independent ring-bound test cleared the observation buffer owned by generated-runtime diary tests without taking their fixture lock.
A concurrent clear after reset's accepted invocation erased its recorded empty-ring observation and made the unchanged reset assertion report the fallback count of one.
Remove the unused shared-buffer clear from the local ring exercise.
Run that same exercise between the real generated owner's reset invocation and its observation assertion to protect this interference boundary deterministically.
Production diary behavior, bounds, reset semantics and suite scheduling remain unchanged.
Validation: