[Webkit-unassigned] [Bug 186062] CommitSet range bisector should use commits occur in commit sets which specify the range as valid commits for commits without ordering.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 1 14:36:56 PDT 2018


https://bugs.webkit.org/show_bug.cgi?id=186062

--- Comment #3 from dewei_zhu at apple.com ---
Comment on attachment 341522
  --> https://bugs.webkit.org/attachment.cgi?id=341522
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=341522&action=review

>> Websites/perf.webkit.org/ChangeLog:8
>> +        For commits without ordering, we should use the commits occurs in the commit sets which specify the range as valid commits.
> 
> What do you mean by "the commits occurs in the commit sets"?

Let's say we cannot order commits for WebKit (r100, r102) due to lack of commit time and commit order. Then we should make sure any commit set get chosen, the commit for WebKit should be either r100 or r102.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180601/de94435d/attachment.html>


More information about the webkit-unassigned mailing list