trial run of vs2013 with iterator debugging off to see if browser_tests are timing-related

BUG=

Review URL: https://codereview.chromium.org/165693005

git-svn-id: http://src.chromium.org/svn/trunk/src/build@252837 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This commit is contained in:
scottmg@chromium.org 2014-02-23 04:30:43 +00:00
Родитель de9fb55579
Коммит e39449f467
2 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -2054,7 +2054,7 @@
# instead of O(N*logN). This is particularly slow under memory
# tools like ThreadSanitizer so we want it to be disablable.
# See http://msdn.microsoft.com/en-us/library/aa985982(v=VS.80).aspx
'win_debug_disable_iterator_debugging%': '0',
'win_debug_disable_iterator_debugging%': '1',
# An application manifest fragment to declare compatibility settings for
# 'executable' targets. Ignored in other target type.

Просмотреть файл

@ -458,7 +458,7 @@ if __name__ == '__main__':
vs2013_runtime_dll_dirs = None
# TODO(scottmg): Temporarily default to off, see http://crbug.com/345993.
depot_tools_win_toolchain = \
bool(int(os.environ.get('DEPOT_TOOLS_WIN_TOOLCHAIN', '0')))
bool(int(os.environ.get('DEPOT_TOOLS_WIN_TOOLCHAIN', '1')))
if sys.platform in ('win32', 'cygwin') and depot_tools_win_toolchain:
import find_depot_tools
depot_tools_path = find_depot_tools.add_depot_tools_to_path()