While trying to get in a fix for another flaky test ( Issue 786310 ), this test was observed to fail in this tryjob:
https://ci.chromium.org/buildbot/tryserver.chromium.android/android_n5x_swarming_rel/330697

Log excerpt:
java.lang.AssertionError: expected:<1920.0> but was:<1795.0>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:575)
	at org.junit.Assert.assertEquals(Assert.java:700)
	at org.chromium.android_webview.test.AwLegacyQuirksTest.testTargetDensityDpi(AwLegacyQuirksTest.java:61)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37)


There is an indication from older bugs ( Issue 672382 ) that this might be a bot configuration problem. However, there's another bug against a variant of this test (single-process?), Issue 672461, which has been open for a year.