Summary of changes to the Android CTS test fail Item (IV)

The test on the Android5.1

1, android.security.cts.selinuxdomaintest# Testinitdomain fail

The printed log

This is the typical L version of the SELinux Test problem.
Android.security.cts.SELinuxDomainTest has 1 fail,
--Testinitdomain
junit.framework.AssertionFailedError:Expected 1 process in SELinux domain "U:R:INIT:S0" Found "[PID:" 1 "proctitle:"/ini T "label:" U:r:init:s0 "vsize:1327104, pid:" 298 "Proctitle:"/system/bin/immvibed "Label:" U:r:init:s0 "vsize:1765376]" Expected:<1> but was:<2> at Junit.framework.Assert.fail (assert.java:50)

The key reason is that because Google emphasizes that the SELinux Context of the system's critical processes must be unique, system-critical processes include such as Init, Vold, Surfaceflinger, netd, ServiceManager, Drmserver, and so on. Once multiple process is found to use these critical domain at the same time, SELinux Test fail.

This is required. A domain switchover is required for a system-critical process to start a long-executing process. Otherwise, you will not be able to pass Google CTS test.

A typical scenario is to start a service with init without a domain switch to the service. For example, in this problem, suntrold_32 the service did not switch to domain, but failed to test.

Here is a simple demo.
Scenario: Define an init-initiated service, Demo_service, and the corresponding run file is/system/bin/demo.
(1). Create a Demo.te under the/device/mediatke/common/sepolicy folder, and then in/device/mediatke/common/boardconfig.mk board_sepolicy_ New Demo.te in UNION macro
(2). Define the demo type, init start service type conversion, Demo.te
Type demo, domain;
Type demo_exec, Exec_type, File_type;
Init_daemon_domain (Demo)
(3). Binding Run File File_context type
/system/bin/demo U:object_r:demo_exec:s0
(4). Define other permissions in Demo.te according to the files and devices that the demo needs to access.

A typical scenario is to start a service with init without a domain switch to the service. For example, in this problem immvibed the service does not have domain switch, so it can not pass the test. Just follow the demo changes.

2, android.webgl.cts.webgltest#test_conformance_extensions_oes_texture_float_with_canvas_html fail

Remove the webviewgoogle.apk in the GMs to use webview.apk to pass. Assuming the domestic version number must be integrated webviewgoogle.apk only can apply for exemption, can refer to the following link
https://code.google.com/p/chromium/issues/detail?id=482278
Integrated webviewgoogle.apk, because this is Chromium 42 version common problem, cannot change, can take Chromium bug report data with Google discussion, waive this issue

3. COM.ANDROID.CTS.APPSECURITY.APPSECURITYTESTS#2 Item fail

"Step" compatibility Test Package:android.tests.appsecurity ABI
Com.android.cts.appsecurity.AppSecurityTests
--Testexternalstoragenone
--Testexternalstoragewrite
Phenomenon
Com.android.cts.tradefed.testtype.TestTimeoutException at Com.android.cts.tradefed.testtype.JarHostTest.runTest ( jarhosttest.java:223)

Analysis Ideas:

1, first confirm whether there is an SD card inserted in the test, because this test needs to insert the SD card talent through

2. If you insert an SD card or fail.

Please make sure that the support Write permission part of Mtklogger in SDCARD.C (system/core/sdcard/) is added to the result.
Assuming no/frameworks/base/data/etc/platform.xml write_external_storage remove group id= "MEDIA_RW" and then test

3, assume that there is export secondary_storage/storage/sdcard1 init.rc, remove the test

4, the above steps after verification or fail, after the version number control, found that yuloreframework.apk caused. Delete Test Pass

CTS-TF > Run CTS--class com.android.cts.appsecurity.appsecuritytests06-29 10:10:46 i/testinvocation:starting Invocation for ' CTS ' on Build ' 5.1_r1 ' on device ayema6yhkvnjqoiz06-29 10:10:46 i/ayema6yhkvnjqoiz:created result dir 201 5.06.29_10.10.4606-29 10:10:47 i/ctstest:abis: [armeabi-v7a, arm64-v8a]06-29 10:11:01 i/ayema6yhkvnjqoiz:collecting Device info06-29 10:11:03 I/ctstest:start test run of 2 packages, containing of tests06-29 10:11:03 I/ayema6yhkvnjqoiz:- ----------------------------------------06-29 10:11:03 i/ayema6yhkvnjqoiz:test Package arm64-v8a Android.tests.appsecurity started06-29 10:11:03 I/ayema6yhkvnjqoiz:-----------------------------------------06-29 10:11:23 I/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests#testappfailaccessprivatedata PASS 06-29 10:11:32 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests#testappupgradedifferentcerts PASS 06-29 10:11:59 I/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests#testexterNalstoragegifts PASS 06-29 10:12:10 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstoragenone PASS 06-29 10:12:20 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstorageread PASS 06-29 10:12:31 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstoragewrite PASS 06-29 10:12:47 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testinstrumentationdiffcert PASS 06-29 10:12:49 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testmultiuserstorage PASS 06-29 10:14:06 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testpermissiondiffcert PASS 06-29 10:14:17 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testshareduiddifferentcerts PASS 06-29 10:14:34 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testuninstallremovesdata PASS 06-29 10:14:37 i/ayema6yhkvnjqoiz:arm64-v8a android.tests.appsecurity Package Complete: Passed, Failed 0, not Executed 006-29 10:14:37 i/ayema6yhkvnjqoiz:-----------------------------------------06-29 10:14:37 i/ Ayema6yhkvnjqoiz:test Package armeabi-v7a android.tests.appsecurity started06-29 10:14:37 I/ayema6yhkvnjqoiz:------- ----------------------------------06-29 10:14:57 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests #testAppFailAccessPrivateData PASS 06-29 10:15:06 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testappupgradedifferentcerts PASS 06-29 10:15:32 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstoragegifts PASS 06-29 10:15:43 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstoragenone PASS 06-29 10:15:53 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstorageread PASS 06-29 10:16:04 i/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appsecuritytests# Testexternalstoragewrite PASS 06-29 10:16:20 I/ayema6yhkvnjqoiz:com.android.cts.appsecurity.appSecuritytests#testinstrumentationdiffcert PASS 06-29 10:16:22 I/ayema6yhkvnjqoiz: Com.android.cts.appsecurity.appsecuritytests#testmultiuserstorage PASS 06-29 10:17:43 I/AYEMA6YHKVNJQOIZ: Com.android.cts.appsecurity.appsecuritytests#testpermissiondiffcert PASS 06-29 10:17:56 I/AYEMA6YHKVNJQOIZ: Com.android.cts.appsecurity.appsecuritytests#testshareduiddifferentcerts PASS 06-29 10:18:16 I/AYEMA6YHKVNJQOIZ: Com.android.cts.appsecurity.appsecuritytests#testuninstallremovesdata PASS 06-29 10:18:21 i/ayema6yhkvnjqoiz:saved Log device_logcat_892804764496421781.zip06-29 10:18:25 i/ayema6yhkvnjqoiz:saved log host_log_3382781982890595027. zip06-29 10:18:25 i/ayema6yhkvnjqoiz:armeabi-v7a android.tests.appsecurity package complete:passed One, Failed 0, not Exe cuted 006-29 10:18:25 i/ayema6yhkvnjqoiz:xml test result file generated at 2015.06.29_10.10.46. Passed, Failed 0, not Executed 006-29 10:18:25 i/ayema6yhkvnjqoiz:time:7m 38s

4, android.media.cts.decodeeditencodetest#testvideoedit720p fail

"Step" compatibility Test Package:android.media ABI
Android.media.cts.DecodeEditEncodeTest
--testvideoedit720p
Phenomenon
Junit.framework.AssertionFailedError:Found frames at Junit.framework.Assert.fail (assert.java:50)
This problem is caused by the same cause as the android.media.cts.encodedecodetest#2 fail

"Step" compatibility Test Package:android.media ABI
Android.media.cts.EncodeDecodeTest
--testencodedecodevideofromsurfacetosurface720p
--testvp8encodedecodevideofromsurfacetosurface720p
Phenomenon
Junit.framework.AssertionFailedError:Found frames at Junit.framework.Assert.fail (assert.java:50)

Change Scenario:

Root cause:
Pq_adl_index_default is turned on by default. The screen will be processed, resulting in a color dot error.

Solution:
Change Alps/vendor/mediatek/proprietary/platform/mt6795/hardware/pq/cust_color.h This file
Will
#define PQ_ADL_INDEX_DEFAULT "1"
Switch
#define PQ_ADL_INDEX_DEFAULT "0"

5, Com.android.cts.devicepolicy.DeviceOwnerTest Fail

Test part Results

CTS-TF > Run CTS--class com.android.cts.devicepolicy.deviceownertest07-08 11:31:36 i/testinvocation:starting Invocation for ' CTS ' on Build ' 5.1_r1 ' on device 8ef2d4c207-08 11:31:36 i/8ef2d4c2:created result dir 2015.07.08_11.31.36 07-08 11:31:36 i/ctstest:abis: [armeabi-v7a, arm64-v8a]07-08 11:31:48 i/8ef2d4c2:collecting device info07-08 11:31:50 I/ Ctstest:start test run of 2 packages, containing tests07-08 11:31:50 i/8ef2d4c2:------------------------------------- ----07-08 11:31:50 i/8ef2d4c2:test package arm64-v8a android.adminhostside started07-08 11:31:50 I/8ef2d4c2:---------- -------------------------------07-08 11:31:50 i/basedevicepolicytest:installing app ctsdeviceownerapp.apk07-08 11:31:55 i/deviceownertest:output for command DPM Set-device-owner ' com.android.cts.deviceowner/ Com.android.cts.deviceowner.basedeviceownertest$basicadminreceiver ': java.lang.IllegalStateException:Trying to    Set device owner But device is already provisioned. At Android.os.Parcel.reaDexception (parcel.java:1569) at Android.os.Parcel.readException (parcel.java:1509) at Android.app.admin.idevicepolicymanager$stub$proxy.setdeviceowner (idevicepolicymanager.java:3212) at    Com.android.commands.dpm.Dpm.runSetDeviceOwner (dpm.java:114) at Com.android.commands.dpm.Dpm.onRun (dpm.java:82)    At Com.android.internal.os.BaseCommand.run (basecommand.java:47) at Com.android.commands.dpm.Dpm.main (dpm.java:38) At Com.android.internal.os.RuntimeInit.nativeFinishInit (Native Method) at Com.android.internal.os.RuntimeInit.main (runtimeinit.java:249) 07-08 11:31:55 i/8ef2d4c2:com.android.cts.devicepolicy.deviceownertest# Testapplicationrestrictions FAIL junit.framework.AssertionFailedError:java.lang.IllegalStateException:Trying to    Set device owner But device is already provisioned. At Android.os.Parcel.readException (parcel.java:1569) at Android.os.Parcel.readException (parcel.java:1509) at Androi D.app.admin.idevicepolicymanager$stub$proxy.setdeviceowner (IDEVICEPolicymanager.java:3212) at Com.android.commands.dpm.Dpm.runSetDeviceOwner (dpm.java:114) at    Com.android.commands.dpm.Dpm.onRun (dpm.java:82) at Com.android.internal.os.BaseCommand.run (basecommand.java:47) At Com.android.commands.dpm.Dpm.main (dpm.java:38) at Com.android.internal.os.RuntimeInit.nativeFinishInit (Native Method) at Com.android.internal.os.RuntimeInit.main (runtimeinit.java:249) expected-to-start with ' Success: ' at JUnit . Framework. Assert.fail (assert.java:50) at Junit.framework.Assert.assertTrue (ASSERT.JAVA:20) at Com.android.cts.devicepolicy.DeviceOwnerTest.setDeviceOwner (deviceownertest.java:96) at Com.android.cts.devicepolicy.DeviceOwnerTest.setUp (deviceownertest.java:41) at Junit.framework.TestCase.runBare ( testcase.java:132) at Com.android.tradefed.testtype.devicetestresult$1.protect (devicetestresult.java:81) at Com.android.tradefed.testtype.DeviceTestResult.runProtected (devicetestresult.java:56) at Com.android.tradefed.testtype.DeviCetestresult.run (devicetestresult.java:85) at Junit.framework.TestCase.run (testcase.java:124) at Com.android.tradefed.testtype.DeviceTestCase.run (devicetestcase.java:117) at Com.android.cts.tradefed.testtype.jarhosttest$testrunnable.run (jarhosttest.java:248) at Com.android.tradefed.util.runutil$runnablenotifier.run (runutil.java:346)

Tip: java.lang.IllegalStateException:Trying To set device owner, but device is already provisioned. Device owner already exists

Solution Ideas:

Go to Settings-"Advanced Settings-" view in Account

An account already exists and needs to be deleted. Methods such as the following:

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Delete and try again

CTS-TF > Run CTS--class com.android.cts.devicepolicy.deviceownertest07-08 11:38:25 i/testinvocation:starting Invocation for ' CTS ' on Build ' 5.1_r1 ' on device 8ef2d4c207-08 11:38:25 i/8ef2d4c2:created result dir 2015.07.08_11.38.25 07-08 11:38:25 i/ctstest:abis: [armeabi-v7a, arm64-v8a]07-08 11:38:37 i/8ef2d4c2:collecting device info07-08 11:38:39 I/ Ctstest:start test run of 2 packages, containing tests07-08 11:38:39 i/8ef2d4c2:------------------------------------- ----07-08 11:38:39 i/8ef2d4c2:test package arm64-v8a android.adminhostside started07-08 11:38:39 I/8ef2d4c2:---------- -------------------------------07-08 11:38:40 i/basedevicepolicytest:installing app ctsdeviceownerapp.apk07-08 11:38:44 i/deviceownertest:output for command DPM Set-device-owner ' com.android.cts.deviceowner/ Com.android.cts.deviceowner.basedeviceownertest$basicadminreceiver ': Success:device owner set to package Com.android.cts.deviceownerActive Admin set to component {Com.android.cts.deviceowner/com.android.cts.deviceowner.basedeviceownertest$basicadminreceiver}07-08 11:38:46 I/basedevicepolicytest:test com.android.cts.deviceowner.applicationrestrictionstest#testsetapplicationrestrictions:passed07-08 11:38:46 I/ Basedevicepolicytest:test com.android.cts.deviceowner.applicationrestrictionstest# testandroidtestcasesetupproperly:passed07-08 11:38:48 I/basedevicepolicytest:test com.android.cts.deviceowner.cleardeviceownertest#testcleardeviceowner:passed07-08 11:38:48 I/ Basedevicepolicytest:test com.android.cts.deviceowner.cleardeviceownertest#testandroidtestcasesetupproperly:  passed07-08 11:38:49 i/8ef2d4c2:com.android.cts.devicepolicy.deviceownertest#testapplicationrestrictions PASS

This test is also available in GTS: Com.google.android.xts.devicepolicy.DeviceOwnerTest

Suppose there is a report: Java.lang.IllegalStateException:Trying to set device owner but the device is already provisioned should be the same problem, just to delete the account and then test

Summary of changes to the Android CTS test fail Item (IV)