• fdoray's avatar
    Use TaskScheduler instead of WorkerPool in fake_cros_disks_client.cc. · b520619b
    fdoray authored
    The following traits are used:
    
    Priority:
      BACKGROUND
        User won't notice if this task takes an arbitrarily long time
        to complete.
    
      and
    
      Inherited (default)
        The priority is inherited from the calling context (i.e. TaskTraits
        are initialized with the priority of the current task).
    
    Shutdown behavior: CONTINUE_ON_SHUTDOWN
      Tasks posted with this mode which have not started executing before
      shutdown is initiated will never run. Tasks with this mode running at
      shutdown will be ignored (the worker will not be joined).
    
      Note: Tasks that were previously posted to base::WorkerPool should
      use this shutdown behavior because this is how base::WorkerPool
      handles all its tasks.
    
    May Block:
      Tasks posted with MayBlock() may block. This includes but is not
      limited to tasks that wait on synchronous file I/O operations:
      read or write a file from disk, interact with a pipe or a socket,
      rename or delete a file, enumerate files in a directory, etc. This
      trait isn't required for the mere use of locks.
    
    BUG=659191
    
    Review-Url: https://codereview.chromium.org/2601413002
    Cr-Commit-Position: refs/heads/master@{#442074}
    b520619b
disk_mount_manager_unittest.cc 37 KB