IssueTracker

All three fixed API 24 trace tests all fail on Shamu but not emulator, both running API 23. May be a subtle difference in behavior between x86 and arm 32, perhaps in trace processor.

Emulator (doesn't fail): Android/sdk_google_phone_x86/generic_x86:6.0/MASTER/6695544:userdebug/test-keys

Shamu (does fail): google/shamu/shamu:6.0.1/MOB31T/3671974:userdebug/dev-keys

Three different problems for the 3 tests using API 24 traces

# cold start not observed at all:
java.lang.AssertionError: expected:<SubMetrics(timeToInitialDisplayNs=264869885, timeToFullDisplayNs=715406822, timelineRangeNs=791231114368..791946521190)> but was:<null>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at kotlin.test.junit.JUnitAsserter.assertEquals(JUnitSupport.kt:32)
at kotlin.test.AssertionsKt__AssertionsKt.assertEquals(Assertions.kt:63)
at kotlin.test.AssertionsKt.assertEquals(Unknown Source)
...


# numbers don't match (note timeline range is very different, maybe clock conversion issue)
java.lang.AssertionError: expected:<SubMetrics(timeToInitialDisplayNs=35039927, timeToFullDisplayNs=537343160, timelineRangeNs=780778904571..781316247731)> but was:<SubMetrics(timeToInitialDisplayNs=35038802, timeToFullDisplayNs=537340158, timelineRangeNs=780823199413..781360539571)>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
...


java.lang.AssertionError: expected:<SubMetrics(timeToInitialDisplayNs=108563770, timeToFullDisplayNs=581026583, timelineRangeNs=800868511677..801449538260)> but was:<SubMetrics(timeToInitialDisplayNs=108562448, timeToFullDisplayNs=581041616, timelineRangeNs=800912796924..801493838540)>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
...