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

Issue 709704 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
OOO until 2019-01-24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

WebglConformance_conformance_glsl_bugs_varying_arrays_should_not_be_reversed fails on Nexus 5

Project Member Reported by jbau...@chromium.org, Apr 8 2017

Issue description

Added in r462964. I'll disable it for now.

https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%28Nexus%205%29/builds/4966

  Traceback (most recent call last):
    File "/b/c/b/Android_Release__Nexus_5_/irgpYPz5/third_party/catapult/telemetry/telemetry/testing/serially_executed_browser_test_case.py", line 194, in <lambda>
      return lambda self: based_method(self, *args)
    File "/b/c/b/Android_Release__Nexus_5_/irgpYPz5/content/test/gpu/gpu_tests/gpu_integration_test.py", line 73, in _RunGpuTest
      self.RunActualGpuTest(url, *args)
    File "/b/c/b/Android_Release__Nexus_5_/irgpYPz5/content/test/gpu/gpu_tests/webgl_conformance_integration_test.py", line 203, in RunActualGpuTest
      getattr(self, test_name)(test_path, *args[1:])
    File "/b/c/b/Android_Release__Nexus_5_/irgpYPz5/content/test/gpu/gpu_tests/webgl_conformance_integration_test.py", line 217, in _RunConformanceTest
      self._CheckTestCompletion()
    File "/b/c/b/Android_Release__Nexus_5_/irgpYPz5/content/test/gpu/gpu_tests/webgl_conformance_integration_test.py", line 213, in _CheckTestCompletion
      self.fail(self._WebGLTestMessages(self.tab))
  AssertionError: should be 255,0,0,255
  at (0, 0) expected: 255,0,0,255 was 0,0,255,255
  FAIL should be 255,0,0,255
  at (0, 0) expected: 255,0,0,255 was 0,0,255,255
  should be 0,0,255,255
  at (128, 0) expected: 0,0,255,255 was 255,0,0,255
  FAIL should be 0,0,255,255
  at (128, 0) expected: 0,0,255,255 was 255,0,0,255
  should be 0,128,255,255
  at (192, 0) expected: 0,128,255,255 was 255,128,0,255
  FAIL should be 0,128,255,255
  at (192, 0) expected: 0,128,255,255 was 255,128,0,255
  should be 255,128,0,255
  at (256, 0) expected: 255,128,0,255 was 0,128,255,255
  FAIL should be 255,128,0,255
  at (256, 0) expected: 255,128,0,255 was 0,128,255,255
  
 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 8 2017

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

commit b1c15eed1e0019a45f2bded8a153d5cd89dffed5
Author: jbauman <jbauman@chromium.org>
Date: Sat Apr 08 02:08:06 2017

Mark WebglConformance_conformance_glsl_bugs_varying_arrays_should_not_be_reversed failing on Nexus 5

It was just added in r462964

BUG=709704
TBR=kbr@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2802293003
Cr-Commit-Position: refs/heads/master@{#463106}

[modify] https://crrev.com/b1c15eed1e0019a45f2bded8a153d5cd89dffed5/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Sign in to add a comment