DevToolsPixelOutputTests.TestLatencyInfoInstrumentation flaky |
|||
Issue descriptionI've seen two failures in a single sheriffing shift. Maybe this is an issue with the underlying machine, as it appears to have problems loading D3D for DX11 (if I read the dll name right), so it could be a configuration issue on the machine where the test runs. DevToolsPixelOutputTests.TestLatencyInfoInstrumentation (run #1): [ RUN ] DevToolsPixelOutputTests.TestLatencyInfoInstrumentation err: rx::Renderer11::initializeD3DDevice(750): Failed creating Debug D3D11 device - falling back to release runtime. [4248:2724:0628/165358:ERROR:angle_platform_impl.cc(33)] ANGLE Display::initialize error 4: Could not create D3D11 device. [4248:2724:0628/165358:ERROR:gl_surface_egl.cc(598)] eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type [4248:2724:0628/165358:ERROR:angle_platform_impl.cc(33)] ANGLE Display::initialize error 4: Renderer does not support PS 3.0.aborting! [4248:2724:0628/165358:ERROR:gl_surface_egl.cc(598)] eglInitialize D3D9 failed with error EGL_NOT_INITIALIZED err: rx::Renderer11::initializeD3DDevice(750): Failed creating Debug D3D11 device - falling back to release runtime. Full logs: https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/50167 and https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/50164
,
Dec 2 2016
Is anyone looking at this. Flake seems to have flared up on Linux too now. e.g.: https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests/builds/49618
,
Dec 8 2016
,
Dec 8 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dbcbd4aa79d65b8edff6e4a83158e61c7a0eada3 commit dbcbd4aa79d65b8edff6e4a83158e61c7a0eada3 Author: flackr <flackr@chromium.org> Date: Thu Dec 08 16:03:42 2016 Mark DevToolsPixelOutputTests.TestLatencyInfoInstrumentation flaky on linux. TBR=pfeldman@chromium.org BUG= 624215 Review-Url: https://codereview.chromium.org/2559183002 Cr-Commit-Position: refs/heads/master@{#437253} [modify] https://crrev.com/dbcbd4aa79d65b8edff6e4a83158e61c7a0eada3/chrome/browser/devtools/devtools_sanity_browsertest.cc
,
Dec 8 2016
,
Dec 15 2016
,
Dec 15 2016
,
Apr 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0b9fe71b83e108c2d72cb6ef5bf8772fa486cbdc commit 0b9fe71b83e108c2d72cb6ef5bf8772fa486cbdc Author: timloh <timloh@chromium.org> Date: Tue Apr 04 05:23:53 2017 Disable DevToolsPixelOutputTests.TestLatencyInfoInstrumentation The test DevToolsPixelOutputTests.TestLatencyInfoInstrumentation is already disabled on Windows and Linux due to previous flakiness. It's been flaky on Mac recently too, so expanding this to disable on all platforms. https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=browser_side_navigation_browser_tests&tests=TestLatencyInfoInstrumentation TBR=caseq@chromium.org BUG= 624215 Review-Url: https://codereview.chromium.org/2794223002 Cr-Commit-Position: refs/heads/master@{#461635} [modify] https://crrev.com/0b9fe71b83e108c2d72cb6ef5bf8772fa486cbdc/chrome/browser/devtools/devtools_sanity_browsertest.cc
,
Oct 5 2017
Bulk DevTools triage, closing low priority issues with no action plan. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Jun 29 2016