[CI] Add debug logging for premerge advisor explanations #690
+74
−4
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
Created using spr 1.3.7
boomanaiden154
added a commit
to boomanaiden154/llvm-zorg
that referenced
this pull request
Dec 27, 2025
We sometimes want to be able to debug how the premerge advisor makes explanations, especially in the case of false positive/negatives (although only the latter has been observed in the wild before). This proves hard because it is difficult to understand the system state at the moment the explanation request was made. This patch adds some logging so we can see all relevant information (namly the relevant failures stored by the premerge advisor in the DB). Pull Request: llvm#690
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.
We sometimes want to be able to debug how the premerge advisor makes
explanations, especially in the case of false positive/negatives
(although only the latter has been observed in the wild before). This
proves hard because it is difficult to understand the system state at
the moment the explanation request was made.
This patch adds some logging so we can see all relevant information
(namly the relevant failures stored by the premerge advisor in the DB).