New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 703138 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: ----



Sign in to add a comment

v8.browsing_desktop_classic on Intel GPU on Mac on Mac-10.11 failing on 2 builders

Project Member Reported by zh...@chromium.org, Mar 20 2017

Issue description

v8.browsing_desktop_classic on Intel GPU on Mac on Mac-10.11 failing on 2 builders

Builders failed on: 
- Mac 10.11 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Mac%2010.11%20Perf
- Mac Retina Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf



 

Comment 1 by zh...@chromium.org, Mar 20 2017

Cc: u...@chromium.org

Comment 3 by zh...@chromium.org, Mar 20 2017

Labels: OS-Linux
Also happening on Linux https://uberchromegw.corp.google.com/i/chromium.perf/builders/Linux%20Perf

Comment 4 by u...@chromium.org, Mar 20 2017

Cc: hablich@chromium.org
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Mar 20 2017

Owner: hablich@chromium.org

=== Auto-CCing suspected CL author hablich@chromium.org ===

Hi hablich@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Test failure found with culprit

Suspected Commit
  Author : hablich
  Commit : c11f641e886c8c1c3fa9c7133452cf8902830411
  Date   : Wed Mar 15 20:21:41 2017
  Subject: [Benchmark] Add variants for V8's classic pipeline

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.browsing_desktop_classic
  Metric       : memory:chrome:renderer_processes:process_count_avg/browse_news/browse_news_cnn

Revision             Exit Code      N
chromium@457179      1 +- N/A       5      good
chromium@457183      1 +- N/A       5      good
chromium@457185      1 +- N/A       5      good
chromium@457186      0 +- N/A       5      bad       <--
chromium@457192      0 +- N/A       5      bad
chromium@457204      0 +- N/A       5      bad
chromium@457229      0 +- N/A       5      bad
chromium@457278      0 +- N/A       5      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 --story-filter=browse.news.cnn v8.browsing_desktop_classic

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

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


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

Comment 6 by zh...@chromium.org, Mar 20 2017

hablich, can you check if there is a quick fix or it needs to be reverted?
Friendly Perfbot Sheriff ping.
Cc: rnep...@chromium.org
Looks like there is no quick fix, we should probably disable this benchmark where it is failing. Randy, as perfbot sheriff, are you able to do that?

Sign in to add a comment