Issue metadata
Sign in to add a comment
|
webrtc failing on chromium.perf/Linux Perf |
||||||||||||||||||
Issue descriptionwebrtc failing on chromium.perf/Linux Perf Builders failed on: - Linux Perf: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf
,
Jun 28 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: linux_perf_bisect Benchmark : webrtc Metric : benchmark_duration/benchmark_duration To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests webrtc Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975532509386934256 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5146716585590784 | 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 Speed>Bisection. Thank you!
,
Jun 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8975524467324656864
,
Jun 28 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: linux_perf_bisect Benchmark : webrtc Metric : benchmark_duration/benchmark_duration To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests webrtc Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8975524467324656864 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5146716585590784 | 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 Speed>Bisection. Thank you!
,
Jun 29 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 10
Archiving issues with no priority, no component and no owner |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 28 2017