fix/highlight log errors - #2082
Open
alanpeixinho wants to merge 4 commits into
Open
alanpeixinho wants to merge 4 commits into
alanpeixinho wants to merge 4 commits into
Conversation
* Match fail with word boundary to exclude pipefail * Skip error_mode and _0_errors in LAVA test names * Skip kselftest # Totals: header lines * Extend highlight tests for filtered cases Signed-off-by: Alan Peixinho <alan.peixinho@profusion.mobi>
* Rename chips to Suspected fail, Suspected error, Other matches * Add tooltip that heuristic counts may not match test status * Update locale strings Signed-off-by: Alan Peixinho <alan.peixinho@profusion.mobi>
Comment on lines
+170
to
+172
| newCode = newCode.replace(/^.*(error|\bfail).*$/gim, match => { | ||
| if (/^\s*# Totals:/i.test(match)) { | ||
| return match; |
Member
There was a problem hiding this comment.
I don't get this. What I see in database is:
# # Totals: pass:1 fail:0 ...
and
[timestamp] # Totals: ...
I don't see what this line wants to match
Contributor
Author
There was a problem hiding this comment.
Nice catch. This was incorrect, and to be fair, might not be worth including.
Contributor
Author
There was a problem hiding this comment.
I am keeping only the error_mode and _0_errors false positives here.
Signed-off-by: Alan Peixinho <alan.peixinho@profusion.mobi>
Member
|
not sure if we should highlight this line: and maybe we should also try to make clear what the blue logs mean. I think they are the "Other matches", but if this is the case we should use the same color on counter badge below 
|
* Strip `fail:0` / `error:0` in the existing noise-removal step * Remove "Other matches" chip; only highlight suspected fail/error * Leave ambiguous keyword lines unhighlighted * Derive `highlightCount` from `fails + errors` * Extend tests for kselftest totals, xfail, and interleaved lines Closes kernelci#2065 Closes kernelci#2066
Contributor
Author
|
Updated to remove the "other matches" section. |
felipebergamin
approved these changes
Sep 16, 2026
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
2 participants
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.
fix(log-viewer): reduce highlight false positives and clarify counts (#2065, #2066)
Closes #2065
Closes #2066
What it is
failwith word boundary (\bfail) — fixespipefailfalse positives (Log viewer: exclude "pipefail" from the highlight heuristic #2065)error_modeand_0_errorsLAVA test names before highlighting (Log viewer: exclude "pipefail" from the highlight heuristic #2065)30-day DB analysis (36k test excerpts):
error_mode_0_errorsHow to Test
error_modeor_0_errorsin log — no highlight counts# Totals:lines still highlight when they report real failures