Jit-zygote compiled code isn't debuggable
We check the debuggablity of compiled code by checking to see if it
was compiled by the JIT. This works since we throw all precompiled
code out when transitioning to debuggable. Unfortunately with
jit-zygote the non-debuggable zygote methods can be incorrectly seen
as debuggable when encountered on the stack. This can lead to
incorrect deoptimization and other issues. To fix this we explicitly
exclude jit-zygote code from the check.
Bug: 144947842
Test: ./test.py --host
Change-Id: I4e953f64f8261b7a16d7c3199cec89998af0c1cf
diff --git a/test/knownfailures.json b/test/knownfailures.json
index 5e57be5..9dc5f26 100644
--- a/test/knownfailures.json
+++ b/test/knownfailures.json
@@ -1333,6 +1333,13 @@
"description": ["Occasional timeouts."]
},
{
+ "tests": ["2031-zygote-compiled-frame-deopt"],
+ "zipapex": true,
+ "bug": "b/144947842",
+ "description": ["This test requires strong knowledge about where the libdir is",
+ "which the zipapex runner breaks."]
+ },
+ {
"tests": ["909-attach-agent", "126-miranda-multidex"],
"zipapex": true,
"bug": "b/135507613",