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

Issue 737740 link

Starred by 1 user
Status: Assigned
Owner:
chanli@chromium.org
Cc:
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
st...@chromium.org
liaoyuke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----

Blocked on:
issue 737769
issue 737772


Sign in to add a comment

Notification extremely late, making it useless

Project Member Reported by mmenke@chromium.org, Jun 28 2017 
Detail is https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzhkODkwYWIzM2VhODBjNWE0YjkwM2Y3NzE3Yzc3MDQzNTI1MDg4YWIM

I reverted a CL to fix the failures a day ago.  Sending an email about a find-it result ~23 hours after the issue was fixed on trunk seems like a waste of developer time.

Comment 1 by chanli@chromium.org, Jun 28 2017 

Thank you so much for reporting this bug to us.

I have checked and it seems that for some reason one of the pipeline took much longer time than we expected. I'll file a separate bug for the issue.

And also we need to consider to only send notifications if the failure happened within certain period.

Comment 2 by chanli@chromium.org, Jun 28 2017

Blockedon: 737772 737769

Comment 3 by mmenke@chromium.org, Jun 28 2017

Summary: Notification extremely late, making it useless (was: Wrongly blame 482746)
Oops, forgot to update the description when I filed this.

Comment 4 by robert...@chromium.org, Oct 2 2017

Labels: Pri-2
Setting priority for visibility.

This was a while ago, but seems important.

chanli@, you commented last on this bug, what should we do with it?

Comment 5 by st...@chromium.org, Oct 2 2017

Labels: Test notification
Owner: chanli@chromium.org
Status: Assigned (was: Available)
Assigned to Chan as this is related to test and also the notification pipeline.

Comment 6 by st...@chromium.org, Oct 2 2017 

IIRC, we have a check on the time gap between when the build failed and when the culprit is found. There might be a bug somewhere around this.
►

Sign in to add a comment