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

Issue 910289 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 898693



Sign in to add a comment

Take care of different patchsets caused by rebase and commit-message edit

Project Member Reported by liaoyuke@chromium.org, Nov 29

Issue description

Following cases need to the handled:
1. If two patchsets are only different on commit message, their coverage data should be shared.
2. If two patchsets are only different due to trivial rebasing, their coverage data should be shared as well, though needs rebasing.
3. A special case of 2, whenever a CL lands, a new patchset is automatically created due to rebasing, and it is possible that a file in the CL be changed by another commit landed after the CQ build started and before the CL landed.
 

Sign in to add a comment