Repository navigation
Update integration tests and retain reproducible performance evidence - #15
Merged
Merged
Conversation
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.
Integration fixtures used removed server settings and metrics, while benchmark artifacts could lose their connection to the measured source and binary. Update fixtures for the current public SDK/protocol, verify bounded result streaming and drained accounting, and retain frozen source, commands and owned-fixture evidence. Bind every report to its actual binary, source and dependency pins, reject changed binaries and incomplete physical counters, and pin the server to the optimized Weir commit. Search measurements default to 20-second warmup and measurement; server batching remains 32 records.
Validated with race tests, default and integration-tagged vet, offline dependency checks, 19 Python tests in normal and optimized modes, and full MongoDB/Elasticsearch integration against the measured server source. Historical summaries reproduce the original throughput and latency values, retain negative results, and distinguish database drift. Independent reviews cover the server integration contracts and benchmark evidence validation.