Closed Bug 1143094 Opened 9 years ago Closed 9 years ago

talosprocess (mozprocess) fails to output needed data locally

Categories

(Testing :: Talos, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: jmaher)

References

Details

Attachments

(1 file)

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: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #8577362 - Flags: review?(wlachance)
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+
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Depends on: 1151466
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: