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

Issue 870336 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 863767



Sign in to add a comment

Ensure test paths on android-go-perf builder are monitored

Project Member Reported by nednguyen@chromium.org, Aug 2

Issue description

I haven't found any regressions on android-go-perf recently on perf dashboard. We need to ensure that all test paths that are monitored on usual android configs are also monitored here.

Can someone from perf dashboard team helps checking this?
 
Blocking: 863767
Cc: simonhatch@chromium.org
+simonhatch FYI

Alerted test paths look like e.g.:

ChromiumPerf/*/system_health.memory_mobile/memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/*/*

which should also match alerts coming from the android-go-perf bot.

I did just have a look and found a few alerts on that bot already, e.g.:
https://chromeperf.appspot.com/group_report?bug_id=870632 has one alert from android-go-perf.

So I guess all is working as intended?
Status: WontFix (was: Untriaged)
Thanks Juan for the verification!

Sign in to add a comment