New issue
Advanced search Search tips

Issue 753768 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Lots of stories are flaky on system_health.memory_mobile

Project Member Reported by charliea@chromium.org, Aug 9 2017

Issue description

Revision range first seen: ??????

The logs seem to indicate that the root cause is the browser crashing.

There doesn't seem to be a ton of consistency as to what stories are failing.

http://bit.ly/2wHQMNs
- browse:shopping:avito
- load:news:cnn

http://bit.ly/2wHQDK5
- browse:shopping:avito

http://bit.ly/2wHUIOB
- browse:chrome:newtab

http://bit.ly/2wHBNDr
- load:news:nytimes

http://bit.ly/2wHQ1UG
- browse:news:qq

http://bit.ly/2wHN1YD
- browse:social:twitter

I'm not really sure how to approach these failures: they seem wide ranging, but are causing quite a few failures on the Android waterfalls.
 
Just had a look at this. It's true that stories flake every now and then, but there are no consistent failure patterns. Recent failures on each (config, story) pair show:

                    config                        story               history
0           android-nexus6        browse:social:twitter  ----1------1---??---
1           android-nexus5             load:news:reddit  -1---?----------~~~-
2           android-nexus5          load:games:spychase  -?-1-?----------~~~-
3  android-nexus5x-webview     background:search:google  --~-?1--------------
4              android-one     browse:social:tumblr_inf  -----1--------~~~~~~
5          android-nexus5x  browse:social:pinterest_inf  -------1?-----?-?-?-
6           android-nexus6        browse:shopping:avito  ----------------2---
7   android-nexus6-webview              load:news:irctc  ----~-----~1-~~~~~~~
8           android-nexus6            load:search:yahoo  ---------------1?---
9           clankium-phone        browse:chrome:omnibox  --------------~--1--

Key:
'-': Story ran OK
'~': Story did not run (e.g. was disabled)
'?': Benchmark got interrupted, story did not run
'1', '2', ..: Number of times the story failed

Also failure rate for all system health story runs is now at 0.1%, pretty good in fact!

Of course we run hundreds of stories per benchmark so, even this small failure rate can translate to seeing ~10% of system health runs in the waterfall painted red.

Hoping flakiness dashboard will make it easier to assess the current situation.
Status: WontFix (was: Assigned)

Sign in to add a comment