[root layer scrolls] HeadlessWebContentsBeginFrameControlViewportTest fails |
|||
Issue descriptionThis test fails in the headless_browsertests step on four trybots: HeadlessWebContentsBeginFrameControlViewportTest.RunAsyncTest DomTreeExtractionBrowserTest.RunAsyncTest The affected bots are: https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_headless_rel/233159 https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/620275 https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/76819 https://ci.chromium.org/buildbot/tryserver.chromium.win/win10_chromium_x64_rel_ng/58124 The output includes: ../../headless/lib/headless_web_contents_browsertest.cc:1304: Failure Expected equality of these values: expected_color Which is: 4278190335 actual_color Which is: 4294967295 ../../headless/lib/headless_web_contents_browsertest.cc:1306: Failure Expected equality of these values: expected_color Which is: 4278190335 actual_color Which is: 4294967295 ../../headless/lib/headless_web_contents_browsertest.cc:1308: Failure Expected equality of these values: expected_color Which is: 4278190335 actual_color Which is: 4294967295 ../../headless/lib/headless_web_contents_browsertest.cc:1310: Failure Expected equality of these values: expected_color Which is: 4278190335 actual_color Which is: 4294967295 ../../headless/lib/headless_web_contents_browsertest.cc:1312: Failure Expected equality of these values: expected_color Which is: 4278190335 actual_color Which is: 4294967295 [ FAILED ] HeadlessWebContentsBeginFrameControlViewportTest.RunAsyncTest, where TypeParam = and GetParam() = (258 ms)
,
Jan 18 2018
,
Jan 18 2018
This one is also passing for me locally.
,
Jan 19 2018
Did a new tryjob and this test was green on all bots mentioned above: https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_headless_rel/239694 https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/627856 https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/84254 https://ci.chromium.org/buildbot/tryserver.chromium.win/win10_chromium_x64_rel_ng/65026 So either it got fixed by another patch in the mean time or it was a flake. |
|||
►
Sign in to add a comment |
|||
Comment 1 by skobes@chromium.org
, Jan 16 2018