New issue
Advanced search Search tips

Issue 614597 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

"gpu_process_launch_tests (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, May 25 2016

Issue description

"gpu_process_launch_tests (with patch)" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiVncHVfcHJvY2Vzc19sYXVuY2hfdGVzdHMgKHdpdGggcGF0Y2gpDA.



This flaky test/step was previously tracked in  issue 601297 .
 
 Issue 614596  has been merged into this issue.
Project Member

Comment 2 by chromium...@appspot.gserviceaccount.com, May 26 2016

Detected 3 new flakes for test/step "gpu_process_launch_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiVncHVfcHJvY2Vzc19sYXVuY2hfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 3 by suzyh@chromium.org, May 30 2016

Cc: zmo@chromium.org
Components: Internals>GPU>Testing
Labels: -Sheriff-Chromium OS-Windows
Flaking on win_chromium_rel_ng between 24 and 26 May.

GpuProcess.equal_bug_workarounds_in_browser_and_gpu_process failed:
"""
Traceback (most recent call last):
  RunBenchmark at c:\users\chrome~1\appdata\local\temp\runsdnyir\third_party\catapult\telemetry\telemetry\internal\story_runner.py:312
    benchmark.ShouldTearDownStateAfterEachStoryRun())
  Run at c:\users\chrome~1\appdata\local\temp\runsdnyir\third_party\catapult\telemetry\telemetry\internal\story_runner.py:225
    _RunStoryAndProcessErrorIfNeeded(story, results, state, test)
  _RunStoryAndProcessErrorIfNeeded at c:\users\chrome~1\appdata\local\temp\runsdnyir\third_party\catapult\telemetry\telemetry\internal\story_runner.py:84
    state.RunStory(results)
  RunStory at c:\users\chrome~1\appdata\local\temp\runsdnyir\content\test\gpu\gpu_tests\gpu_test_base.py:111
    RunStoryWithRetries(GpuSharedPageState, self, results)
  RunStoryWithRetries at c:\users\chrome~1\appdata\local\temp\runsdnyir\content\test\gpu\gpu_tests\gpu_test_base.py:72
    super(cls, shared_page_state).RunStory(results)
  RunStory at c:\users\chrome~1\appdata\local\temp\runsdnyir\third_party\catapult\telemetry\telemetry\page\shared_page_state.py:332
    self._current_page, self._current_tab, results)
  ValidateAndMeasurePage at c:\users\chrome~1\appdata\local\temp\runsdnyir\content\test\gpu\gpu_tests\gpu_process.py:39
    page.Validate(tab, results)
  Validate at c:\users\chrome~1\appdata\local\temp\runsdnyir\content\test\gpu\page_sets\gpu_process_tests.py:516
    diff = set(browser_list).symmetric_difference(set(gpu_list))
TypeError: 'NoneType' object is not iterable

Locals:
  browser_list : [u'clear_uniforms_before_first_program_use', u'disable_direct_composition', u'disable_discard_framebuffer', u'exit_on_context_lost', u'force_cube_complete', u'scalarize_vec_and_mat_constructor_args', u'texsubimage_faster_than_teximage', u'use_current_program_after_successful_link']
  gpu_list     : None
  results      : <telemetry.internal.results.page_test_results.PageTestResults object at 0x03C0E1B0>
  tab          : <telemetry.internal.browser.tab.Tab object at 0x03C3FF50>
"""

Since this has apparently stopped flaking, I'll remove it from the sheriffing queue.

zmo, you've been active in content/test/gpu/gpu_tests lately. Can you have a look and see if there is any further action to be taken here and/or route it to a more appropriate person?
Project Member

Comment 4 by chromium...@appspot.gserviceaccount.com, May 31 2016

Labels: Sheriff-Chromium
Detected 3 new flakes for test/step "gpu_process_launch_tests (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiVncHVfcHJvY2Vzc19sYXVuY2hfdGVzdHMgKHdpdGggcGF0Y2gpDA. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Comment 5 by guidou@chromium.org, May 31 2016

Labels: -Sheriff-Chromium
Status: WontFix (was: Untriaged)
Lots of things failed during the "3 new flakes", so not specific to gpu_process_launch_tests. No flakes specific to gpu_process_launch_tests in recent builds.

Sign in to add a comment