New issue
Advanced search Search tips

Issue 713036 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

browse:news:globo failing on system health and v8.runtimestats

Project Member Reported by perezju@chromium.org, Apr 19 2017

Issue description

The story has been consistently failing on the android one bot, while running system_health.common_mobile.

Screenshot shows that the tab crashed:
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_10-2017-04-18_16-48-2617173.png

logcat in the logs show ANR's:

	E/ActivityManager(  550): ANR in com.google.process.location
	E/ActivityManager(  550): PID: 9803
	E/ActivityManager(  550): Reason: executing service com.google.android.gms/.common.stats.GmsCoreStatsService
	E/ActivityManager(  550): Load: 15.56 / 14.0 / 10.71
	E/ActivityManager(  550): CPU usage from 3804ms to -15567ms ago:
	E/ActivityManager(  550):   23% 8614/org.chromium.chrome:sandboxed_process0: 20% user + 2.9% kernel / faults: 27220 minor 1171 major
	E/ActivityManager(  550):   12% 550/system_server: 5.9% user + 6.8% kernel / faults: 18481 minor 1661 major
        [...]
	E/ActivityManager(  550): 97% TOTAL: 4.9% user + 23% kernel + 68% iowait
	I/ActivityManager(  550): Killing 9803:com.google.process.location/u0a9 (adj 0): bg anr

A couple of builds with failures:
https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20One%20Perf%20%282%29/6280
https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20One%20Perf%20%282%29/6276

On the nexus5 bot (reported by mythria@ on  issue 694658 ) it seems to be failing waiting for the next article to come up:

  File "/b/c/b/Android_Nexus5_Perf__2_/src/tools/perf/page_sets/system_health/browsing_stories.py", line 75, in _DidLoadDocument
    self._ReadNextArticle(action_runner)
  File "/b/c/b/Android_Nexus5_Perf__2_/src/tools/perf/page_sets/system_health/browsing_stories.py", line 80, in _ReadNextArticle
    action_runner.tab.WaitForDocumentReadyStateToBeComplete()
  File "/b/c/b/Android_Nexus5_Perf__2_/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 "/b/c/b/Android_Nexus5_Perf__2_/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 74, in WaitForDocumentReadyStateToBeComplete
    'document.readyState == "complete"', timeout=timeout)
  File "/b/c/b/Android_Nexus5_Perf__2_/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 "/b/c/b/Android_Nexus5_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_Nexus5_Perf__2_/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 "/b/c/b/Android_Nexus5_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.
https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5_Perf__2_%2F5467%2F%2B%2Frecipes%2Fsteps%2Fv8.runtimestats.browsing_mobile%2F0%2Fstdout

Screenshot:
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_4-2017-04-17_19-16-5650983.png

 
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 19 2017

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

commit 819396e5f75958be68396a85362872a6fa46921a
Author: perezju <perezju@chromium.org>
Date: Wed Apr 19 10:54:40 2017

[tools/perf] Disable browse:news:globo on android

Story is failing on the waterfall.

TBR=nednguyen@google.com,mythria@chromium.org
BUG= 713036 

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

[modify] https://crrev.com/819396e5f75958be68396a85362872a6fa46921a/tools/perf/page_sets/system_health/browsing_stories.py

Any insight why this is not failing on CQ?
I think because we don't have android one on CQ?

Comment 4 by ssid@chromium.org, Apr 19 2017

Hm this just looks like the page takes too long to load and it times out on the One device.
This could be issue 678965
Maybe try to increase the timeout and run some tryjobs on android one?
This was also failing on Nexus 5 for v8.runtimestats.browsing_mobile. It failed consistently, it wasn't flaky. 
Project Member

Comment 8 by bugdroid1@chromium.org, Apr 21 2017

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

commit 8ce14996ccd3915bec8c5507cd0e34c5d651f663
Author: ssid <ssid@chromium.org>
Date: Fri Apr 21 01:20:26 2017

Increase timeout for complete state for globo story

Android One someties takes longer to load.

BUG= 713036 

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

[modify] https://crrev.com/8ce14996ccd3915bec8c5507cd0e34c5d651f663/tools/perf/page_sets/system_health/browsing_stories.py

Comment 9 by ssid@chromium.org, Apr 25 2017

Status: Fixed (was: Untriaged)

Sign in to add a comment