Disable No-compile tests. They are flaky on the tree.

build/nocompile.gypi

 # Copyright (c) 2011 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 file is meant to be included into an target to create a unittest that
 # invokes a set of no-compile tests.  A no-compile test is a test that asserts
 # a particular construct will not compile.
 #
 # Also see:
 #   http://dev.chromium.org/developers/testing/no-compile-tests
@@ skipping 39 matching lines @@
 #
 # Implementation notes:
 # The .nc files are actually processed by a python script which executes the
 # compiler and generates a .cc file that is empty on success, or will have a
 # series of #error lines on failure, and a set of trivially passing gunit
 # TEST() functions on success. This allows us to fail at the compile step when
 # something goes wrong, and know during the unittest run that the test was at
 # least processed when things go right.
 
 {
+  # TODO(awong): Disabled until http://crbug.com/105388 is resolved.
+  'sources/': [['exclude', '\\.nc$']],
   'conditions': [
     [ 'OS=="linux" and clang==0', {
       'rules': [
         {
           'variables': {
             'nocompile_driver': '<(DEPTH)/tools/nocompile_driver.py',
             'nc_result_path': ('<(INTERMEDIATE_DIR)/<(module_dir)/'
                                '<(RULE_INPUT_ROOT)_nc.cc'),
            },
           'rule_name': 'run_nocompile',
@@ skipping 15 matching lines @@
           'message': 'Generating no compile results for <(RULE_INPUT_PATH)',
           'process_outputs_as_sources': 1,
         },
       ],
     }, {
       'sources/': [['exclude', '\\.nc$']]
     }],  # 'OS=="linux" and clang=="0"'
   ],
 }