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

Issue 600535 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

crash: Avoid redundant analysis of crashes from Fracas

Project Member Reported by st...@chromium.org, Apr 4 2016

Issue description

Fracas keeps producing crash data for Findit to analyze. However, not all crashes of the same (channel, platform, signature) has to be re-analyzed each time. If the stack trace and regression range do not change, the analysis result will be the same.

We'd better avoid such redundant analysis, and save resource to analyze more crashes in parallel.

Another factor to consider is the Findit version: if we upgrade our algorithm, the result might change even the crash data is the same.

 

Comment 1 by st...@chromium.org, Apr 21 2016

Components: Tools>Test>FindIt
Labels: -Findit
Summary: crash: Avoid redundant analysis of crashes from Fracas (was: Avoid redundant analysis of crashes from Fracas)

Comment 2 by st...@chromium.org, May 26 2016

Blocking: 615262
Currently, if a crash with the same crash identifiers is already analyzed, the  crash won't be analyzed anymore.

However, we need to make Findit smarter. For example, if regression range changes, the crash should be re-analyzed. Or have an expired time for the analysis results.
Status: Started (was: Available)
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 7 2016

Status: Fixed (was: Started)
Blocking: -615262

Sign in to add a comment