Closed Bug 1520705 Opened 4 years ago Closed 4 years ago

Enable mochitest-chrome on WebRender


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




Tracking Status
firefox67 --- fixed


(Reporter: sotaro, Assigned: sotaro)


(Blocks 1 open bug)



(1 file)

During Bug 1508522 Comment 26, I noticed that mochitest-chrome is not enabled on WebRender yet. It includes several tests for animation. It is better to be enabled.

See Also: → 1455999
Summary: Enable mochitest chrome on WebRender → Enable mochitest-chrome on WebRender
Assignee: nobody → sotaro.ikeda.g
Priority: -- → P3
Depends on: 1522407

When I tried to enabled mochitest-chrome on both linux-qr-tests and windows-qr-tests. WebRender did not enabled on windows-qr-tests. It was because mochitest-chrome disables e10s. On windows, WebRender is disabled without GPU Process. Then for now, it seems OK to enable mochitest-chrome only on linux-qr-tests.

Depends on: 1522775
Depends on: 1523233
Depends on: 1523522
Depends on: 1524168

There are still the following internittent failures. Both are for Find Tookbar. There are already intermittent failures(Bug 1339326 and Bug 1511944). I talked with :m_kato, he also thought the failures happens very frequent with WebRender just because of timing change.

  • toolkit/content/tests/chrome/test_bug331215.xul
  • toolkit/content/tests/chrome/test_bug304188.xul

Can we mark them as intermittent and file follow ups to fix them?

Flags: needinfo?(sotaro.ikeda.g)

No problem about it. I am also thinking about it. Mochitest seems not have a filter for intermittent failure like reftest. Then I am going to mark them as skip-if.

Flags: needinfo?(sotaro.ikeda.g)
Blocks: 1526723

Created Bug 1526723 for re-enable test_bug331215.xul and test_bug304188.xul on WebRender.

Pushed by
Enable mochitest-chrome on WebRender r=kats
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
See Also: → 1454935
You need to log in before you can comment on or make changes to this bug.