Re-enable tests for Non-SFI NaCl

chrome/test/nacl/nacl_browsertest_util.h

Index: chrome/test/nacl/nacl_browsertest_util.h
diff --git a/chrome/test/nacl/nacl_browsertest_util.h b/chrome/test/nacl/nacl_browsertest_util.h
index 5b7a5dd0e7e38c063a00ffd17056138f98a5232b..3e5859d6f3bfc1d31e04db42a2cc544852d5ed67 100644
--- a/chrome/test/nacl/nacl_browsertest_util.h
+++ b/chrome/test/nacl/nacl_browsertest_util.h
@@ -196,10 +196,9 @@ class NaClBrowserTestGLibcExtension : public NaClBrowserTestGLibc {
 
 // Similar to MAYBE_NONSFI, this is available only on x86-32, x86-64 or
 // ARM linux.
-// TODO(crbug.com/579804) -- tests disabled on Linux for flakiness.
 #if defined(OS_LINUX) && \
     (defined(ARCH_CPU_X86_FAMILY) || defined(ARCH_CPU_ARMEL))

[Sam McNally, 2016/10/13 21:11:40]

Given the ASAN bot failures, I'm guessing this needs the sanitizer ifdefs from
above.

[Mark Seaborn, 2016/10/14 19:34:02]

I'm not sure what's going on with those ASAN bot failures, because they're also
showing failures in tests for SFI NaCl (e.g. "PPAPINaClPNaClTest.Core"), not
just Non-SFI NaCl.  And I don't see how this change can be enabling SFI NaCl
tests on ASAN...

[Mark Seaborn, 2016/10/15 00:12:43]

OK, done.
I think that was an unrelated flake, maybe caused by https://crbug.com/633067. 
It went away when I ran the trybot again.

-#  define MAYBE_PNACL_NONSFI(test_case) DISABLED_##test_case
+#  define MAYBE_PNACL_NONSFI(test_case) test_case
 #else
 #  define MAYBE_PNACL_NONSFI(test_case) DISABLED_##test_case
 #endif