Closed
Bug 1143094
Opened 9 years ago
Closed 9 years ago
talosprocess (mozprocess) fails to output needed data locally
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
Attachments
(1 file)
1.96 KB,
patch
|
wlach
:
review+
|
Details | Diff | Splinter Review |
while running talos locally, I found that the local.out and local.json didn't have results. Looking into this further, we had failures in the browser_output.txt format causing our results processing to be wonky. Why this is different locally vs in tree, no idea. I have a patch that doesn't log by default, instead we use a processOutputHandler. try run is here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=4cbddf8c46fb
Assignee | ||
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Comment on attachment 8577362 [details] [diff] [review] use processOutputHandler instead of logFile (1.0) Review of attachment 8577362 [details] [diff] [review]: ----------------------------------------------------------------- So as discussed on irc, the proper solution is to just remove this class and call mozprocess directly. However, this fixes the immediate problem of us writing to the file from two different places, so we might as well put it in.
Attachment #8577362 -
Flags: review?(wlachance) → review+
Assignee | ||
Comment 3•9 years ago
|
||
https://hg.mozilla.org/build/talos/rev/4d31e0f61658
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•