Filed by: rvandermeulen [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=2779473&repo=autoland https://queue.taskcluster.net/v1/task/Qv5AmwiwTk-FOZzCDygI7g/runs/0/artifacts/public%2Flogs%2Flive_backing.log https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/Qv5AmwiwTk-FOZzCDygI7g/runs/0/artifacts/public%2Flogs%2Flive_backing.log&only_show_unexpected=1
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
this bug started up on Jan 11th, and I was not able to get it to reproduce with retriggers: https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=Linux%20x64%20opt%20Reftests%20executed%20by%20TaskCluster%20test-linux64%2Fopt-reftest-no-accel-3%20tc-R(Ru3)&tochange=d1d89a3a187aa24845db5886cf0bc89747e2db5b&fromchange=c85f83a7fcd7b1bda04318a2cc6370eb5247600e&group_state=expanded then magically it stopped after Jan 21 and we haven't seen it for a few days- I suspect something triggered this and whatever it was is backed out, or changed to adjust the timing.
(In reply to Joel Maher ( :jmaher) from comment #5) > then magically it stopped after Jan 21 and we haven't seen it for a few days but then it started again. Overall, failure frequency has been fairly consistent since Jan 11.
The problem seems to be that we're taking the snapshot too early for some reason. This seems to fix it. https://treeherder.mozilla.org/#/jobs?repo=try&revision=be3066b9fbefc7d0b560da215d265fcc0df26a00
Attachment #8834956 - Flags: review?(ryanvm)
Attachment #8834956 - Flags: review?(ryanvm) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/99c66e67c00e Wait for MozReftestInvalidate before ending test. r=ryanvm
You need to log in before you can comment on or make changes to this bug.