Another one?

testScreenshotActionReporting,
testScreenshotNumberReportingOne and
testScreenshotNumberReportingTwo are all flaky.

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

commit b81908f9760b608c9cf5f06355442b3304a0adc2
Author: Henrik Boström <hbos@chromium.org>
Date: Tue Nov 06 12:23:19 2018

Disable flaky ScreenshotTabObserverTest tests.

TBR=petewil@chromium.org, jianli@chromium.org, dtrainor@chromium.org, isherman@chromium.org
NOTRY=True

Bug:  901856 
Change-Id: I61b14dca18356bb71618150795cddc7cce016574
Reviewed-on: https://chromium-review.googlesource.com/c/1318911
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605659}
[modify] https://crrev.com/b81908f9760b608c9cf5f06355442b3304a0adc2/chrome/android/javatests/src/org/chromium/chrome/browser/feature_engagement/ScreenshotTabObserverTest.java

With the tests disabled, removing sheriff label.

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

commit d0700345be456a942b35884bd832e9bca7e8c7ec
Author: Henrik Boström <hbos@chromium.org>
Date: Tue Nov 06 13:16:24 2018

Revert "Disable flaky ScreenshotTabObserverTest tests."

This reverts commit b81908f9760b608c9cf5f06355442b3304a0adc2.

Reason for revert: @DisabledTest: Cannot find symbol, oops.

Original change's description:
> Disable flaky ScreenshotTabObserverTest tests.
> 
> TBR=petewil@chromium.org, jianli@chromium.org, dtrainor@chromium.org, isherman@chromium.org
> NOTRY=True
> 
> Bug:  901856 
> Change-Id: I61b14dca18356bb71618150795cddc7cce016574
> Reviewed-on: https://chromium-review.googlesource.com/c/1318911
> Reviewed-by: Henrik Boström <hbos@chromium.org>
> Commit-Queue: Henrik Boström <hbos@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605659}

TBR=isherman@chromium.org,petewil@chromium.org,dtrainor@chromium.org,jianli@chromium.org,hbos@chromium.org

Change-Id: I6ed97b424d0a649d7f02fd17a0569b6bd64f9069
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug:  901856 
Reviewed-on: https://chromium-review.googlesource.com/c/1318913
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605664}
[modify] https://crrev.com/d0700345be456a942b35884bd832e9bca7e8c7ec/chrome/android/javatests/src/org/chromium/chrome/browser/feature_engagement/ScreenshotTabObserverTest.java

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

commit 5a8f1c590008701d1be20a9df9e5db1083251b47
Author: Henrik Boström <hbos@chromium.org>
Date: Tue Nov 06 13:27:46 2018

Disable flaky ScreenshotTabObserverTest tests (retry).

TBR=petewil@chromium.org, jianli@chromium.org, dtrainor@chromium.org, isherman@chromium.org
NOTRY=True

Bug:  901856 
Change-Id: Icea45c9f384c1ad4a46e24a9fb4ee947a1b57a53
Reviewed-on: https://chromium-review.googlesource.com/c/1319593
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605665}
[modify] https://crrev.com/5a8f1c590008701d1be20a9df9e5db1083251b47/chrome/android/javatests/src/org/chromium/chrome/browser/feature_engagement/ScreenshotTabObserverTest.java

org.chromium.chrome.browser.feature_engagement.ScreenshotTabObserverTest#testScreenshotNumberReportingOne is flaky.

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

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%20org.chromium.chrome.browser.feature_engagement.ScreenshotTabObserverTest#testScreenshotNumberReportingOne&comment=Link%20to%20flake%20occurrences%3A%20https://findit-for-me.appspot.com/flake/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVylQELEgVGbGFrZSKJAWNocm9taXVtQGNocm9tZV9wdWJsaWNfdGVzdF9hcGtAb3JnLmNocm9taXVtLmNocm9tZS5icm93c2VyLmZlYXR1cmVfZW5nYWdlbWVudC5TY3JlZW5zaG90VGFiT2JzZXJ2ZXJUZXN0I3Rlc3RTY3JlZW5zaG90TnVtYmVyUmVwb3J0aW5nT25lDA

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

Mark Fixed since Findit notice is false alarm.

The test disabling patch[1] at #c9 is merged at
 Nov 6, 10:27PM
The findit pointed build is done at
 Nov 6, 8:27PM


[1] http://crrev.com/c/1319593 
Disable flaky ScreenshotTabObserverTest tests (retry).