Disable WorkerTaskProviderBrowserTest.DestroyedProfile due to flakiness

Bug: 1168407
Change-Id: I5faa426fac6c53e1219dfe3ae7805a2eff26e393
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639499
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Auto-Submit: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845270}

chrome/browser/task_manager/providers/worker_task_provider_browsertest.cc

@@ -330,7 +330,9 @@ IN_PROC_BROWSER_TEST_F(WorkerTaskProviderBrowserTest, CreateExistingTasks) {
 // Tests that destroying a profile while updating will correctly remove the
 // existing tasks. An incognito browser is used because a regular profile is
 // never truly destroyed until browser shutdown (See https://crbug.com/88586).
-IN_PROC_BROWSER_TEST_F(WorkerTaskProviderBrowserTest, DestroyedProfile) {
+// TODO(crbug.com/1168407): Fix the flakiness and re-enable this.
+IN_PROC_BROWSER_TEST_F(WorkerTaskProviderBrowserTest,
+                       DISABLED_DestroyedProfile) {
   StartUpdating();
 
   EXPECT_TRUE(tasks().empty());