【问题标题】:Appcenter test fail: There was an error in the forked processAppcenter 测试失败:分叉进程中出现错误
【发布时间】:2019-01-17 02:10:30
【问题描述】:

使用 Maven 和 junit 构建测试套件,在将测试上传到 App center 进行测试时,出现“fork process 中出现错误”的错误。这是来自应用中心的消息
Please refer to target/surefire-reports for the individual test results. Please refer to dump files (if any exist) [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream. There was an error in the forked process sun.reflect.annotation.TypeNotPresentExceptionProxy org.apache.maven.surefire.booter.SurefireBooterForkException: There was an error in the forked process sun.reflect.annotation.TypeNotPresentExceptionProxy at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:665) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:279) at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:243) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1077) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:907) at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:785) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
如果需要更多信息,请告诉我。谢谢

【问题讨论】:

    标签: java appium qa maven-surefire-plugin visual-studio-app-center


    【解决方案1】:

    您获得的堆栈跟踪涵盖了真正的堆栈跟踪 - 输出显示 real 堆栈跟踪已写入转储文件。无论如何,这对你没有多大帮助..

    请参考转储文件(如果有的话)[date]-jvmRun[N].dump、[date].dumpstream和[date]-jvmRun[N].dumpstream。

    我认为这是 this question 的副本——至少听起来是这样的。

    在这种情况下,您的代码使用了在测试执行时不可用的注释。我对PowerMock 注释和jcip-annotations 也有同样的错误。

    无论如何,由于这个问题很老,你可能已经自己解决了它或解决了它 - 如果没有,如果你的代码库太大,请尝试禁用测试,如二进制搜索。

    错误(在我的情况下)仅在我使用 dependenciesToScan 运行 maven-surefire-plugin 时发生(执行已经存在的测试工件的测试)。此配置需要显式列出要运行测试的依赖项 - 这对于二进制搜索更好,因为您可以逐个注释掉依赖项,这在正常的测试运行中是不容易做到的。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2019-10-08
      • 1970-01-01
      • 1970-01-01
      • 2020-01-02
      • 2014-07-02
      • 1970-01-01
      • 2015-09-19
      • 1970-01-01
      相关资源
      最近更新 更多