tests: tag features collected from debug logs #15091
Draft
+266
−4
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.
This introduces the ability to collect and process logs during spread runs and extract features of interest.
It requires a version of spread that supports both project-level artifacts and the ability to use gzip instead of xz to download the data from core. The relevant PRs for spread are canonical/spread#212 and canonical/spread#213
The following tests are incompatible with the feature tagging and explained in the jira ticket:
Currently, the only "feature" available is a fake feature called "all" that will match all content of all lines. It will get removed in favor of real features.
As an example, here's the command to get the fake "all" feature for the
tests/main/ack
test:After running, the command, one would then find in the specified feature-artifacts folder:
Artifact retrieval for core requires an additional flag: