commit d0d0afc5ac6ccdd1d0d720ba492b70e209cf91fb
author Pablo Gamito <pablogamito@google.com> Tue Jul 25 15:50:16 2023 +0000
committer Pablo Gamito <pablogamito@google.com> Tue Jul 25 15:50:16 2023 +0000
tree 21c585d3c221faca3cad2e9c001098926133f12d
parent a737b7419191635c5e22a73836ab9822615ee481

Use correct timestamp for RegionSubject

Test: N/A

Bug: 293096776
Change-Id: Id37b4be4eb012ab4369d973008dc237620a4cd35

tests/FlickerTests/src/com/android/server/wm/flicker/CommonAssertions.kt

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 4d36111..abd8758 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 @@
                 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)