android cts执行在中途异常停止 [英] android cts execution stopped abnormally on half-way

问题描述

Android CTS执行异常中途停止。有谁知道如何修复它？

Android CTS execution stopped abnormally half-way. Does anyone know how to fix it?

版本：
Android OS 6.0.1（64位）+ Android CTS 6.0_r6

Version: Android OS 6.0.1(64 bits) + Android CTS 6.0_r6

命令：

run cts --plan CTS --shards 3 --skip-preconditions

错误日志：

06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba5551_depth_stencil_render PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_no_depth_no_stencil_clear PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_no_depth_no_stencil_render PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_no_depth_stencil_clear PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_no_depth_stencil_render PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_depth_no_stencil_clear PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_depth_no_stencil_render PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_depth_stencil_clear PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#rgba8888_depth_stencil_render PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#other_clear PASS 
06-16 03:05:20 I/82abb56f: dEQP-EGL.functional.native_coord_mapping.native_pixmap#other_render PASS 
06-16 03:05:21 E/CtsTest: search postcondition failed
java.lang.AssertionError: search postcondition failed
    at com.android.cts.tradefed.testtype.DeqpTestRunner.selectRunBatch(DeqpTestRunner.java:1247)
    at com.android.cts.tradefed.testtype.DeqpTestRunner.selectRunBatch(DeqpTestRunner.java:1200)
    at com.android.cts.tradefed.testtype.DeqpTestRunner.runTests(DeqpTestRunner.java:1318)
    at com.android.cts.tradefed.testtype.DeqpTestRunner.run(DeqpTestRunner.java:1893)
    at com.android.cts.tradefed.testtype.CtsTest.run(CtsTest.java:581)
    at com.android.tradefed.invoker.TestInvocation.runTests(TestInvocation.java:734)
    at com.android.tradefed.invoker.TestInvocation.prepareAndRun(TestInvocation.java:549)
    at com.android.tradefed.invoker.TestInvocation.performInvocation(TestInvocation.java:452)
    at com.android.tradefed.invoker.TestInvocation.invoke(TestInvocation.java:232)
    at com.android.tradefed.command.CommandScheduler$InvocationThread.run(CommandScheduler.java:449)
06-16 03:05:21 I/82abb56f: arm64-v8a com.drawelements.deqp.egl package complete: Passed 999, Failed 0, Not Executed 0

推荐答案

我用最新的内核看到了这个问题，Google已经确定了这个问题ver，google bug（b / 28979140）。基本上deqp测试在这里随机停止，因为解析了.qpa结果的问题，基于cts-tradefed决定删除已经运行的配置，这些配对错误只是搞乱了cts-tradefed的deqp测试状态并导致崩溃。
来自Google的修复是在修复解析错误的tty驱动程序。

I have seen this with latest kernels, the problem has been identified by Google in tty driver, google bug (b/28979140). Basically the deqp test stops randomly here because of parsing issues of .qpa results based on which cts-tradefed decides to delete the configs that have already been run, these paring errors just mess up the cts-tradefed's deqp test state and cause this crash. Fix from Google is in tty driver that fixes the parsing errors.

这篇关于android cts执行在中途异常停止的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！