Filed by: ihsiao [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=87451064&repo=autoland https://queue.taskcluster.net/v1/task/ZxibGo-CTOWUmW40B-AVUQ/runs/0/artifacts/public/logs/live_backing.log https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/ZxibGo-CTOWUmW40B-AVUQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
5 failures in 845 pushes (0.006 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * autoland: 3 * mozilla-inbound: 2 Platform breakdown: * linux64-stylo: 3 * linux64: 1 * linux32: 1 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1351950&startday=2017-03-27&endday=2017-04-02&tree=all
5 failures in 867 pushes (0.006 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * mozilla-inbound: 2 * autoland: 2 * mozilla-central: 1 Platform breakdown: * linux64: 2 * linux32: 2 * linux64-stylo: 1 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1351950&startday=2017-04-03&endday=2017-04-09&tree=all
And that's why you never want to let a bullshit "crash" "signature" stay in a summary: we'll star every single unfiled 330 seconds without output hang as being all one bug if there's a suggested bug, and we'll only think about whether it was just a hang or an actual crash if we're forced to file because there's nothing with the bogus signature from the post-hang intentional crash to be lazy with.
Resolving intermittent Stylo test failure bugs that haven't had any recent activity.