diff options
| author | 2022-08-10 09:11:05 +0000 | |
|---|---|---|
| committer | 2022-08-10 10:49:50 +0000 | |
| commit | cb6117d2d6bc7be46f103af6919fc8ee5b4afdeb (patch) | |
| tree | b59198440244c730e55cd8d837768e756ffe3bc8 /runtime/gc/heap_verification_test.cc | |
| parent | ef4b8a5246278c51a74a312586a4fd3b8c0a4b10 (diff) | |
Remove an incorrect CHECK in 993-breakpoints-non-debuggable test
993-breakpoints-non-debuggable tests breakpoints in non-debuggable runtimes. All the tests that test jvmti functionality start runtime with --jvmti which starts runtime as debuggable. This test adds an agent after runtime has started which switches the runtime mode from non-debuggable to debuggable. This check was added to make sure that we are non-debuggable but missed the fact that we have a config where we start as debuggable even without any jvmti related flags. So this check would fail in certain configs. Remove the incorrect check
Test: art/test.py -t 993-breakpoints-non-debuggable
Bug: 206029744
Change-Id: I5e0d35abd266920237345f63bc4cd7c9f37a1170
Diffstat (limited to 'runtime/gc/heap_verification_test.cc')
0 files changed, 0 insertions, 0 deletions