diff options
| author | 2022-07-18 14:03:14 +0000 | |
|---|---|---|
| committer | 2022-07-18 15:49:11 +0000 | |
| commit | fde2bb5e3968105c1fc9bcc8a9a32bc24bcc03a7 (patch) | |
| tree | f8232f52b02323d1c3c8c4b9c7cc7946d692a9a1 | |
| parent | 40fbf87fb87a883bfdb765daf5779d7e557727f6 (diff) | |
Set jitthreshold to 0 with --jvmti
This is a speculative revert of the CL that changed the jitthreshold to
1 to see if this fixes time outs on jvmti related tests on ASAN. The
timeouts started with the CL that changed the threshold and the dump
shows exactly two threads one of which is a jit thread. So this is the
potential culprit.
Bug: 238730394
Test: art/test.py
Change-Id: I31c690cbe963d33d06be06fc19f43f70107bcfa8
| -rwxr-xr-x | test/etc/run-test-jar | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/etc/run-test-jar b/test/etc/run-test-jar index ef168ca871..7f251e5d50 100755 --- a/test/etc/run-test-jar +++ b/test/etc/run-test-jar @@ -650,11 +650,11 @@ if [ "$USE_JVMTI" = "y" ]; then # needed anymore since the plugin can do it for us now. FLAGS="${FLAGS} -Xplugin:${plugin}" - # For jvmti tests, set the threshold of compilation to 1, so we jit early to + # For jvmti tests, set the threshold of compilation to 0, so we jit early to # provide better test coverage for jvmti + jit. This means we won't run # the default --jit configuration but it is not too important test scenario for # jvmti tests. This is art specific flag, so don't use it with jvm. - FLAGS="${FLAGS} -Xjitthreshold:1" + FLAGS="${FLAGS} -Xjitthreshold:0" fi fi |