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

Issue 605762 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 669732



Sign in to add a comment

crash: ignore refactoring CLs

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

Issue description

Refactoring CLs usually touched a lot of files without functional change. We should not blame such CLs for a crash.

One special case is adding/modifying a comment.
 

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

Blocking: 605783

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

Blocking: -605783 615262

Comment 3 by st...@chromium.org, Aug 22 2016

Cc: -kateso...@chromium.org wrengr@chromium.org mbarbe...@chromium.org infe...@chromium.org
Owner: kateso...@chromium.org
Status: Assigned (was: Available)
Blocking: -615262
Blocking: 669732

Comment 6 by st...@chromium.org, Apr 24 2017

Components: -Tools>Test>FindIt Tools>Test>Predator
Example of a case where this is causing trouble: https://bugs.chromium.org/p/chromium/issues/detail?id=733160#c7

Comment 8 by st...@chromium.org, Oct 4 2017

Labels: -Pri-2 Pri-1
We can probably look for simple keywords in the first line of the CL description (such as "rename") and ignore based on that as a short-term fix. We can expand on it if we see more issues later.
I do have concerns about this approach, people may rename things and make functional changes together. In this case, we still have 'rename' in the cl description.
Labels: -Type-Bug Type-Feature
In a case like https://bugs.chromium.org/p/chromium/issues/detail?id=778956

We can check each line of the diff, if every line is a comment line, this should be a comment change cl, we should ignore.

This is a easy case for refactoring cls.
Labels: -Pri-1 Pri-2

Sign in to add a comment