Disable some dynamic code sandboxing tests with ASan

Windows ASan hotpatches executables and allocates RWX code pages, which
means we can't intercept memmove/memset, which ASan needs.
Reimplementing ASan's interception mechanism to avoid hotpatching is an
extended long term project.

R=pennymac@chromium.org
BUG=805414

Change-Id: I4b05235e5c8abac1055a3ed56a26ca2ba4b7ad22
Reviewed-on: https://chromium-review.googlesource.com/1105513Reviewed-by: Penny MacNeil <pennymac@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568613}

sandbox/win/src/process_mitigations_dyncode_unittest.cc

@@ -406,6 +406,11 @@ TEST(ProcessMitigationsTest, CheckWin81DynamicCodePolicySuccess) {
   if (base::win::GetVersion() < base::win::VERSION_WIN8_1)
     return;
 
+// TODO(crbug.com/805414): Windows ASan hotpatching requires dynamic code.
+#if defined(ADDRESS_SANITIZER)
+  return;
+#endif
+
   base::string16 test_command = L"CheckPolicy ";
   test_command += std::to_wstring(TESTPOLICY_DYNAMICCODE);
 
@@ -487,6 +492,11 @@ TEST(ProcessMitigationsTest, CheckWin10DynamicCodeOptOutPolicySuccess) {
   if (base::win::GetVersion() < base::win::VERSION_WIN10_RS1)
     return;
 
+// TODO(crbug.com/805414): Windows ASan hotpatching requires dynamic code.
+#if defined(ADDRESS_SANITIZER)
+  return;
+#endif
+
   base::string16 test_command = L"CheckPolicy ";
   test_command += std::to_wstring(TESTPOLICY_DYNAMICCODEOPTOUT);