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

Issue 838617 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
█ abdulsyed@chromium.org
gov...@chromium.org
█ bustamante@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Determine whether crbug/815161 should have been filed automatically

Project Member Reported by sdy@chromium.org, May 1 2018 
Writing a postmortem for crbug/815161, I noticed that this bug was filed by hand and didn't have RBS applied until much later, after stable had already gone out.

Is there or should there be an automated process for filing a crash bug in a case like this?

Comment 1 by sdy@chromium.org, May 1 2018

Components: Internals>CrashReporting
Owner: gov...@chromium.org
Status: Assigned (was: Untriaged)
govind@, you seem like a good initial assignee for this bug, but feel free to reassign it or close it if followup isn't needed here.

Comment 2 by gov...@chromium.org, May 1 2018

Cc: gov...@chromium.org abdulsyed@chromium.org bustamante@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
AFAIK clusterfuzz reports crashes automatically. Other crashes are triaged and reported by test team.

+  abdulsyed@ (Desktop Release TPM) & bustamante@ (Test Lead), to take their input as well.

Comment 3 by kariahda@chromium.org, May 21 2018 

Bulk edit**

This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all.

We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you.
►

Sign in to add a comment