This test was reported as flaky, but there have not been many occurrences, so I'm not sure it's worth disabling. Unfortunately, I could not analyze it with findit due to a login error (even though I am logged in).

Detected 3 new flakes for test/step "IndexedDBDispatcherHostTest.NotifyIndexedDBContentChanged". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyRAsSBUZsYWtlIjlJbmRleGVkREJEaXNwYXRjaGVySG9zdFRlc3QuTm90aWZ5SW5kZXhlZERCQ29udGVudENoYW5nZWQM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

Taking off queue again. No flakes in ~5 days.

IndexedDBDispatcherHostTest.NotifyIndexedDBContentChanged is flaky.

Findit has detected 3 new flake occurrences of this test. List
of all flake occurrences can be found at:
https://findit-for-me.appspot.com/flake/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyXwsSBUZsYWtlIlRjaHJvbWl1bUBjb250ZW50X3VuaXR0ZXN0c0BJbmRleGVkREJEaXNwYXRjaGVySG9zdFRlc3QuTm90aWZ5SW5kZXhlZERCQ29udGVudENoYW5nZWQM.

Since this test is still flaky, this issue has been moved back onto the Sheriff
Bug Queue if it's not already there.

If the result above is wrong, please file a bug using this link:
https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Detection%20-%20Wrong%20result%20for%20IndexedDBDispatcherHostTest.NotifyIndexedDBContentChanged&comment=Link%20to%20flake%20occurrences%3A%20https://findit-for-me.appspot.com/flake/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyXwsSBUZsYWtlIlRjaHJvbWl1bUBjb250ZW50X3VuaXR0ZXN0c0BJbmRleGVkREJEaXNwYXRjaGVySG9zdFRlc3QuTm90aWZ5SW5kZXhlZERCQ29udGVudENoYW5nZWQM

Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).

disabling: https://chromium-review.googlesource.com/c/chromium/src/+/1246823

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/228c573919e21b2abc08d491cad6bcbeba9f567e

commit 228c573919e21b2abc08d491cad6bcbeba9f567e
Author: Evan Stade <estade@chromium.org>
Date: Wed Sep 26 19:22:28 2018

Disable a test under fuschia

IndexedDBDispatcherHostTest.NotifyIndexedDBContentChanged is flaky.

TBR=dmurph@chromium.org

Bug: 879213
Change-Id: I933e46c2ec3df71920a1f7f809b80c300f19f80c
Reviewed-on: https://chromium-review.googlesource.com/1246823
Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594422}
[modify] https://crrev.com/228c573919e21b2abc08d491cad6bcbeba9f567e/testing/buildbot/filters/fuchsia.content_unittests.filter

The test is failing due to an unexpected call to the |connection_callbacks| IndexedDBDatabaseCallback of one of the TestDatabaseConnections:

  Uninteresting mock function call - returning directly.
      Function call: Abort(2, 28, @0x6cedcd7bb670 Connection is closing.)
  Stack trace:
  ...

I notice that NotifyIndexedDBListChanged was disabled last year because it was also flaky (see issue 772067), though from the bug it's not clear whether the issue was related.

What does "Connection is closing." mean in this context?

I would suggest finding an owner for this issue that has some context and might be able to investigate sooner:
https://cs.chromium.org/chromium/src/content/browser/indexed_db/OWNERS