Set linux_chromium_headless_rel CQ experiment at 100%

infra/config/cq.cfg

 # See http://luci-config.appspot.com/schemas/projects/refs:cq.cfg for the
 # documentation of this file format.
 
 version: 1
 cq_name: "chromium"
 cq_status_url: "https://chromium-cq-status.appspot.com"
 commit_burst_delay: 60
 max_commit_burst: 2
 target_ref: "refs/pending/heads/master"
 
@@ skipping 36 matching lines @@
       builders { name: "linux_chromium_asan_rel_ng" }
       # TODO(dpranke): reenable ASAP; see crbug.com/669297.
       #builders { name: "linux_chromium_chromeos_compile_dbg_ng" }
       builders { name: "linux_chromium_chromeos_ozone_rel_ng" }
       builders { name: "linux_chromium_chromeos_rel_ng" }
       # TODO(dpranke): reenable ASAP; see crbug.com/669297.
       #builders { name: "linux_chromium_clobber_rel_ng" }
       builders { name: "linux_chromium_compile_dbg_ng" }
       builders {
         name: "linux_chromium_headless_rel"
-        experiment_percentage: 10
+        experiment_percentage: 100

[Sami, 2016/12/20 14:52:09]

Is this equivalent to just removing experiment_percentage?

[Paweł Hajdan Jr., 2016/12/20 16:19:52]

Nope. A 100% experiment is still an experiment. It doesn't block CQ.

       }
       builders { name: "linux_chromium_rel_ng" }
     }
     buckets {
       name: "master.tryserver.chromium.mac"
       builders { name: "ios-device" }
       builders { name: "ios-device-xcode-clang" }
       builders { name: "ios-simulator" }
       builders { name: "ios-simulator-xcode-clang" }
       builders { name: "mac_chromium_compile_dbg_ng" }
@@ skipping 15 matching lines @@
       builders { name: "win_clang" }
     }
   }
 
 # NOTE: when adding new configs to the commit queue, please contact
 # chrome-eng-review per
 # https://sites.google.com/a/chromium.org/dev/developers/testing/chromium-build-infrastructure/tour-of-the-chromium-buildbot?pli=1#TOC-Adding-new-build-configurations-and-tests-to-the-main-Chromium-waterfall-Commit-Queue
 
   sign_cla {}
 }