New issue
Advanced search Search tips

Issue 690384 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

15.1%-27% regression in speedometer at 448605:448672

Project Member Reported by tebbi@chromium.org, Feb 9 2017

Issue description

See the link to graphs below.
 

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@448604      951.66 +- 128.461       21      good
chromium@448621      935.7 +- 102.746        21      unknown
chromium@448638      927.983 +- 74.7642      21      bad
chromium@448672      933.293 +- 61.0612      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 speedometer

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

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


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

Comment 4 by tebbi@chromium.org, Feb 10 2017

Status: WontFix (was: Untriaged)

Comment 5 by tebbi@chromium.org, Feb 10 2017

Status: Untriaged (was: WontFix)

Comment 6 by tebbi@chromium.org, Feb 13 2017

Status: WontFix (was: Untriaged)
flaky bot

Sign in to add a comment