Issue metadata
Sign in to add a comment
|
77.7% regression in cc_perftests at 408770:408842 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005542152805555040
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005521142694710368
,
Aug 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005430001034588560
,
Aug 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004789868799973424
,
Aug 9 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1961 Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Aug 16 2016
Bisect failed; only one alert; appears recovered. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Aug 1 2016