Remove fps checks from DecoderTest#testVrHighPerformance tests.
They're flaky and better suited as a dedicated VR benchmarking test
instead of a CTS test. Instead, simply verify the reported capabilities.
(originally contributed by scherkus@google.com)
Change-Id: Ic5d2a8b985053fba0f84566c93cf92ad8554e219
diff --git a/tests/tests/media/src/android/media/cts/DecoderTest.java b/tests/tests/media/src/android/media/cts/DecoderTest.java
index f695c692..686f5ed 100755
--- a/tests/tests/media/src/android/media/cts/DecoderTest.java
+++ b/tests/tests/media/src/android/media/cts/DecoderTest.java
@@ -2889,10 +2889,6 @@
// Test minimum mandatory requirements.
assertTrue(doesMimeTypeHaveMinimumSpecVrReadyCodec(MediaFormat.MIMETYPE_VIDEO_HEVC));
- decodeInParallel(
- // using the 60fps sample to save on apk size, but decoding only at 30fps @ 5Mbps
- R.raw.bbb_s2_1920x1080_mp4_hevc_mp41_10mbps_60fps_aac_lc_6ch_384kbps_22050hz,
- 300, 30 /* fps */, 1);
boolean hevcIsReady = doesMimeTypeHaveVrReadyCodec(MediaFormat.MIMETYPE_VIDEO_HEVC);
if (!hevcIsReady) {
@@ -2915,10 +2911,6 @@
// Test minimum mandatory requirements.
assertTrue(doesMimeTypeHaveMinimumSpecVrReadyCodec(MediaFormat.MIMETYPE_VIDEO_VP9));
- decodeInParallel(
- // using the 60fps sample to save on apk size, but decoding only at 30fps @ 5Mbps
- R.raw.bbb_s2_1920x1080_webm_vp9_0p41_10mbps_60fps_vorbis_6ch_384kbps_22050hz,
- 300, 30 /* fps */, 1);
boolean vp9IsReady = doesMimeTypeHaveVrReadyCodec(MediaFormat.MIMETYPE_VIDEO_VP9);
if (!vp9IsReady) {
