New issue
Advanced search Search tips

Issue 598510 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

Build failure:Pixel.2DCanvasWebGL fails on Android Debug (Nexus 5)

Project Member Reported by horo@chromium.org, Mar 29 2016

Issue description

Build is broken:
pixel_tests

Revision range:
chromium 383572 : 383589

Failing builders:
Android Debug (Nexus 5): https://build.chromium.org/p/chromium.gpu/builders/Android%20Debug%20(Nexus%205)


 
relevant lines:

"""
[ RUN      ] Pixel.2DCanvasWebGL
(INFO) 2016-03-28 19:21:17,193 cmd_helper._ValidateAndLogCommand:153  [host]> /b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 073072040059a5a9 shell '( rm -f /data/local/chrome-trace-config.json );echo %$?'
Traceback (most recent call last):
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/content/test/gpu/gpu_tests/gpu_test_base.py", line 111, in RunStory
    RunStoryWithRetries(GpuSharedPageState, self, results)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/content/test/gpu/gpu_tests/gpu_test_base.py", line 72, in RunStoryWithRetries
    super(cls, shared_page_state).RunStory(results)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 338, in RunStory
    self._current_page, self._current_tab, results)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/content/test/gpu/gpu_tests/pixel.py", line 74, in ValidateAndMeasurePage
    page.test_rect[2] * dpr, page.test_rect[3] * dpr)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/telemetry/telemetry/util/image_util.py", line 111, in Crop
    return impl.Crop(image, left, top, width, height)
  File "/b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/telemetry/telemetry/internal/image_processing/image_util_numpy_impl.py", line 150, in Crop
    raise ValueError('Invalid dimensions')
ValueError: Invalid dimensions

[  FAILED  ] Pixel.2DCanvasWebGL (1302 ms)
"""

apparently unrelated errors:
"""
 RUN      ] Pixel.ScissorTestWithPreserveDrawingBuffer
(INFO) 2016-03-28 19:21:15,445 cmd_helper._ValidateAndLogCommand:153  [host]> /b/build/slave/Android_Debug__Nexus_5_/build/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 073072040059a5a9 shell '( rm -f /data/local/chrome-trace-config.json );echo %$?'
(INFO) 2016-03-28 19:21:16,417 cloud_storage.Insert:286  Uploading /tmp/tmpdwEK7G.png to gs://chromium-browser-gpu-tests/runs/3c3b1f39801a0fd6308cc4a6b3dc08b5b0066f02_Android_Debug__Nexus_5__telemetry/gen/Pixel_ScissorTestWithPreserveDrawingBuffer_3c3b1f39801a0fd6308cc4a6b3dc08b5b0066f02.png (publicly readable)

Expected exception while running Pixel.ScissorTestWithPreserveDrawingBuffer

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:338
    self._current_page, self._current_tab, results)
  ValidateAndMeasurePage at content/test/gpu/gpu_tests/pixel.py:82
    page.display_name, screenshot, expected_colors, dpr)
  _ValidateScreenshotSamples at content/test/gpu/gpu_tests/cloud_storage_test_base.py:222
    _CompareScreenshotSamples(screenshot, expectations, device_pixel_ratio)
  _CompareScreenshotSamples at content/test/gpu/gpu_tests/cloud_storage_test_base.py:55
    str(actual_color.b) + "]")
Failure: Expected pixel at [1, 1] to be [255, 0, 0] but got [108, 147, 0]
"""
failure-log.txt
47.2 KB View Download
Status: Assigned (was: Available)
It looks like this type of problem happens when we try to crop past the bounds of the image? This test has a slightly larger crop size (400, 400), so maybe it's wider than the android screen?
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 6 2016

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

commit 71f45e21cf7f65aa80389531cdd7c9bfc87f0739
Author: erikchen <erikchen@chromium.org>
Date: Wed Apr 06 18:36:46 2016

Rework Pixel.2DCanvasWebGL to be less than 400px wide.

The test was experiencing the error "Invalid dimensions" on some Android
devices. It's probably because the test was trying to do a screen capture wider
than the dimensions of the phone.

BUG=598510
CQ_INCLUDE_TRYBOTS=tryserver.chromium.win:win_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel

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

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

[modify] https://crrev.com/71f45e21cf7f65aa80389531cdd7c9bfc87f0739/content/test/data/gpu/pixel_canvas2d_webgl.html
[modify] https://crrev.com/71f45e21cf7f65aa80389531cdd7c9bfc87f0739/content/test/gpu/page_sets/pixel_tests.py

Sign in to add a comment