Closed
Bug 1092317
Opened 10 years ago
Closed 10 years ago
Talos logparsing problems
Categories
(Tree Management :: Treeherder, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wlach, Assigned: wlach)
Details
Attachments
(1 file)
When we were trying to figure out what was going on with the performance artifact ingestion, we noticed some minor issues with the talos logparser: 1. It doesn't fail noisily if it encounters a badly formed TALOSDATA or TalusResult line. 2. We want a "TalosResult" artifact, but we're sometimes prematurely truncating that line (and weren't noticing that because of (1)). 3. We should have unit tests for logparser failure cases, as well as success ones
|
Assignee | |
Comment 1•10 years ago
|
||
Assignee: nobody → wlachance
Attachment #8515222 -
Flags: review?(mdoglio)
|
||
Updated•10 years ago
|
Attachment #8515222 -
Flags: review?(mdoglio) → review+
|
||
Comment 2•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/treeherder-service https://github.com/mozilla/treeherder-service/commit/8fae856593e630ec5de4acf9747383c19e152c20 Bug 1092317 - Minor performance log parsing fixes (with tests) https://github.com/mozilla/treeherder-service/commit/8e43943c6d5debb321117e2eb7aa280d00b6be0a Merge pull request #278 from wlach/1092317 Bug 1092317 - Perf logparsing fixes/cleanups
|
|
Assignee | |
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•