Temporarily disable tests 914, 915, 917, & 918 on JIT.
Since these tests are very sensitive to the positioning of
runtime methods due to bugs we will temporarily disable them.
Bug: 33630159
Bug: 33616143
Test: ART_TEST_JIT=true mma -j40 test-art-host
Change-Id: I38795029eed2ea8416d24a259f3a7925d95684c6
diff --git a/test/Android.run-test.mk b/test/Android.run-test.mk
index 474e95d..f4cf66c 100644
--- a/test/Android.run-test.mk
+++ b/test/Android.run-test.mk
@@ -543,6 +543,11 @@
# Test 902 hits races with the JIT compiler. b/32821077
# Test 626-const-class-linking can deadlock with JIT. b/33567581
# Test 629 requires compilation.
+# Test 914, 915, 917, & 918 are very sensitive to the exact state of the stack,
+# including the jit-inserted runtime frames. This causes them to be somewhat
+# flaky as JIT tests. This should be fixed once b/33630159 or b/33616143 are
+# resolved but until then just disable them. Test 916 already checks this
+# feature for JIT use cases in a way that is resilient to the jit frames.
TEST_ART_BROKEN_JIT_RUN_TESTS := \
137-cfi \
626-const-class-linking \
@@ -550,6 +555,10 @@
902-hello-transformation \
904-object-allocation \
906-iterate-heap \
+ 914-hello-obsolescence \
+ 915-obsolete-2 \
+ 917-fields-transformation \
+ 918-obsolete-fields \
ifneq (,$(filter jit,$(COMPILER_TYPES)))
ART_TEST_KNOWN_BROKEN += $(call all-run-test-names,$(TARGET_TYPES),$(RUN_TYPES),$(PREBUILD_TYPES), \