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

Issue 669933 link

Starred by 1 user
Status: WontFix
Owner:
charliea@chromium.org
Closed: Nov 2016
Cc:
█ alexandermont@chromium.org
dtu@chromium.org
█ rnep...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug



Sign in to add a comment

Lower the amount of time before a data stoppage alert is received for power tests

Project Member Reported by charliea@chromium.org, Nov 30 2016 
Confusingly, it already appears to be set to 1 day (see 1_day.png). However, it took almost 60 hours for a data stoppage alert to be received for https://bugs.chromium.org/p/chromium/issues/detail?id=669088.
1_day.png
120 KB View Download

Comment 1 by charliea@chromium.org, Nov 30 2016

Cc: dtu@chromium.org
dtu@, any idea why this might be?

Comment 2 by charliea@chromium.org, Nov 30 2016

Cc: charliea@google.com

Comment 3 by charliea@chromium.org, Nov 30 2016

Cc: -charliea@google.com

Comment 4 by sullivan@chromium.org, Nov 30 2016

Status: WontFix (was: Assigned)
The data stoppage alerts run on a mapreduce. The mapreduce goes through every test in the datastore, and it doesn't run quickly. 24 hours is a minimum; I don't think it's feasible to guarantee the alert comes in that quickly. I think we need to do something on the bot health side instead of on the dashboard side to alert faster.
►

Sign in to add a comment