aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJerome Jiang <jianj@google.com>2023-10-19 10:06:50 -0400
committerJerome Jiang <jianj@google.com>2023-10-19 11:36:47 -0400
commit424723dc025ce451dab9568239a46b18d0919b4d (patch)
treed8ad03533e29e8071092497db7c76d0ed92d61fe
parente4db6c3aacb3fbcbb939f132915234988f8617c1 (diff)
downloadlibvpx-424723dc025ce451dab9568239a46b18d0919b4d.tar.gz
Run bitrate overflow test only on 64bit systems
Frame size caps the target bitrate internally, so the frame size needs to be large enough to reproduce the target bitrate overflow in the fuzzing test. However the frame size needed exceeds the max buffer allowed on 32bit system defined by VPX_MAX_ALLOCABLE_MEMORY Bug: chromium:1492864 Change-Id: Ia3a9a78cd35516373897039a7769b492e29e8450
-rw-r--r--test/encode_api_test.cc2
1 files changed, 2 insertions, 0 deletions
diff --git a/test/encode_api_test.cc b/test/encode_api_test.cc
index 8e90af911..cf89fd1f2 100644
--- a/test/encode_api_test.cc
+++ b/test/encode_api_test.cc
@@ -409,6 +409,7 @@ TEST(EncodeAPI, ConfigResizeChangeThreadCount) {
}
#if CONFIG_VP9_ENCODER
+#if VPX_ARCH_X86_64 || VPX_ARCH_AARCH64
TEST(EncodeAPI, ConfigLargeTargetBitrateVp9) {
constexpr int kWidth = 16383;
constexpr int kHeight = 16383;
@@ -431,6 +432,7 @@ TEST(EncodeAPI, ConfigLargeTargetBitrateVp9) {
<< "target bitrate: " << cfg.rc_target_bitrate << " framerate: "
<< static_cast<double>(cfg.g_timebase.den) / cfg.g_timebase.num;
}
+#endif // VPX_ARCH_X86_64 || VPX_ARCH_AARCH64
class EncodeApiGetTplStatsTest
: public ::libvpx_test::EncoderTest,