Disable PPAPITest.FileIO on Win too.

This test is also highly flaky on Windows (failed 5/7 recent runs).
http://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%286%29

[3504:128:0527/154657:FATAL:thread_restrictions.cc(38)] Function marked as IO-only was called from a thread that disallows IO!  If this thread really should be allowed to make IO calls, adjust the call to base::ThreadRestrictions::SetIOAllowed() in this thread's startup.
Backtrace:
	base::debug::StackTrace::StackTrace [0x100A9DC1+33]
	logging::LogMessage::~LogMessage [0x101495BE+94]
	base::ThreadRestrictions::AssertIOAllowed [0x102962A6+246]
	base::File::Close [0x10135082+34]
	base::File::~File [0x1011551C+60]
...
	fileapi::FileSystemOperationImpl::DidOpenFile [0x238518A3+179]
...
	fileapi::`anonymous namespace'::RunCreateOrOpenCallback [0x237F9104+180]
...
	base::MessageLoop::RunTask [0x10184201+881]
...
See full stack in http://crbug.com/378046

BUG=377599,378046
TBR=hidehiko@chromium.org,bbudge@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273152 0039d316-1c4b-4281-b951-d872f2087c98

chrome/test/ppapi/ppapi_browsertest.cc

@@ -725,12 +725,12 @@ TEST_PPAPI_OUT_OF_PROCESS(VideoDecoderDev)
 #define MAYBE_FileIO DISABLED_FileIO
 #define MAYBE_FileIO_Private DISABLED_FileIO_Private
 #else
-// Flaky on Mac. http://crbug.com/377599
-# if defined(OS_MACOSX)
+// Flaky on Mac and Win. http://crbug.com/377599
+#if defined(OS_MACOSX) || defined(OS_WIN)
 #define MAYBE_FileIO DISABLED_FileIO
-# else
+#else
 #define MAYBE_FileIO FileIO
-# endif  // defined(OS_MACOSX)
+#endif  // OS_MACOSX || OS_WIN
 #define MAYBE_FileIO_Private FileIO_Private
 #endif