Issue metadata
Sign in to add a comment
|
266.9% regression in cc_perftests at 409296:409360 |
||||||||||||||||||
Issue descriptionSee attached graph.
,
Aug 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005318893553578496
,
Aug 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005311050247954128
,
Aug 4 2016
Wont-fixing because this recovered.
,
Aug 4 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005219888249441792
,
Aug 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9004576712132302080
,
Aug 12 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/886 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 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9003308221927450336
,
Aug 26 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/960 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. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by aiolos@chromium.org
, Aug 3 2016