Closed
Bug 1419060
Opened 6 years ago
Closed 5 years ago
Document log output requirements for getting bug suggestions and test failures
Categories
(Tree Management :: Treeherder, enhancement, P3)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1506799
People
(Reporter: camd, Unassigned)
Details
This documentation would be helpful if test authors wanted their test failures to show in the test-based view. It's mostly about using structured logs. But a link from our docs to the mozlog structured logs docs would be a good start.
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → cdawson
Reporter | ||
Comment 1•6 years ago
|
||
http://mozbase.readthedocs.io/en/latest/mozlog.html
Reporter | ||
Updated•6 years ago
|
Priority: -- → P3
Reporter | ||
Updated•6 years ago
|
Assignee: cdawson → nobody
Reporter | ||
Comment 2•6 years ago
|
||
This includes why some errors that are expected to show in Treeherder proper are also not shown until the log output matches what we expect. Ideally moving to structured logs would handle this, but for non-structured logs outputting the right text so that our existing regex catches them. We don't want to add more regex.
Summary: Document the requirements for the test-based view to display data → Document log output requirements for getting bug suggestions and test failures
Comment 3•5 years ago
|
||
Let's do this in bug 1506799.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•2 years ago
|
Component: Treeherder: Docs & Development → TreeHerder
You need to log in
before you can comment on or make changes to this bug.
Description
•