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

Issue 718481 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 718171
Owner: ----
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

page_cycler_v2.typical_25 is failing on CrOS

Project Member Reported by laszio@chromium.org, May 4 2017

Issue description

This will block master-chromium-pfq. I'm trying to reproduce it locally, but feel that I should loop people who may know what's going on as early as possible.

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/115679093-chromeos-test/chromeos4-row12-rack9-host15/telemetry_AFDOGenerate/debug/


05/04 00:24:06.520 DEBUG|             utils:0202| Running 'ssh 100.115.219.130 python /home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/tools/perf/run_benchmark --verbose --browser=cros-chrome --output-format=chartjson --output-dir=/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src --remote=chromeos4-row12-rack9-host15 --pageset-repeat=1 page_cycler_v2.typical_25'
05/04 00:40:22.096 DEBUG|  telemetry_runner:0285| Error occurred executing.
05/04 00:40:22.098 DEBUG|  telemetry_runner:0291| Completed with exit code: 47.
stdout:[ RUN      ] http://www.nick.com/games@{'cache_temperature': 'pcv1-cold'}
[ RUN      ] /tmp/tmpD4lgjs.html
[       OK ] /tmp/tmpD4lgjs.html (6420 ms)
[       OK ] http://www.nick.com/games@{'cache_temperature': 'pcv1-cold'} (40897 ms)
[ RUN      ] http://www.nick.com/games@{'cache_temperature': 'pcv1-warm'}
Traceback (most recent call last):
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 81, in _RunStoryAndProcessErrorIfNeeded
    state.WillRunStory(story)
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 221, in WillRunStory
    self.browser.tabs[-1].Close()
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/telemetry/telemetry/internal/browser/tab.py", line 100, in Close
    self._tab_list_backend.CloseTab(self.id)
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/tab_list_backend.py", line 67, in CloseTab
    py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5)
  File "/home/chromeos-test/images/chell-chrome-pfq/R60-9520.0.0-rc1/telemetry_src/src/third_party/catapult/common/py_utils/py_utils/__init__.py", line 132, in WaitFor
    (timeout, GetConditionString()))
TimeoutException: Timed out while waiting 5s for py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5).
 
Seems like some sort of renderer crash to me. I would try to find the chrome stack
Mergedinto: 718171
Status: Duplicate (was: Untriaged)
Project Member

Comment 3 by bugdroid1@chromium.org, May 11 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/df28fe6bcfa0fa1f856f51a7c8fb41c5b42c9823

commit df28fe6bcfa0fa1f856f51a7c8fb41c5b42c9823
Author: Ting-Yuan Huang <laszio@google.com>
Date: Thu May 11 22:04:17 2017

afdo: temporarily extend the timeout to 21 days.

BUG= chromium:718481 
TEST=none

Change-Id: I36bc77b19421af95ca2741a5ea6fe0e59fbecdcc
Reviewed-on: https://chromium-review.googlesource.com/503594
Commit-Queue: Ting-Yuan Huang <laszio@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>
Trybot-Ready: Ting-Yuan Huang <laszio@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>

[modify] https://crrev.com/df28fe6bcfa0fa1f856f51a7c8fb41c5b42c9823/cbuildbot/afdo.py

Project Member

Comment 4 by bugdroid1@chromium.org, May 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/484ca45f35335d3bbee1b08295d20545947791b0

commit 484ca45f35335d3bbee1b08295d20545947791b0
Author: Ting-Yuan Huang <laszio@chromium.org>
Date: Mon May 15 17:46:44 2017

Revert "afdo: temporarily extend the timeout to 21 days."

This reverts commit df28fe6bcfa0fa1f856f51a7c8fb41c5b42c9823.

Reason for revert: 718952 is fixed.

Original change's description:
> afdo: temporarily extend the timeout to 21 days.
> 
> BUG= chromium:718481 
> TEST=none
> 
> Change-Id: I36bc77b19421af95ca2741a5ea6fe0e59fbecdcc
> Reviewed-on: https://chromium-review.googlesource.com/503594
> Commit-Queue: Ting-Yuan Huang <laszio@chromium.org>
> Tested-by: Ting-Yuan Huang <laszio@chromium.org>
> Trybot-Ready: Ting-Yuan Huang <laszio@chromium.org>
> Reviewed-by: James Cook <jamescook@chromium.org>
> 

BUG= chromium:718481 

Change-Id: I17f30e01b766d244f2043fdce26c99bd0f3a8ce3
Reviewed-on: https://chromium-review.googlesource.com/503431
Reviewed-by: James Cook <jamescook@chromium.org>
Tested-by: Ting-Yuan Huang <laszio@chromium.org>

[modify] https://crrev.com/484ca45f35335d3bbee1b08295d20545947791b0/cbuildbot/afdo.py

Sign in to add a comment