小编Roc*_*bal的帖子

我在 android 应用程序 jdk.internal.misc.Unsafe.park （本机方法）中面临这个问题

stackoverflow 中有几个答案，但我需要以 android 特定的方式

main (waiting): tid=1 systid=14525 
   at jdk.internal.misc.Unsafe.park(Native method)
   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:917)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1240)
   at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:267)
   at com.google.android.gms.common.api.internal.zabe.zai(com.google.android.gms:play-services-base@@18.0.1:1)
   at com.google.android.gms.common.api.internal.zabd.zaa(com.google.android.gms:play-services-base@@18.0.1:2)
   at com.google.android.gms.common.api.internal.zabx.onReceive(com.google.android.gms:play-services-base@@18.0.1:4)
   at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$LoadedApk$ReceiverDispatcher$Args(LoadedApk.java:1752)
   at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(unavailable:2)
   at android.os.Handler.handleCallback(Handler.java:938)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loopOnce(Looper.java:233)
   at android.os.Looper.loop(Looper.java:344)
   at android.app.ActivityThread.main(ActivityThread.java:8191)
   at java.lang.reflect.Method.invoke(Native method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1034)

当尝试使用 Circleci 构建 Android 应用程序 Espresso Instrumentation Tests 时Unknown platform error occurred when running the UTP test suite.

任务：app：connectedDebugAndroidTest 失败

测试结果保存为文件：/home/circleci/code/app/build/outputs/androidTest-results/connected/test-result.pb。通过从菜单栏中选择 Run > Import Tests From File 并导入 test-result.pb，在 Android Studio 中检查这些结果。

失败：构建失败并出现异常。

• 出了什么问题：任务“：app：connectedDebugAndroidTest”执行失败。

有测试失败的情况。查看报告：file:///home/circleci/code/app/build/reports/androidTests/connected/index.html

• 尝试：

使用 --stacktrace 选项运行以获取堆栈跟踪。使用 --info 或 --debug 选项运行以获得更多日志输出。使用 --scan 运行以获得完整的见解。

• 在https://help.gradle.org获取更多帮助

12 秒内构建失败 74 个可操作任务：1 个已执行，73 个是最新的

<-------------> 0% WAITING> 已达到 IDLEMax 尝试次数 (2)

退出，代码退出状态 1

我在 UI 测试中尝试使用 MockK 时遇到错误，该错误在 Unittest 案例中完美运行

MockK could not self-attach a jvmti agent to the current VM

完整的错误报告

Caused by: io.mockk.proxy.MockKAgentException: MockK could not self-attach a jvmti agent to the current VM. This feature is required for inline mocking.
This error occured due to an I/O error during the creation of this agent: java.io.IOException: Unable to dlopen libmockkjvmtiagent.so: dlopen failed: library "libmockkjvmtiagent.so" not found

Potentially, the current VM does not support the jvmti API correctly
at io.mockk.proxy.android.AndroidMockKAgentFactory.init(AndroidMockKAgentFactory.kt:67)
at io.mockk.impl.JvmMockKGateway.<init>(JvmMockKGateway.kt:46) …