[fsp] Fix flaky browser test for aborting a write operation.

chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc

Index: chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc
diff --git a/chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc b/chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc
index aadfe74de8ecea8f46b26a0d268e44f6e3393ba0..f6d8141ed1c95a932eb590fcdd0e2c4fed0454a2 100644
--- a/chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc
+++ b/chrome/browser/chromeos/extensions/file_system_provider/file_system_provider_apitest.cc
@@ -114,13 +114,7 @@ IN_PROC_BROWSER_TEST_F(FileSystemProviderApiTest, Truncate) {
       << message_;
 }
 
-// http://crbug.com/426549
-#if defined(OS_CHROMEOS)
-#define MAYBE_WriteFile DISABLED_WriteFile
-#else
-#define MAYBE_WriteFile WriteFile
-#endif
-IN_PROC_BROWSER_TEST_F(FileSystemProviderApiTest, MAYBE_WriteFile) {
+IN_PROC_BROWSER_TEST_F(FileSystemProviderApiTest, WriteFile) {
   ASSERT_TRUE(RunPlatformAppTestWithFlags("file_system_provider/write_file",
                                           kFlagLoadAsComponent))
       << message_;