Issue metadata
Sign in to add a comment
|
Reference builds values go up at close to the same time as test builds but an alert is still sent |
||||||||||||||||||||
Issue descriptionShould I file a bug in catapult for this? I figure I will kick off a bisect just in case.
,
Nov 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963927223885330048
,
Nov 3 2017
,
Nov 3 2017
The larger issue is tracked in https://github.com/catapult-project/catapult/issues/1574
,
Nov 3 2017
Thanks Annie! Since I can't mark duplicate, I will mark ExternalDependency.
,
Nov 3 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : media.desktop Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/video.html?src_tulip2.wav_type_audio Revision Result N chromium@513176 1899582 +- 9729054 21 good chromium@513260 2512605 +- 9734977 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.wav.type.audio media.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963927223885330048 For feedback, file a bug with component Speed>Bisection
,
Jul 10
,
Jul 19
,
Jul 19
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 3 2017