Some "successful" bisects very hard to understand |
||
Issue descriptionExample is the bug comment here: https://bugs.chromium.org/p/chromium/issues/detail?id=664136#c5 The bisect says it is successful, and it appears to blame android-chrome@3320385cb7. But it does not give details about that revision or cc the author. Was the bisect really successful? If so, why wasn't the revision explained? If not, where are the details on why it failed?
,
Nov 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8996212001977832144
,
Nov 14 2016
The refactored bisect has produced the correct output: https://bugs.chromium.org/p/chromium/issues/detail?id=664136#c23 |
||
►
Sign in to add a comment |
||
Comment 1 by robert...@chromium.org
, Nov 11 2016