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

Issue 914631 link

Starred by 1 user
Status: Fixed
Owner:
sunn...@chromium.org
Closed: Jan 15
Cc:
█ kbr@chromium.org
geoffl...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug

Blocking:
issue 882580



Sign in to add a comment

WebglConformance_conformance_limits_gl_max_texture_dimensions is flaky with passthrough on android-marshmallow-arm64-rel

Project Member Reported by sunn...@chromium.org, Dec 13 
E.g. https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/150428

I'll mark it as flaky.

Log:
[67/157] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance_limits_gl_max_texture_dimensions failed unexpectedly 9.4751s:
  
  Traceback (most recent call last):
    _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:155
      self.RunActualGpuTest(url, *args)
    RunActualGpuTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:199
      getattr(self, test_name)(test_path, *args[1:])
    _RunConformanceTest at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:288
      self._CheckTestCompletion()
    _CheckTestCompletion at content/test/gpu/gpu_tests/webgl_conformance_integration_test.py:284
      self.fail(self._WebGLTestMessages(self.tab))
    fail at .swarming_module/lib/python2.7/unittest/case.py:410
      raise self.failureException(msg)
  AssertionError: Should be 0, 255, 128, 255
  at (0, 3) expected: 0,255,128,255 was 0,203,102,203
  FAIL Should be 0, 255, 128, 255
  at (0, 3) expected: 0,255,128,255 was 0,203,102,203
  
  Locals:
    msg : u'Should be 0, 255, 128, 255\nat (0, 3) expected: 0,255,128,255 was 0,203,102,203\nFAIL Should be 0, 255, 128, 255\nat (0, 3) expected: 0,255,128,255 was 0,203,102,203\n'

Comment 1 by kbr@chromium.org, Dec 13

Blocking: 882580
Cc: geoffl...@chromium.org
Components: Internals>GPU>ANGLE
Important note: it's flaky on the passthrough command decoder ( webgl_conformance_gles_passthrough_tests ).

Comment 2 by kbr@chromium.org, Dec 13

Summary: WebglConformance_conformance_limits_gl_max_texture_dimensions is flaky with passthrough on android-marshmallow-arm64-rel (was: WebglConformance_conformance_limits_gl_max_texture_dimensions is flaky on android-marshmallow-arm64-rel)
Project Member

Comment 3 by bugdroid1@chromium.org, Dec 13 

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

commit 6235c697728146aeaad8dc244c45f003e09289e6
Author: Sunny Sachanandani <sunnyps@chromium.org>
Date: Thu Dec 13 03:54:31 2018

Mark gl-max-texture-dimensions test (passthrough) as flaky on Nexus 5X

This test has been flaking on the android-marshmallow-arm64-rel trybot
for a while e.g.
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/150428

TBR=kbr@chromium.org

Bug:  914631 
Change-Id: I5e5f640ba8386296dda8dc8c7607ce50ec1a2236
Reviewed-on: https://chromium-review.googlesource.com/c/1374977
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#616202}
[modify] https://crrev.com/6235c697728146aeaad8dc244c45f003e09289e6/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Comment 4 by geoffl...@chromium.org, Dec 13 

This may be due to timeouts, we're not artificially limiting max texture size on Android yet like Chrome does.

Comment 5 by sunn...@chromium.org, Jan 15

Status: Fixed (was: Assigned)
►

Sign in to add a comment