Closed Bug 1777593 Opened 3 years ago Closed 3 years ago

Intermittent gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_initial_displayport.html | The displayport height should be less than the iframe height -

Categories

(Core :: Panning and Zooming, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Filed by: smolnar [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=383053862&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/SwOq9n7FSCKkStyPtBVzPg/runs/0/artifacts/public/logs/live_backing.log


INFO - TEST-PASS | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_initial_displayport.html | The displayport height should be greater than zero - 
[task 2022-06-30T19:54:35.629Z] 19:54:35     INFO - Buffered messages finished
[task 2022-06-30T19:54:35.630Z] 19:54:35     INFO - TEST-UNEXPECTED-FAIL | gfx/layers/apz/test/mochitest/browser_test_group_fission.js | http://mochi.test:8888/browser/gfx/layers/apz/test/mochitest/helper_fission_initial_displayport.html | The displayport height should be less than the iframe height - 
[task 2022-06-30T19:54:35.630Z] 19:54:35     INFO - Stack trace:
[task 2022-06-30T19:54:35.630Z] 19:54:35     INFO - chrome://mochikit/content/browser-test.js:test_ok:1401
[task 2022-06-30T19:54:35.631Z] 19:54:35     INFO - chrome://mochitests/content/browser/gfx/layers/apz/test/mochitest/FissionTestHelperParent.jsm:receiveMessage:45
[task 2022-06-30T19:54:35.631Z] 19:54:35     INFO - GECKO(5312) | OOPIF response for Displayport: {"x":0,"y":0,"width":400,"height":256}
[task 2022-06-30T19:54:35.632Z] 19:54:35     INFO - TEST-PASS | gfx/layers/apz/test/mochitest/browser_test_group_fission.js 
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.