Fix ExoPlayerTest to use C.TIME_UNSET instead of C.POSITION_UNSET

This inconsistency was exposed by an upcoming change to deprecate
`POSITION_UNSET` in favour of `INDEX_UNSET` because position is an
ambiguous term between 'byte offset' and 'media position', as shown
here.

PiperOrigin-RevId: 492470241
(cherry picked from commit 2650654dd0d0654fc4cca67b0d3347d88431fa4e)
This commit is contained in:
ibaker 2022-12-02 16:05:02 +00:00 committed by christosts
parent 5612f6924a
commit f43cc38ce1

View File

@ -2524,7 +2524,7 @@ public final class ExoPlayerTest {
.build()
.start()
.blockUntilEnded(TIMEOUT_MS);
assertThat(target.positionMs).isEqualTo(C.POSITION_UNSET);
assertThat(target.positionMs).isEqualTo(C.TIME_UNSET);
}
@Test
@ -2546,7 +2546,7 @@ public final class ExoPlayerTest {
.build()
.start()
.blockUntilEnded(TIMEOUT_MS);
assertThat(target.positionMs).isEqualTo(C.POSITION_UNSET);
assertThat(target.positionMs).isEqualTo(C.TIME_UNSET);
}
@Test
@ -12292,7 +12292,7 @@ public final class ExoPlayerTest {
public PositionGrabbingMessageTarget() {
mediaItemIndex = C.INDEX_UNSET;
positionMs = C.POSITION_UNSET;
positionMs = C.TIME_UNSET;
}
@Override