The bisect goes red with no red steps when a culprit cannot be identified. The bug comment is very unclear. We need to make this easier to undersand. Examples: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_arm64_aosp_perf_bisect/builds/441 https://bugs.chromium.org/p/chromium/issues/detail?id=664109#c5 https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_arm64_aosp_perf_bisect/builds/441/steps/Failure%20reason/logs/stdio https://bugs.chromium.org/p/chromium/issues/detail?id=664101#c4 https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_arm64_aosp_perf_bisect/builds/439 https://build.chromium.org/p/tryserver.chromium.perf/builders/android_webview_arm64_aosp_perf_bisect/builds/439/steps/Failure%20reason/logs/stdio https://bugs.chromium.org/p/chromium/issues/detail?id=664103#c5 https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/592 https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/592/steps/Failure%20reason/logs/reason
I will make sure we have a clear message for these cases: "Could not identify a culprit. Low statistical significance." or something like that.
Started https://chromeperf.appspot.com/buildbucket_job_status/8996212596210160880 https://chromeperf.appspot.com/buildbucket_job_status/8996212212840992784 https://chromeperf.appspot.com/buildbucket_job_status/8996212148855302208
+Annie, what do you think about this message? https://bugs.chromium.org/p/chromium/issues/detail?id=664103#c10 I think this is accurate.
Issue 664685 has been merged into this issue.
Marking fixed but will reopen if bug 664480 comes back with a bad result.
Comment 1 by sullivan@chromium.org
, Nov 11 2016