intermittent failures of performance/tabopen.js and browser_appmenu.js on os x on reload/forward buttons
Categories
(Firefox :: General, defect, P3)
Tracking
()
People
(Reporter: surkov, Unassigned)
Details
Attachments
(2 files)
I see these intermittent failures on osx when running the test locally:
browser/base/content/test/performance/browser_tabopen.js
FAIL unexpected changed rect for a frame at 1th index: ({x1:45, x2:60, y1:46, y2:59, w:16, h:14}), window width: 1280 -
Stack trace:
chrome://mochikit/content/browser-test.js:test_ok:1314
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker/rects<:587
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker:578
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:withPerfObserver:652
chrome://mochitests/content/browser/browser/base/content/test/performance/browser_tabopen.js:null:48
chrome://mochikit/content/browser-test.js:Tester_execTest/<:1116
chrome://mochikit/content/browser-test.js:Tester_execTest:1144
chrome://mochikit/content/browser-test.js:nextTest/<:1005
chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
FAIL unexpected changed rect for a frame at 1th index: ({x1:78, x2:92, y1:46, y2:59, w:15, h:14}), window width: 1280 -
Stack trace:
chrome://mochikit/content/browser-test.js:test_ok:1314
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker/rects<:587
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker:578
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:withPerfObserver:652
chrome://mochitests/content/browser/browser/base/content/test/performance/browser_tabopen.js:null:48
chrome://mochikit/content/browser-test.js:Tester_execTest/<:1116
chrome://mochikit/content/browser-test.js:Tester_execTest:1144
chrome://mochikit/content/browser-test.js:nextTest/<:1005
chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
FAIL should have 0 unknown flickering areas - Got 2, expected 0
Stack trace:
chrome://mochikit/content/browser-test.js:test_is:1325
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:reportUnexpectedFlicker:609
chrome://mochitests/content/browser/browser/base/content/test/performance/head.js:withPerfObserver:652
chrome://mochitests/content/browser/browser/base/content/test/performance/browser_tabopen.js:null:48
chrome://mochikit/content/browser-test.js:Tester_execTest/<:1116
chrome://mochikit/content/browser-test.js:Tester_execTest:1144
chrome://mochikit/content/browser-test.js:nextTest/<:1005
chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
➜ central
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Comment 2•5 years ago
|
||
Alexander, the attached patch is 3 months old. Are you still working on this?
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Neha Kochar [:neha] from comment #2)
Alexander, the attached patch is 3 months old. Are you still working on this?
Honestly I don't. The patch was a workaround rather than a real fix. My understanding is florian wasn't happy about the approach.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•2 years ago
|
Description
•