Repository navigation
fix(tests): replace the filebeat test archive with synthetic cases - #152
Merged
Merged
Conversation
Remove tests/fixtures/filebeat/filebeat-testdata.tar.gz and scripts/filebeat/fetch_testdata.py. The filebeat integration tests, the Kafka e2e test and the PGO workload now replay 31 lines in tests/fixtures/filebeat/cases.yaml (12 Umbrella, 8 IOS, 11 Meraki). Each case carries the fields its output must have. The e2e test pairs outputs to cases by a root _case field instead of by position. Cargo.toml drops flate2 and tar, which only the archive reader used. The PGO workload cycles 31 events where it cycled about 370 lines.
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 filebeat tests use lines written for this repo.
_casefield.On desktop-derek:
hyperi-ci check --quickpasses.Under plain
cargo test,pipeline_memory::test_pipeline_refuses_a_messagepack_recordfails on a metric count (1160, expected 2) even when only thepipeline_memorytests run.