[fsp] Simplify aborting logic.

chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc

Index: chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc
diff --git a/chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc b/chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc
index 5fff4ba6f2532901524d0e12230425a788f64822..9b18acaa3cbee882fbbce426966bf10937f6c713 100644
--- a/chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc
+++ b/chrome/browser/chromeos/file_system_provider/throttled_file_system_unittest.cc
@@ -160,13 +160,9 @@ TEST_F(FileSystemProviderThrottledFileSystemTest, AbortAfterRun) {
   // The first file is opened, so the opening operation has completed, then
   // aborting it should result in an error. This is tested, as from the queue
   // point of view, the opening task stays in the queue until closing the file.
-  StatusLog abort_log;
-  abort_callback.Run(base::Bind(&LogStatus, &abort_log));
+  abort_callback.Run();
   base::RunLoop().RunUntilIdle();
 
-  ASSERT_EQ(1u, abort_log.size());
-  EXPECT_EQ(base::File::FILE_ERROR_INVALID_OPERATION, abort_log[0]);
-
   // Confirm, that the second task is not executed after a invalid abort of the
   // first one.
   EXPECT_EQ(1u, first_open_log.size());