kernelci: api: models: add new "process" node type #2948
+13
−0
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
Post-processing jobs are currently nodes of the `job` kind, which only works as long as they're related to `checkout` or `kbuild` nodes. However, due to performance issues of the `coverage-report` jobs, we need to post-process each coverage-enabled test job individually. This leads to scheduling issues, as we could enter an infinite loop where new post-processing jobs would be triggered whenever one of those transitions to the `done` state. We must therefore create a new node kind for post-processing jobs in order to avoid those scheduler limitations. Signed-off-by: Arnaud Ferraris <[email protected]>
|
Works fine on staging (example node) |
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.
Post-processing jobs are currently nodes of the
jobkind, which only works as long as they're related tocheckoutorkbuildnodes. However, due to performance issues of thecoverage-reportjobs, we need to post-process each coverage-enabled test job individually.This leads to scheduling issues, as we could enter an infinite loop where new post-processing jobs would be triggered whenever one of those transitions to the
donestate.We must therefore create a new node kind for post-processing jobs in order to avoid those scheduler limitations.