Closed Bug 1819906 Opened 1 year ago Closed 1 year ago

adjust treeherder rule for non-fatal errors to account for timestamps

Categories

(Tree Management :: Treeherder, task)

Product:
Tree Management
Component:
Treeherder
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: aryx, Assigned: aryx)

References

Details

Context:
update-verify tasks like this one can have these lines in the log:

[task 2023-02-28T22:06:01.418Z] 2023-02-28 22:06:01+0000: non-fatal error removing directory: icons/, rv: 0, err: 39

Treeherder picks them up as error lines because it only looks for non-fatal error at the start of the sanitized line which has [task 2023-02-28T22:06:01.418Z] removed.

Could/should the update-verify tasks drop the additional timestamps or should Treeherder adjust its filtering to search for the text at any position in the log line?

Flags: needinfo?(jcristau)

The timestamps were added in bug 1775522 a few months ago.

Blocks: 1775522
Assignee: nobody → aryx.bugmail
Status: NEW → ASSIGNED
Component: Release Automation: Updates → Treeherder
Flags: needinfo?(jcristau)
Product: Release Engineering → Tree Management
QA Contact: gbrown
Summary: remove timestamps from logs of update-verify tasks or adjust treeherder rule for non-fatal errors → adjust treeherder rule for non-fatal errors to account for timestamps
Version: unspecified → ---
You need to log in before you can comment on or make changes to this bug.