GitLab

Recent Finch data has indicated a large percentage of failing overlays.
In order to better understand why these overlays might be failing we add
a new fail enum that indicates that the overlay candidate failure was
a deliberate act by prioritization.

Also included in this cl is a minor fix for a specific case with low
latency surfaces. Some low latency surfaces (eg Ink) do not change
content Ids even when the pixel data changes. We now detect these
content changes by testing for a valid surface damage index. If the
surface has a damage index we can assume that the content has
changed.



Change-Id: I00b7015ee78a952105c7107eb4cedaf798f88b12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2614860Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Peter McNeeley <petermcneeley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#842996}