New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 872302 link

Starred by 1 user
Status: Fixed
Owner:
█ kbr@chromium.org
OOO until 2019-01-24
Closed: Aug 21
Cc:
geoffl...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 522133
issue 876777



Sign in to add a comment

Run WebGL2 tests on Intel with the passthrough command decoder

Project Member Reported by geoffl...@chromium.org, Aug 8 
This configuration is a hole in our automated testing, we can at least run these tests on the FYI waterfall.

Comment 1 by geoffl...@chromium.org, Aug 8

Labels: -Pri-3 Pri-2
Project Member

Comment 2 by bugdroid1@chromium.org, Aug 11 

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

commit 4c7862cb6e7b0be134f2373e3dae5af8d0f6dc64
Author: Kenneth Russell <kbr@chromium.org>
Date: Sat Aug 11 00:01:27 2018

Run WebGL 2.0 tests on passthrough cmd decoder on Linux/Intel.

It looks like an oversight that they weren't run on this configuration
previously.

Tbr: geofflang@chromium.org
Bug:  872302 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I77e4e175a449cea70254dcc3bab8ea3686fc74d9
Reviewed-on: https://chromium-review.googlesource.com/1168464
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582392}
[modify] https://crrev.com/4c7862cb6e7b0be134f2373e3dae5af8d0f6dc64/testing/buildbot/chromium.gpu.fyi.json
[modify] https://crrev.com/4c7862cb6e7b0be134f2373e3dae5af8d0f6dc64/testing/buildbot/waterfalls.pyl

Comment 3 by kbr@chromium.org, Aug 21

Cc: geoffl...@chromium.org
A couple of test flakes were observed on this bot after enabling these tests:

WebglConformance_conformance2_rendering_attrib_type_match
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28Intel%20HD%20630%29/5094
(and many other instances)

WebglConformance_deqp_functional_gles3_shaderpackingfunction
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28Intel%20HD%20630%29/5093
(and many other instances)

These were suppressed in:
https://chromium-review.googlesource.com/1179819

At this point there is one more intermittent flake:
WebglConformance_conformance_extensions_webgl_compressed_texture_s3tc
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28Intel%20HD%20630%29/5194

Symptom:

[54/145] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance_extensions_webgl_compressed_texture_s3tc failed unexpectedly 6.6202s:
  
  Traceback (most recent call last):
    _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:138
      self.RunActualGpuTest(url, *args)
    RunActualGpuTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:186
      getattr(self, test_name)(test_path, *args[1:])
    _RunConformanceTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:200
      self._CheckTestCompletion()
    _CheckTestCompletion at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:196
      self.fail(self._WebGLTestMessages(self.tab))
    fail at .swarming_module/lib/python2.7/unittest/case.py:410
      raise self.failureException(msg)
  AssertionError: at (4, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 0) expected: 0,0,0,0 was 0,0,66,1
  at (4, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 0) expected: 0,0,0,0 was 0,0,66,1
  at (5, 0) expected: 0,0,0,0 was 0,0,44,1
  FAIL at (5, 0) expected: 0,0,0,0 was 0,0,44,1
  at (5, 0) expected: 0,0,0,0 was 0,0,44,1
  FAIL at (5, 0) expected: 0,0,0,0 was 0,0,44,1
  at (6, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 0) expected: 0,0,0,0 was 0,0,66,1
  at (6, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 0) expected: 0,0,0,0 was 0,0,66,1
  at (7, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 0) expected: 0,0,0,0 was 0,0,66,1
  at (7, 0) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 0) expected: 0,0,0,0 was 0,0,66,1
  at (4, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 1) expected: 0,0,0,0 was 0,0,66,1
  at (4, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 1) expected: 0,0,0,0 was 0,0,66,1
  at (5, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 1) expected: 0,0,0,0 was 0,0,66,1
  at (5, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 1) expected: 0,0,0,0 was 0,0,66,1
  at (6, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 1) expected: 0,0,0,0 was 0,0,66,1
  at (6, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 1) expected: 0,0,0,0 was 0,0,66,1
  at (7, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 1) expected: 0,0,0,0 was 0,0,66,1
  at (7, 1) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 1) expected: 0,0,0,0 was 0,0,66,1
  at (4, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 2) expected: 0,0,0,0 was 0,0,66,1
  at (4, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 2) expected: 0,0,0,0 was 0,0,66,1
  at (5, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 2) expected: 0,0,0,0 was 0,0,66,1
  at (5, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 2) expected: 0,0,0,0 was 0,0,66,1
  at (6, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 2) expected: 0,0,0,0 was 0,0,66,1
  at (6, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 2) expected: 0,0,0,0 was 0,0,66,1
  at (7, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 2) expected: 0,0,0,0 was 0,0,66,1
  at (7, 2) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 2) expected: 0,0,0,0 was 0,0,66,1
  at (4, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 3) expected: 0,0,0,0 was 0,0,66,1
  at (4, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (4, 3) expected: 0,0,0,0 was 0,0,66,1
  at (5, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 3) expected: 0,0,0,0 was 0,0,66,1
  at (5, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (5, 3) expected: 0,0,0,0 was 0,0,66,1
  at (6, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 3) expected: 0,0,0,0 was 0,0,66,1
  at (6, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (6, 3) expected: 0,0,0,0 was 0,0,66,1
  at (7, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 3) expected: 0,0,0,0 was 0,0,66,1
  at (7, 3) expected: 0,0,0,0 was 0,0,66,1
  FAIL at (7, 3) expected: 0,0,0,0 was 0,0,66,1
  at (0, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 4) expected: 0,0,0,0 was 132,0,0,1
  at (0, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 4) expected: 0,0,0,0 was 132,0,0,1
  at (1, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 4) expected: 0,0,0,0 was 132,0,0,1
  at (1, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 4) expected: 0,0,0,0 was 132,0,0,1
  at (2, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 4) expected: 0,0,0,0 was 132,0,0,1
  at (2, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 4) expected: 0,0,0,0 was 132,0,0,1
  at (3, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 4) expected: 0,0,0,0 was 132,0,0,1
  at (3, 4) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 4) expected: 0,0,0,0 was 132,0,0,1
  at (4, 4) expected: 0,0,0,0 was 0,0,0,255
  FAIL at (4, 4) expected: 0,0,0,0 was 0,0,0,255
  at (0, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 5) expected: 0,0,0,0 was 132,0,0,1
  at (0, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 5) expected: 0,0,0,0 was 132,0,0,1
  at (1, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 5) expected: 0,0,0,0 was 132,0,0,1
  at (1, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 5) expected: 0,0,0,0 was 132,0,0,1
  at (2, 5) expected: 0,0,0,0 was 132,0,0,0
  FAIL at (2, 5) expected: 0,0,0,0 was 132,0,0,0
  at (3, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 5) expected: 0,0,0,0 was 132,0,0,1
  at (3, 5) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 5) expected: 0,0,0,0 was 132,0,0,1
  at (0, 6) expected: 0,0,0,0 was 132,0,0,0
  FAIL at (0, 6) expected: 0,0,0,0 was 132,0,0,0
  at (1, 6) expected: 0,0,0,0 was 132,0,0,0
  FAIL at (1, 6) expected: 0,0,0,0 was 132,0,0,0
  at (2, 6) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 6) expected: 0,0,0,0 was 132,0,0,1
  at (2, 6) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 6) expected: 0,0,0,0 was 132,0,0,1
  at (3, 6) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 6) expected: 0,0,0,0 was 132,0,0,1
  at (3, 6) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 6) expected: 0,0,0,0 was 132,0,0,1
  at (7, 6) expected: 0,0,0,0 was 19,81,0,0
  FAIL at (7, 6) expected: 0,0,0,0 was 19,81,0,0
  at (7, 6) expected: 0,0,0,0 was 19,81,0,0
  FAIL at (7, 6) expected: 0,0,0,0 was 19,81,0,0
  at (0, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 7) expected: 0,0,0,0 was 132,0,0,1
  at (0, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (0, 7) expected: 0,0,0,0 was 132,0,0,1
  at (1, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 7) expected: 0,0,0,0 was 132,0,0,1
  at (1, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (1, 7) expected: 0,0,0,0 was 132,0,0,1
  at (2, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 7) expected: 0,0,0,0 was 132,0,0,1
  at (2, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (2, 7) expected: 0,0,0,0 was 132,0,0,1
  at (3, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 7) expected: 0,0,0,0 was 132,0,0,1
  at (3, 7) expected: 0,0,0,0 was 132,0,0,1
  FAIL at (3, 7) expected: 0,0,0,0 was 132,0,0,1
  at (4, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (4, 7) expected: 0,0,0,0 was 38,162,0,0
  at (4, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (4, 7) expected: 0,0,0,0 was 38,162,0,0
  at (5, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (5, 7) expected: 0,0,0,0 was 38,162,0,0
  at (5, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (5, 7) expected: 0,0,0,0 was 38,162,0,0
  at (6, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (6, 7) expected: 0,0,0,0 was 38,162,0,0
  at (6, 7) expected: 0,0,0,0 was 38,162,0,0
  FAIL at (6, 7) expected: 0,0,0,0 was 38,162,0,0

Comment 4 by kbr@chromium.org, Aug 21

Status: Started (was: Assigned)
Project Member

Comment 5 by bugdroid1@chromium.org, Aug 21 

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

commit 9cbe26531ad64a7fdb332f570ccbf9ae303f838e
Author: Kenneth Russell <kbr@chromium.org>
Date: Tue Aug 21 22:47:22 2018

Suppress webgl-compressed-texture-s3tc flake on Linux Intel.

Observed flaky after starting testing on the passthrough command
decoder on this configuration.

Tbr: geofflang@chromium.org
Bug:  872302 
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I44700af5fa229f10037435c226f870e306736730
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/1184178
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584914}
[modify] https://crrev.com/9cbe26531ad64a7fdb332f570ccbf9ae303f838e/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Comment 6 by kbr@chromium.org, Aug 21

Status: Fixed (was: Started)
With the change above, these tests should be running reliably on this bot. Please reopen or file a dependent bug if not.

Comment 8 by kbr@chromium.org, Aug 22

Blocking: 876777
►

Sign in to add a comment