config: explain missing forecast jobs#3119
Draft
nuclearcat wants to merge 1 commit into
Draft
Conversation
Add a targeted forecast explanation mode that can answer why an expected job was not scheduled for a tree, branch, platform, or runtime. The debug path builds a forecast graph, evaluates scheduler/job/platform/runtime rules, and reports blocked inputs in reverse from the target node. Use simulated kbuild node data when evaluating downstream tests so rules depending on build parameters, such as LTP rejecting kselftest fragments, are represented in forecast output. Add regression coverage for the LTP syscalls missing-job case. Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
a775d08 to
32da1a3
Compare
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.
Add a targeted forecast explanation mode that can answer why an expected job was not scheduled for a tree, branch, platform, or runtime. The debug path builds a forecast graph, evaluates scheduler/job/platform/runtime rules, and reports blocked inputs in reverse from the target node.
Use simulated kbuild node data when evaluating downstream tests so rules depending on build parameters, such as LTP rejecting kselftest fragments, are represented in forecast output. Add regression coverage for the LTP syscalls missing-job case.