DRAFT: kcidb-automatching #547
Draft
Conversation
This file contains 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
See kcidb-automatching/README.md Signed-off-by: Helen Koike <[email protected]>
helen-fornazier
had a problem deploying
to
staging
GitHub Actions
Failure
|
@helen-fornazier the gist link is this one (same minus the Any plans on how to apply this practically in a way that's not O(n)? IMO that should be the first problem to address. |
helen-fornazier
force-pushed
the
automatching
branch
2 times, most recently
from
70a7739
to
56986a8
Compare
Signed-off-by: Helen Koike <[email protected]>
helen-fornazier
force-pushed
the
automatching
branch
from
56986a8
to
41b7fd4
Compare
kcidb-ingest -d "sqlite:mykcidb.sqlite" < automatch-test.json | kcidb-ingest -d "sqlite:mykcidb.sqlite"
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.
kcidb-automatching is supposed to be a command line tool that kcidb can use to create incidents automatically when new nodes (tests or builds) arrive when the nodes matches with rules defined in issues.
We are discussed the schema on https://gist.github.com/helen-fornazier/0e9528d7d011e07f08c3a19f997ac5b0/edit
But since I want to exercise the entire process, for now I just used kcidb-io as a schema, assuming all string fields are regexes, and adding a
log_regexfield to match the content of log. This is supposed to be temporary, as I'd like to see how everything would glue together, than we can go back to the schema discussion, and we can also work on specific details to improve performance.See kcidb-automatching/README.md for more details.
My next step is: understand where in kcidb this would be integrated and how, so I can make the appropriate changes to kcidb-automatching.
cc @JenySadadia @spbnick @hardboprobot