-
Notifications
You must be signed in to change notification settings - Fork 241
test(profile): Pin the truncation lookahead boundary #660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nit] This one is mostly redundant — worth re-pointing its docstring at what it uniquely holds.
The docstring says dropping the
+ 1"would silently stop reporting truncation," which is the justification I gave you and which turns out to be inaccurate:test_schema_iterator_consumes_only_remaining_plus_one, ~60 lines above in this same class, already fails on that mutation viaassert consumed == remaining_after_key_findings + 1. So doestest_schema_prefix_is_stable_across_hash_seeds.I'd still keep the test — it asserts the observable contract (marker present, exactly once, last, error severity) where the older one asserts iterator mechanics, and those are worth pinning separately. But as written, someone auditing coverage later will read this docstring, believe it is the sole guard on the
+ 1, and may delete the older test as duplicative — which would drop theconsumedassertion, the only check that the tail isn't drained.Something like:
No change needed to the assertions themselves; they're right.
For contrast,
test_exactly_filling_the_budget_emits_no_markerabove genuinely stands alone — I confirmed>→>=survives all 63 tests onmainand is caught only by it. That one's docstring is accurate as written.