New issue
Advanced search Search tips

Issue 702319 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 7
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

blink_perf.shadow_dom failing on chromium.perf/Android Nexus5X Perf (2)

Project Member Reported by sullivan@chromium.org, Mar 16 2017

Issue description

blink_perf.shadow_dom failing on chromium.perf/Android Nexus5X Perf (2)

Builders failed on: 
- Android Nexus5X Perf (2): 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf%20%282%29


Sample log:
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5X_Perf__2_%2F3340%2F%2B%2Frecipes%2Fsteps%2Fblink_perf.shadow_dom%2F0%2Fstdout

[ RUN      ] v1-slot-append.html
...
INFO:root:*************** BROWSER STANDARD OUTPUT ***************
INFO:root:Cannot get standard output on Android
INFO:root:*********** END OF BROWSER STANDARD OUTPUT ************
INFO:root:********************* BROWSER LOG *********************
INFO:root:No log file
INFO:root:***************** END OF BROWSER LOG ******************
INFO:devil.utils.cmd_helper:[host]> /b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 01e15d4fa2659c8d shell '( /system/bin/screencap -p /data/local/tmp/temp_file-854cb9cab586a.png );echo %$?'
INFO:devil.utils.cmd_helper:[host]> /b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 01e15d4fa2659c8d pull /data/local/tmp/temp_file-854cb9cab586a.png /tmp/tmp9ZahW2.png
INFO:devil.utils.cmd_helper:[host]> /b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 01e15d4fa2659c8d shell 'rm -f /data/local/tmp/temp_file-854cb9cab586a.png'
Traceback (most recent call last):
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 88, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 299, in RunStory
    self._current_page.Run(self)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 108, in Run
    shared_state.page_test.RunNavigateSteps(self, current_tab)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/page/legacy_page_test.py", line 195, in RunNavigateSteps
    page.RunNavigateSteps(action_runner)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 117, in RunNavigateSteps
    url, script_to_evaluate_on_commit=self.script_to_evaluate_on_commit)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py", line 177, in Navigate
    timeout_in_seconds=timeout_in_seconds))
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py", line 56, in _RunAction
    action.RunAction(self._tab)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/actions/navigate.py", line 30, in RunAction
    tab.WaitForFrameToBeDisplayed()
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 103, in WaitForFrameToBeDisplayed
    timeout=timeout)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 191, in WaitForJavaScriptCondition
    return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
    return func(*args, **kwargs)
  File "/b/c/b/Android_Nexus5X_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 294, in WaitForJavaScriptCondition
    e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 90s for IsJavaScriptExpressionTrue.
 
Cc: hayato@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 17 2017

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

commit fcdb00073c9f59874a7b3a728a258ebbc4d74374
Author: sullivan <sullivan@chromium.org>
Date: Fri Mar 17 00:03:54 2017

Disable failing blink_perf.shadow_dom on N5X

BUG= 702319 

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

[modify] https://crrev.com/fcdb00073c9f59874a7b3a728a258ebbc4d74374/tools/perf/benchmarks/blink_perf.py

Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Mar 17 2017


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 8da1ba7c8986319ff64219464f9dc6d86b84da5c
  bad_revision : d489195dc00b8cc61ab89cf4545fe510873183a9

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : ChangingClassName/ChangingClassName

Revision             Exit Code      N
chromium@453486      0 +- N/A       20      good
chromium@453501      0 +- N/A       20      good
chromium@453509      1 +- N/A       20      bad
chromium@453516      1 +- N/A       20      bad
chromium@453545      1 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984938542425801056

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5080420422516736


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 12 2017


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : blink_perf.shadow_dom
  Metric       : ChangingClassName/ChangingClassName

Revision             Exit Code      N
chromium@453486      0 +- N/A       20      good
chromium@453545      1 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982652004545358416

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5080420422516736


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 10 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.

Sign in to add a comment