Flake Analysis attempts unrelated revisions during bisect after looking back |
|
Issue descriptionhttps://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVy1QELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCKeAWNocm9taXVtLm1lbW9yeS9MaW51eCBDaHJvbWl1bU9TIE1TYW4gVGVzdHMvNzE3MC9pbnRlcmFjdGl2ZV91aV90ZXN0cy9SRzkzYm14dllXUk9iM1JwWm1sallYUnBiMjVVWlhOMExsTnBiWFZzZEdGdVpXOTFjMGx1WTI5bmJtbDBiMEZ1WkU1dmNtMWhiRVJ2ZDI1c2IyRmtjdz09DAsSE01hc3RlckZsYWtlQW5hbHlzaXMYAQw in the above example, the look back algorithm identified 558333 and 558284 as the suspected range, and decided to start bisect in that range. The first position to bisect should be (558333 + 558284) / 2 = 558308, however, there is also a data point with revision: 558332, which is greater than 558308. So, 558332 should not be attempted at all. |
|
►
Sign in to add a comment |
|