From d0d0afc5ac6ccdd1d0d720ba492b70e209cf91fb Mon Sep 17 00:00:00 2001 From: Pablo Gamito Date: Tue, 25 Jul 2023 15:50:16 +0000 Subject: [PATCH] Use correct timestamp for RegionSubject Test: N/A Bug: 293096776 Change-Id: Id37b4be4eb012ab4369d973008dc237620a4cd35 --- .../src/com/android/server/wm/flicker/CommonAssertions.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/FlickerTests/src/com/android/server/wm/flicker/CommonAssertions.kt b/tests/FlickerTests/src/com/android/server/wm/flicker/CommonAssertions.kt index 4d36111cb1243..abd8758383fa5 100644 --- a/tests/FlickerTests/src/com/android/server/wm/flicker/CommonAssertions.kt +++ b/tests/FlickerTests/src/com/android/server/wm/flicker/CommonAssertions.kt @@ -282,7 +282,7 @@ fun LegacyFlickerTest.snapshotStartingWindowLayerCoversExactlyOnApp( snapshotLayers .mapNotNull { snapshotLayer -> snapshotLayer.layer.visibleRegion } .toTypedArray() - val snapshotRegion = RegionSubject(visibleAreas, timestamp) + val snapshotRegion = RegionSubject(visibleAreas, it.timestamp) // Verify the size of snapshotRegion covers appVisibleRegion exactly in animation. if (snapshotRegion.region.isNotEmpty) { val appVisibleRegion = it.visibleRegion(component)