Closed Bug 1361048 Opened 7 years ago Closed 7 years ago

Intermittent linux64-qr debug tc-M(a11y),tc-M-e10s(gpu) TEST-UNEXPECTED-TIMEOUT | automation.py | application timed out after 330 seconds with no output

Categories

(Core :: Graphics: WebRender, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, regression, Whiteboard: [gfx-noted])

bisection at e151a646b157: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e9927cb4867b310f64eb8d69f35bf5fa7c94f644
bisection at 8c97d7533b82: https://treeherder.mozilla.org/#/jobs?repo=try&revision=07bc3c36e95e369c76c55300c5219db834b8c67a

Both show a failure rate of 2/7 which I'm going to consider as failure since we had a 0/7 on the successful one a couple of comments ago.

Regression range is now https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=260f2ff492af&tochange=8c97d7533b82
Summary: Intermittent linux64-qr debug tc-M(a11y) TEST-UNEXPECTED-TIMEOUT | automation.py | application timed out after 330 seconds with no output → Intermittent linux64-qr debug tc-M(a11y),tc-M-e10s(gpu) TEST-UNEXPECTED-TIMEOUT | automation.py | application timed out after 330 seconds with no output
Priority: -- → P3
Whiteboard: [gfx-noted]
These two failures are not on linux64-qr, so wrong bug. I'm going to close this one since it hasn't happened in a while.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.