Make chromium.perf waterfall use official builds on Win.

masters/master.chromium.perf/master.cfg

 # -*- python -*-
 # ex: set syntax=python:
 
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This is the buildmaster config file for the 'chromium' bot. It must
 # be installed as 'master.cfg' in your buildmaster's base directory
 # (although the filename can be changed with the --basedir option to
@@ skipping 212 matching lines @@
 
 chromium_perf_linux_archive = master_config.GetGSUtilUrl('chrome-perf',
                                                          'Linux Builder')
 
 chromium_perf_mac_archive = master_config.GetGSUtilUrl('chrome-perf',
                                                        'Mac Builder')
 
 # The identifier of the factory is the build configuration. If two factories
 # are using the same build configuration, they should have the same identifier.
 
-FFMPEG_GYP_DEFINES_WIN = (
-  'fastbuild=1 '
-  'ffmpeg_branding=Chrome '

[ghost stip (do not use), 2013/11/13 19:57:17]

do we not need this, as the chromium.chrome builds don't have it either?

[tonyg, 2013/11/13 20:15:51]

An official build implies these codecs, so they can be removed.

-  'proprietary_codecs=1 '
-)
+# BuilderTesters using a custom build configuration.
+f_cr_rel_builder = F_WIN(
+    slave_type='Builder',
+    mode='google_chrome',
+    compile_timeout=4800,
+    project='all.sln;chromium_builder_perf',
+    factory_properties={
+      'create_profiles': True,
+      'trigger': 'winrel',
+      'gclient_env': {
+        'GYP_DEFINES': 'branding=Chrome component=static_library'},
+      'build_url': chromium_perf_archive,},
+    )
 
-# BuilderTesters using a custom build configuration.
-f_cr_rel_builder = F_WIN(slave_type='Builder',
-                         options=[
-                             '--build-tool=ninja', 'chromium_builder_perf'],
-                         factory_properties={
-                            'create_profiles': True,
-                            'trigger': 'winrel',
-                            'gclient_env': {
-                                'GYP_DEFINES': FFMPEG_GYP_DEFINES_WIN,
-                                'GYP_GENERATORS': 'ninja'},
-                            'build_url': chromium_perf_archive,},
-                         )
-
-f_cr_rel_x64_builder = F_WIN(slave_type='Builder',
-                             options=[
-                                 '--build-tool=ninja', 'chromium_builder_perf'],
-                             target='Release_x64',
-                             factory_properties={
-                                'create_profiles': True,
-                                'trigger': 'winrel_x64',
-                                'gclient_env': {
-                                    'GYP_DEFINES': (FFMPEG_GYP_DEFINES_WIN +
-                                        'component=shared_library '

[tonyg, 2013/11/13 16:16:25]

I'm not sure why this was a shared_library before. If we ship 64 bit chromes on
win, would they be static or shared?

[jschuh, 2013/11/13 18:15:50]

They should be static for performance tests. We were just trying to cut cycle
times since the link is slow.

[tonyg, 2013/11/13 20:15:51]

Great, thanks for confirming.

-                                        'target_arch=x64'),
-                                    'GYP_GENERATORS': 'ninja'},
-                                    'GYP_MSVS_VERSION': '2012',

[tonyg, 2013/11/13 16:16:25]

I assume this is necessary for 64 bit builds and shipping 64-bit chromes would
use 2012?

[jschuh, 2013/11/13 18:15:50]

Oddly enough, early versions of VS can't even build x64 Chrome with WPO. They
either crash or have codegen errors.

[jschuh, 2013/11/13 18:17:28]

Sorry, that should have been "earlier". Point being that only VS 2012 update 3
can actually build x64 Chrome at all.

[tonyg, 2013/11/13 20:15:51]

OK

-                                'build_url': chromium_perf_x64_archive,},
-                             )
+f_cr_rel_x64_builder = F_WIN(
+    slave_type='Builder',
+    mode='google_chrome',
+    compile_timeout=4800,
+    project='all.sln;chromium_builder_perf',
+    target='Release_x64',
+    factory_properties={
+      'create_profiles': True,
+      'trigger': 'winrel_x64',
+      'gclient_env': {
+        'GYP_DEFINES':
+          'branding=Chrome component=static_library target_arch=x64',

[jschuh, 2013/11/13 18:15:50]

Dumb question from me. Is it branding=Chrome or buildtype=Official that triggers
WPO?

[tonyg, 2013/11/13 20:15:51]

Good question. From common.gypi, it seems like you need both. But I thought I
was copying this from the right place. Is there another, more canonical
master.cfg I should copy from?

[tonyg, 2013/11/14 02:35:29]

James or Scott, do you guys know?

+        'GYP_MSVS_VERSION': '2012',},
+      'build_url': chromium_perf_x64_archive,},
+    )
 
 f_cr_rel_perf_xp_1 = F_WIN(slave_type='Tester',
                            build_url=chromium_rel_archive,
                            tests=['page_cycler_bloat',
                                   'page_cycler_morejs',
                                   'page_cycler_intl_ar_fa_he',
                                   'page_cycler_intl_es_fr_pt-BR',
                                   'page_cycler_intl_hi_ru',
                                   'page_cycler_intl_ja_zh',
                                   'dom_perf',
@@ skipping 1117 matching lines @@
 c['projectName'] = ActiveMaster.project_name
 c['projectURL'] = config.Master.project_url
 
 # the 'buildbotURL' string should point to the location where the buildbot's
 # internal web server (usually the html.Waterfall page) is visible. This
 # typically uses the port number set in the Waterfall 'status' entry, but
 # with an externally-visible host name which the buildbot cannot figure out
 # without some help.
 
 c['buildbotURL'] = 'http://build.chromium.org/p/chromium.perf/'