New issue
Advanced search Search tips

Issue 705923 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Test bug

Project Member Reported by ehmaldonado@chromium.org, Mar 28 2017

Issue description

Test bug
 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Mar 28 2017


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: staging_win_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/cpu_utilization_gpu


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 webrtc.peerconnection

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983883836992630656

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5842958831583232


| 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!
Status: WontFix (was: Untriaged)

Sign in to add a comment