Restrict 175-alloc-big-bignums to compiled builds
175-alloc-big-bignums copies a lot of huge BigIntegers. Running
this in interpreted mode relies on the fact that the copying is
done in native code. With the RI implementation
it won't be. Disable those tests to avoid timeouts. Running this
interpreted was never very useful. The test as a whole will be
less useful with the RI implementation, since we'll no longer
rely on reference processing to clean up native BigInteger
memory.
Bug: 136887041
Test: Only disabling test
Change-Id: Ia5af281b98758bf5ad8465a8f07614594c4ac31d
diff --git a/test/knownfailures.json b/test/knownfailures.json
index 6ddb91d..bd085f9 100644
--- a/test/knownfailures.json
+++ b/test/knownfailures.json
@@ -1320,6 +1320,11 @@
"zipapex runner."]
},
{
+ "tests": ["175-alloc-big-bignums"],
+ "variant": "interpreter | interp-ac",
+ "description": "Interpreting BigInteger.add() is too slow (timeouts)"
+ },
+ {
"tests": ["2029-contended-monitors"],
"variant": "interpreter | interp-ac | gcstress | trace",
"description": ["Slow test. Prone to timeouts."]