New issue
Advanced search Search tips

Issue 722408 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 7
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

loading.desktop failure on chromium.perf at 471206 - 471286

Project Member Reported by altimin@chromium.org, May 15 2017

Issue description

Revision range first seen: https://test-results.appspot.com/revision_range?start=471206&end=471286
Link to failing step log: https://chromium-swarm.appspot.com/user/task/36239d502a472210

Failing bots:
Linux Perf [11 out of the last 11 builds have failed]
Win 10 High-DPI Perf [11 out of the last 11 builds have failed]


If the test is disabled, please downgrade to Pri-2.

 
Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, May 16 2017


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 94b5fe8aa1afc38349e4b0441a35790913905f04
  bad_revision : 897fedad953f7ef4d6d092e3f7ad6d7a34900eea

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : loading.desktop
  Metric       : benchmark_duration/benchmark_duration

Revision             Exit Code      N
chromium@471206      1 +- N/A       20      good
chromium@471246      1 +- N/A       20      good
chromium@471266      1 +- N/A       20      good
chromium@471286      0 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests loading.desktop

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

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


| 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!
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, May 17 2017


=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : loading.desktop
  Metric       : benchmark_duration/benchmark_duration

Revision             Exit Code      N
chromium@471206      1 +- N/A       20      good
chromium@471286      1 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests loading.desktop

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

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


| 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)
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.

Sign in to add a comment