Closed Bug 1574535 Opened 2 years ago Closed 2 years ago

Perma Windows 10 asan browser/base/content/test/performance/browser_startup_syncIPC.js | unexpected PAPZInputBridge::Msg_ProcessUnhandledEvent sync IPC before handling user events -

Categories

(Firefox :: General, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1553693

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, regression)

Filed by: archaeopteryx [at] coole-files.de
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=262029676&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/blxXKC8oSvmrwutoxS36MA/runs/0/artifacts/public/logs/live_backing.log


[task 2019-08-16T15:38:54.762Z] 15:38:54 INFO - TEST-PASS | browser/base/content/test/performance/browser_startup_syncIPC.js | sync IPC PCompositorBridge::Msg_WillClose allowed 1 more times before first paint -
[task 2019-08-16T15:38:54.762Z] 15:38:54 INFO - TEST-PASS | browser/base/content/test/performance/browser_startup_syncIPC.js | sync IPC PAPZInputBridge::Msg_ProcessUnhandledEvent happened as many times as expected before first paint -
[task 2019-08-16T15:38:54.763Z] 15:38:54 INFO - whitelisted sync IPC before handling user events:
[task 2019-08-16T15:38:54.763Z] 15:38:54 INFO - PLayerTransaction::Msg_GetTextureFactoryIdentifier - at most 1 times
[task 2019-08-16T15:38:54.763Z] 15:38:54 INFO - PCompositorBridge::Msg_Initialize - at most 1 times
[task 2019-08-16T15:38:54.764Z] 15:38:54 INFO - PCompositorBridge::Msg_WillClose - at most 2 times
[task 2019-08-16T15:38:54.764Z] 15:38:54 INFO - PCompositorBridge::Msg_MakeSnapshot - at most 1 times
[task 2019-08-16T15:38:54.764Z] 15:38:54 INFO - Buffered messages finished
[task 2019-08-16T15:38:54.765Z] 15:38:54 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_startup_syncIPC.js | unexpected PAPZInputBridge::Msg_ProcessUnhandledEvent sync IPC before handling user events -
[task 2019-08-16T15:38:54.765Z] 15:38:54 INFO - Stack trace:
[task 2019-08-16T15:38:54.765Z] 15:38:54 INFO - chrome://mochikit/content/browser-test.js:test_ok:1576
[task 2019-08-16T15:38:54.765Z] 15:38:54 INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/browser_startup_syncIPC.js:null:320
[task 2019-08-16T15:38:54.766Z] 15:38:54 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1346
[task 2019-08-16T15:38:54.766Z] 15:38:54 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1381
[task 2019-08-16T15:38:54.766Z] 15:38:54 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1209
[task 2019-08-16T15:38:54.766Z] 15:38:54 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:803
[task 2019-08-16T15:38:54.767Z] 15:38:54 INFO - Not taking screenshot here: see the one that was previously logged

Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/autoland/rev/da39f0cebbff
temporarily disable suddenly permafailing browser_startup_syncIPC.js. a=florian-on-IRC CLOSED TREE

This started with bug 1562292 landing on inbound and had been classified with bug 1553693 which is a perfectly matching suggestion.

The root of the problem here is that the test is designed to expect sync IPCs (which are blocking) to happen during a specific phase of startup, but a lot of the sync IPC requests happen in reaction to async stuff (like creating a content process), so when running on different hardware, some IPC happens during different phases. The whitelist already has plenty of "ignoreIfUunused" attributes due to this. It might be time to re-engineer the test a bit so that the phase listed is the earliest phase at which the IPC is known to happen, but let the test not fail if the IPC happens later than expected.

In the specific case of this bug, we have a bunch of stuff that happens "before becoming idle" instead of "before handling user events", which should actually be an improvement (and there's also stuff happening "before handling user events" instead of "before first paint").

This is no longer perma-failing and there is another bug for this issue, bug 1553693, closing as a duplicate.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(florian)
Resolution: --- → DUPLICATE
Duplicate of bug: 1553693
You need to log in before you can comment on or make changes to this bug.