All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=621804

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggo-wvwoM


Bot(s) for this bug's original alert(s):

chromium-rel-win7-gpu-nvidia

manually copy and paste bisect results.
 
===== BISECT JOB RESULTS ===== 
Status: started 
 
 
===== TESTED REVISIONS ===== 
Revision Mean Std Dev N Good? 
chromium@399398 44.4496 0.198307 5 good 
chromium@399504 45.2241 0.225718 5 bad 
 
Bisect job ran on: winx64nvidia_perf_bisect 
Bug ID: 621804 
 
Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests image_decoding.image_decoding_measurement 
Test Metric: ImageDecoding_avg/ImageDecoding_avg 
Relative Change: 1.74% 
Score: 0 
 
Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1662 
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009265838653453712 
 
 
Not what you expected? We'll investigate and get back to you! 
https://chromeperf.appspot.com/bad_bisect?try_job_id=5808213933424640 
 
| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq 
| X | for more information addressing perf regression bugs. For feedback, 
| / \ | file a bug with component Tests>AutoBisect. Thank you!

Hum...

https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1662

Exception steps exception wiggling revision chromium@399451.gsutil ls exception wiggling revision chromium@399451.gsutil ls (2) exception wiggling revision chromium@399451.gsutil ls (3) exception wiggling revision chromium@399451.gsutil ls (4) exception wiggling revision chromium@399451.gsutil ls (5) exception wiggling revision chromium@399451.gsutil ls (6) exception wiggling revision chromium@399451.gsutil ls (7) exception wiggling revision chromium@399451.gsutil ls (8) exception wiggling revision chromium@399451.gsutil ls (9) exception wiggling revision chromium@399451.gsutil ls (10) exception wiggling revision chromium@399451.gsutil ls (11) exception wiggling revision chromium@399451.gsutil ls (12) exception wiggling revision chromium@399451.gsutil ls (13) exception wiggling revision chromium@399451.gsutil ls (14) exception wiggling revision chromium@399451.gsutil ls (15) exception wiggling revision chromium@399451.gsutil ls (16) exception wiggling revision chromium@399451.gsutil ls (17) exception wiggling revision chromium@399451.gsutil ls (18) exception wiggling revision chromium@399451.gsutil ls (19) exception wiggling revision chromium@399451.gsutil ls (20) exception wiggling revision chromium@399451.gsutil ls (21) exception wiggling revision chromium@399451.gsutil ls (22) exception wiggling revision chromium@399451.gsutil ls (23) exception wiggling revision chromium@399451.gsutil ls (24) exception wiggling revision chromium@399451.gsutil ls (25) exception wiggling revision chromium@399451.gsutil ls (26) exception working on revision chromium@399451.gsutil ls

So the reason why the results were not reported here seems that the test failed with an exception.
Probably, it's better to update crbug with the reason, an exception happening in the bisect or something.

Anyway, let me set AutoBiset component.

CC: test owner

looks noise