All of the Windows Debug bots on the chromium.gpu.fyi waterfall seem to be failing the WebGL 2.0 conformance tests:

https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20(NVIDIA)
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win8%20Debug%20(NVIDIA)
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20(ATI)
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20(New%20Intel)

The failure mode is a timeout:

Expected exception while running WebglConformance.deqp_data_gles3_shaders_linkage

Traceback (most recent call last):
  RunStoryWithRetries at content\test\gpu\gpu_tests\gpu_test_base.py:72
    super(cls, shared_page_state).RunStory(results)
  RunStory at third_party\catapult\telemetry\telemetry\page\shared_page_state.py:336
    self._current_page.Run(self)
  Run at third_party\catapult\telemetry\telemetry\page\__init__.py:84
    shared_state.page_test.RunNavigateSteps(self, current_tab)
  RunNavigateSteps at third_party\catapult\telemetry\telemetry\page\page_test.py:182
    page.RunNavigateSteps(action_runner)
  RunNavigateSteps at content\test\gpu\gpu_tests\webgl_conformance.py:143
    'webglTestHarness._finished', timeout_in_seconds=300)
  WaitForJavaScriptCondition at third_party\catapult\telemetry\telemetry\page\action_runner.py:186
    self._tab.WaitForJavaScriptExpression(condition, timeout_in_seconds)
  WaitForJavaScriptExpression at third_party\catapult\telemetry\telemetry\internal\browser\web_contents.py:111
    e.message + '\n' + debug_message)
TimeoutException: 
Exception thrown when trying to capture console output: TimeoutException('',)

Locals:
  IsJavaScriptExpressionTrue : <function IsJavaScriptExpressionTrue at 0x031FBDF0>
  debug_message              : "Exception thrown when trying to capture console output: TimeoutException('',)"
  e                          : TimeoutException('',)
  expr                       : 'webglTestHarness._finished'
  timeout                    : 300

[1868:3960:0408/215843:WARNING:histogram_base.cc(131)] 2 histograms were created before reporting was enabled.
+--------------------------------------------------------------------------------+
| End of shard 0  Pending: 541.4s  Duration: 1992.8s  Bot: build124-m1  Exit: -1 |
+--------------------------------------------------------------------------------+


I'm not 100% sure what is going on but it looks like this particular test may be timing out, and Telemetry may not be handling that timeout correctly, causing the entire test suite to abort.

Jamie, can you please try reproducing this behavior locally in a debug build on Windows? If it's necessary to skip a test in Debug, let's add it to webgl2_conformance_expectations.py.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/86e7030b9c0bd7c13661fa3058e21235e1c4bf74

commit 86e7030b9c0bd7c13661fa3058e21235e1c4bf74
Author: jmadill <jmadill@chromium.org>
Date: Mon Apr 11 18:41:49 2016

gpu: Skip the dEQP linkage GLES3 test on Windows Debug.

Seems to be causing an assert failure, unknown as to why.

BUG= 601821 
TBR=kbr@chromium.org,zmo@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Review URL: https://codereview.chromium.org/1880543002

Cr-Commit-Position: refs/heads/master@{#386426}

[modify] https://crrev.com/86e7030b9c0bd7c13661fa3058e21235e1c4bf74/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

ANGLE CQ is fixed, regression remains for unknown reasons - unlikely it's ANGLE.

It's not a regression, but I enabled some tests for WebGL 2.

This should be a bug in ANGLE all the time.  Enabling this test triggers this bug.

Ken: I think it's weird that telemetry fails to run subsequent test in this case. I don't have cycle to look into this right now, but this is something to watch out for.