There was a corresponding moztest change landed in that bug. Everything is fine as long as we release mozlog first. (the moztest update doesn't make sense without the mozlog update, but the mozlog update shouldn't break anything)
Assignee: nobody → cmanchester
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in before you can comment on or make changes to this bug.