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

Issue 610023 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocked on:
issue 611930

Blocking:
issue 490984



Sign in to add a comment

Nexus 9 bot is failing some tests from gpu_process

Project Member Reported by cblume@chromium.org, May 7 2016

Issue description

The following gpu_process tests are failing on the Nexus 9:

GpuProcess.no_gpu_process
GpuProcess.skip_gpu_process
GpuProcess.identify_active_gpu1
GpuProcess.identify_active_gpu2
GpuProcess.identify_active_gpu3
GpuProcess.identify_active_gpu4
GpuProcess.readback_webgl_gpu_process
GpuProcess.driver_bug_workarounds_upon_gl_renderer
 

Comment 1 by kbr@chromium.org, May 9 2016

Blocking: 490984
Project Member

Comment 2 by bugdroid1@chromium.org, May 9 2016

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

commit b0135d6afd0d12f1be4ede852ae15e751941b389
Author: cblume <cblume@chromium.org>
Date: Mon May 09 22:09:18 2016

The Nexus 9 bot is failing a maps test and a few gpu_process tests.

I have filed bugs  610023  and  610034  for these.

The failing tests are:

GpuProcess.no_gpu_process
GpuProcess.skip_gpu_process
GpuProcess.identify_active_gpu1
GpuProcess.identify_active_gpu2
GpuProcess.identify_active_gpu3
GpuProcess.identify_active_gpu4
GpuProcess.readback_webgl_gpu_process
GpuProcess.driver_bug_workarounds_upon_gl_renderer
Maps.maps_002

I tested locally on a Nexus 9.

BUG= 409984 ,  610023 ,  610034 
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/1956153002
Cr-Commit-Position: refs/heads/master@{#392439}

[modify] https://crrev.com/b0135d6afd0d12f1be4ede852ae15e751941b389/content/test/gpu/generate_buildbot_json.py
[modify] https://crrev.com/b0135d6afd0d12f1be4ede852ae15e751941b389/content/test/gpu/gpu_tests/gpu_process_expectations.py
[modify] https://crrev.com/b0135d6afd0d12f1be4ede852ae15e751941b389/content/test/gpu/gpu_tests/maps_expectations.py
[modify] https://crrev.com/b0135d6afd0d12f1be4ede852ae15e751941b389/testing/buildbot/chromium.gpu.fyi.json

Comment 3 by cblume@chromium.org, May 14 2016

Blockedon: 611930
Cc: j.iso...@samsung.com
Status: Available (was: Untriaged)

Comment 6 by kbr@chromium.org, Feb 3 2017

Status: WontFix (was: Available)
The gpu_process test failures were addressed in  Issue 611930 . The Maps test failure was fixed a while ago and it's running successfully on this bot. Closing as WontFix - no longer applicable.

Sign in to add a comment