|
|
DescriptionFix compositor_unittests with Ozone X11.
Some of the tests in compositor_unittests use OSMesa to draw but
TestCompositorHostOzone never creates an AccereleratedWidget. This works
fine with the headless OSMesa implementation, since it never draws to
the AcceleratedWidget, but won't work with GLSurfaceOSMesaX11 which
draws to an XWindow.
Create a PlatformWindow using the OzonePlatform object. This will
produce an AcceleratedWidget appropriately.
BUG=698780
Review-Url: https://codereview.chromium.org/2737513003
Cr-Commit-Position: refs/heads/master@{#455210}
Committed: https://chromium.googlesource.com/chromium/src/+/bf2bb744c704f16735d19c617f69beaba236db9b
Patch Set 1 #Patch Set 2 : Simplify. #Patch Set 3 : Other. #
Total comments: 2
Patch Set 4 : Group. #
Messages
Total messages: 33 (20 generated)
Description was changed from ========== Fix compositor_unittests with Ozone X11. Some of the tests in compositor_unittests use OSMesa to draw. The TestCompositorHostOzone implementation never creates an AccereleratedWidget. BUG=TBD ========== to ========== Fix compositor_unittests with Ozone X11. Some of the tests in compositor_unittests use OSMesa to draw but TestCompositorHostOzone never creates an AccereleratedWidget. This works fine with the headless OSMesa implementation, since it never draws to the AcceleratedWidget, but won't work with GLSurfaceOSMesaX11 which draws to an XWindow. Create a PlatformWindow using the OzonePlatform object. This will produce an AcceleratedWidget appropriately. BUG=698780 ==========
The CQ bit was checked by kylechar@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
kylechar@chromium.org changed reviewers: + danakj@chromium.org, sadrul@chromium.org
+danakj for ui/compositor/* +sadrul for DEPS
LGTM https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... File ui/compositor/test/test_suite.cc (right): https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... ui/compositor/test/test_suite.cc:38: #if defined(USE_OZONE) nit: group with GLSurface init
stamp lgtm
Thanks! https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... File ui/compositor/test/test_suite.cc (right): https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... ui/compositor/test/test_suite.cc:38: #if defined(USE_OZONE) On 2017/03/06 20:56:16, danakj wrote: > nit: group with GLSurface init Done.
Thanks! https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... File ui/compositor/test/test_suite.cc (right): https://codereview.chromium.org/2737513003/diff/40001/ui/compositor/test/test... ui/compositor/test/test_suite.cc:38: #if defined(USE_OZONE) On 2017/03/06 20:56:16, danakj wrote: > nit: group with GLSurface init Done.
The CQ bit was checked by kylechar@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from danakj@chromium.org, sadrul@chromium.org Link to the patchset: https://codereview.chromium.org/2737513003/#ps60001 (title: "Group.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by kylechar@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by kylechar@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2017/03/07 01:30:49, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...) I have no idea how this is breaking a Windows test. None of the changes are even compiled on Windows. It's failed a couples times now though, will investigate further later today.
On 2017/03/07 14:53:46, kylechar wrote: > On 2017/03/07 01:30:49, commit-bot: I haz the power wrote: > > Try jobs failed on following builders: > > win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, > > > http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...) > > I have no idea how this is breaking a Windows test. None of the changes are even > compiled on Windows. It's failed a couples times now though, will investigate > further later today. The test is just broken by the looks of things.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by kylechar@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by kylechar@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 60001, "attempt_start_ts": 1488913192184570, "parent_rev": "79debcb11fbe23b7951ecdbf1721c490319f54e6", "commit_rev": "bf2bb744c704f16735d19c617f69beaba236db9b"}
Message was sent while issue was closed.
Description was changed from ========== Fix compositor_unittests with Ozone X11. Some of the tests in compositor_unittests use OSMesa to draw but TestCompositorHostOzone never creates an AccereleratedWidget. This works fine with the headless OSMesa implementation, since it never draws to the AcceleratedWidget, but won't work with GLSurfaceOSMesaX11 which draws to an XWindow. Create a PlatformWindow using the OzonePlatform object. This will produce an AcceleratedWidget appropriately. BUG=698780 ========== to ========== Fix compositor_unittests with Ozone X11. Some of the tests in compositor_unittests use OSMesa to draw but TestCompositorHostOzone never creates an AccereleratedWidget. This works fine with the headless OSMesa implementation, since it never draws to the AcceleratedWidget, but won't work with GLSurfaceOSMesaX11 which draws to an XWindow. Create a PlatformWindow using the OzonePlatform object. This will produce an AcceleratedWidget appropriately. BUG=698780 Review-Url: https://codereview.chromium.org/2737513003 Cr-Commit-Position: refs/heads/master@{#455210} Committed: https://chromium.googlesource.com/chromium/src/+/bf2bb744c704f16735d19c617f69... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/chromium/src/+/bf2bb744c704f16735d19c617f69... |