Bug 1265637 Comment 166 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I did a try push with Bug 1606652 backed out:
https://treeherder.mozilla.org/#/jobs?repo=try&selectedTaskRun=JRBQSSVcQSC9AjHqIcEsaw.0&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cusercancel%2Crunning%2Cpending%2Crunnable&revision=a103d9148c440ec3977476c2eb830104026bee81

It contains browser-chrome tests on which the assertion failure discussed here has been seen, I don't know if the
failure rate seen there can warrant a backout, but "handleParseWorkload" can be seen in the trace.
Revision 1 by
on 
I did a try push with Bug 1606652 backed out:
https://treeherder.mozilla.org/#/jobs?repo=try&selectedTaskRun=JRBQSSVcQSC9AjHqIcEsaw.0&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cusercancel%2Crunning%2Cpending%2Crunnable&revision=a103d9148c440ec3977476c2eb830104026bee81

It contains browser-chrome tests on which the assertion failure discussed here has been seen recently, I don't know if the
failure rate seen there can warrant a backout, but "handleParseWorkload" can be seen in the trace.

Back to Bug 1265637 Comment 166