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
diff --git a/test/993-breakpoints-non-debuggable/native_attach_agent.cc b/test/993-breakpoints-non-debuggable/native_attach_agent.cc
index 58a68c8..71d30eb 100644
--- a/test/993-breakpoints-non-debuggable/native_attach_agent.cc
+++ b/test/993-breakpoints-non-debuggable/native_attach_agent.cc
@@ -24,7 +24,6 @@
extern "C" JNIEXPORT void JNICALL Java_art_Test993AttachAgent_setupJvmti(JNIEnv* env, jclass) {
Runtime* runtime = Runtime::Current();
- CHECK(!Runtime::Current()->IsJavaDebuggable());
std::ostringstream oss;
oss << (kIsDebugBuild ? "libtiagentd.so" : "libtiagent.so") << "=993-non-debuggable,art";
LOG(INFO) << "agent " << oss.str();