Detected 3 new flakes for test/step "org.chromium.chrome.browser.widget.ScrimTest#testOmniboxScrim". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySAsSBUZsYWtlIj1vcmcuY2hyb21pdW0uY2hyb21lLmJyb3dzZXIud2lkZ2V0LlNjcmltVGVzdCN0ZXN0T21uaWJveFNjcmltDA. This message was posted automatically by the chromium-try-flakes app.

sheriff triaging to twellington@ 

disable cl -> https://chromium-review.googlesource.com/1189263

java.lang.AssertionError: The scrim alpha should not be 0.
Expected: a value less than <0.0F>
     but: <0.0F> was equal to <0.0F>
	at org.hamcrest.MatcherAssert.assertThat(PG:20)
	at org.junit.Assert.assertThat(PG:956)
	at org.chromium.chrome.browser.widget.ScrimTest.testOmniboxScrim(PG:154)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:515)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(PG:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(PG:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(PG:52)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(PG:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(PG:26)
	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(PG:37)
	at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(PG:116)
	at android.support.test.internal.statement.UiThreadStatement.evaluate(PG:55)
	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(PG:270)
	at org.junit.rules.ExternalResource$1.evaluate(PG:48)
	at org.junit.rules.RunRules.evaluate(PG:20)
	at org.junit.runners.ParentRunner.runLeaf(PG:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(PG:78)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(PG:237)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(PG:48)
	at org.junit.runners.ParentRunner$3.run(PG:290)
	at org.junit.runners.ParentRunner$1.schedule(PG:71)
	at org.junit.runners.ParentRunner.runChildren(PG:288)
	at org.junit.runners.ParentRunner.access$000(PG:58)
	at org.junit.runners.ParentRunner$2.evaluate(PG:268)
	at org.junit.runners.ParentRunner.run(PG:363)
	at org.chromium.base.test.BaseJUnit4ClassRunner.run(PG:220)
	at org.junit.runners.Suite.runChild(PG:128)
	at org.junit.runners.Suite.runChild(PG:27)
	at org.junit.runners.ParentRunner$3.run(PG:290)
	at org.junit.runners.ParentRunner$1.schedule(PG:71)
	at org.junit.runners.ParentRunner.runChildren(PG:288)
	at org.junit.runners.ParentRunner.access$000(PG:58)
	at org.junit.runners.ParentRunner$2.evaluate(PG:268)
	at org.junit.runners.ParentRunner.run(PG:363)
	at org.junit.runner.JUnitCore.run(PG:137)
	at org.junit.runner.JUnitCore.run(PG:115)
	at android.support.test.internal.runner.TestExecutor.execute(PG:59)
	at android.support.test.runner.AndroidJUnitRunner.onStart(PG:262)
	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(PG:125)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

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

commit 879cc7e4cf4ee1edbe0dbfa86dda5ebf72abd9e4
Author: Trent Apted <tapted@chromium.org>
Date: Mon Aug 27 04:38:33 2018

Disable flaky org.chromium.chrome.browser.widget.ScrimTest#testOmniboxScrim

TBR=twellington@chromium.org

Bug: 877774
Change-Id: I868883a6a4b841dd6b3a94df813e8da23cc6887c
Reviewed-on: https://chromium-review.googlesource.com/1189263
Commit-Queue: Trent Apted <tapted@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586193}
[modify] https://crrev.com/879cc7e4cf4ee1edbe0dbfa86dda5ebf72abd9e4/chrome/android/javatests/src/org/chromium/chrome/browser/widget/ScrimTest.java

The try flakes page isn't showing flakes before 8/23.. the flakiness dashboard is showing quite a bit of flakiness before then that appears to have started the day prior.

e.g. it failed 2/3 on this test run on 8/22: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/KitKat%20Phone%20Tester%20%28dbg%29/8918

It's possible this failure started when I enabled Modern in https://chromium-review.googlesource.com/c/chromium/src/+/1183684.


Matt, will you please take a look?