FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

CTS Failed on IMX6 DL _testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CTS Failed on IMX6 DL _testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported

‎04-22-2016 12:51 AM
1,330 Views
shuyuchou
Contributor I

Hi ,

We have a CTS Test failed (android.keystore.cts.KeyChainTest - testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported )  on our  custom project .

We verify the same CTS  Test on  EV board  - " IMX6 Series SABRE for Smart Devices" and get the same problems!

Is the CTS failed Known issues  ?

Can anyone Know how to solve this problems or any suggestion?

Test Enviroment :

CTS 5.1_r5

Freescale :

Image: Android 5.1.1 . I.MX6 DualLite (download from NXP i.MX 6 Series Software and Development Tool Resource)

CPU : iMX6DL

EVB version : IMX6 Series SABRE for Smart Devices (detail info)

MFG too: L5.1.1

The following are failed log on IMX6 Series SABRE for Smart Devices:

Compatibility Test Package: android.keystore ABI: armeabi-v7a

Test

Result

Details

  1. android.keystore.cts.KeyChainTest

-- testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported

fail

  1. junit.framework.AssertionFailedError: RSA must be hardware-backed by a hardware-specific Keymaster HAL

Detaild Log :

01-01 00:05:08.395  1970  1986 I TestRunner: started: testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported(android.keystore.cts.KeyChainTest)

01-01 00:05:08.400  1970  1986 D CtsTestRunListener: Total memory  : 1144080

01-01 00:05:08.400  1970  1986 D CtsTestRunListener: Used memory   : 719732

01-01 00:05:08.400  1970  1986 D CtsTestRunListener: Free memory   : 424348

01-01 00:05:08.400  1970  1986 D CtsTestRunListener: Now executing : android.keystore.cts.KeyChainTest

01-01 00:05:08.407  1970  1986 I TestRunner: failed: testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported(android.keystore.cts.KeyChainTest)

01-01 00:05:08.407  1970  1986 I TestRunner: ----- begin exception -----

01-01 00:05:08.409  1970  1986 I TestRunner: junit.framework.AssertionFailedError: RSA must be hardware-backed by a hardware-specific Keymaster HAL

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.Assert.fail(Assert.java:50)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.Assert.assertTrue(Assert.java:20)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.keystore.cts.KeyChainTest.testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported(KeyChainTest.java:42)

01-01 00:05:08.409  1970  1986 I TestRunner:      at java.lang.reflect.Method.invoke(Native Method)

01-01 00:05:08.409  1970  1986 I TestRunner:      at java.lang.reflect.Method.invoke(Method.java:372)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestCase.runTest(TestCase.java:168)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestCase.runBare(TestCase.java:134)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestResult$1.protect(TestResult.java:115)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestResult.runProtected(TestResult.java:133)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.DelegatingTestResult.runProtected(DelegatingTestResult.java:90)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestResult.run(TestResult.java:118)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:52)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestCase.run(TestCase.java:124)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:63)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestSuite.runTest(TestSuite.java:243)

01-01 00:05:08.409  1970  1986 I TestRunner:      at junit.framework.TestSuite.run(TestSuite.java:238)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.DelegatingTestSuite.run(DelegatingTestSuite.java:103)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.AndroidTestSuite.run(AndroidTestSuite.java:52)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.internal.runner.junit3.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.Suite.runChild(Suite.java:128)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.Suite.runChild(Suite.java:24)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)

01-01 00:05:08.409 1970  1986 I TestRunner:      at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runners.ParentRunner.run(ParentRunner.java:300)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runner.JUnitCore.run(JUnitCore.java:157)

01-01 00:05:08.409  1970  1986 I TestRunner:      at org.junit.runner.JUnitCore.run(JUnitCore.java:136)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:245)

01-01 00:05:08.409  1970  1986 I TestRunner:      at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1853)

01-01 00:05:08.409  1970  1986 I TestRunner: ----- end exception -----

01-01 00:05:08.411  1970  1986 I TestRunner: finished: testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported(android.keystore.cts.KeyChainTest)

01-01 00:05:08.414  1970  1986 I TestRunner: started: testIsKeyAlgorithmSupported_RequiredAlgorithmsSupported(android.keystore.cts.KeyChainTest)

01-01 00:05:08.418  1970  1986 I TestRunner: finished: testIsKeyAlgorithmSupported_RequiredAlgorithmsSupported(android.keystore.cts.KeyChainTest)

01-01 00:05:08.420  1970  1986 I TestRunner: started: testAndroidTestCaseSetupProperly(android.keystore.cts.KeyChainTest)

01-01 00:05:08.423  1970  1986 I TestRunner: finished: testAndroidTestCaseSetupProperly(android.keystore.cts.KeyChainTest)

  1. 01-01 00:05:08.427 1970  1986 I TestRunner: run finished: 3 tests, 1 failed, 0 ignored

Thanks,

shuyu

Labels (2)
Labels
Tags (2)
0 Kudos
Reply
3 Replies

‎04-22-2016 03:39 AM
739 Views
shuyuchou
Contributor I

Dear Artur,

I've  check the Table 5 of the attch doc, the table only show "Some CTS use cases may fail randomly if running the whole CTS suite."

Could you please provide the detail CTS errata list .

Many Thanks,

shuyu

146563_146563.pngpastedImage_1.png

0 Kudos
Reply

‎04-22-2016 03:51 AM
739 Views
art
NXP Employee
NXP Employee

As the Table 5 says, the CTS use cases fail is random. So, there is no definite errata list for this issue.

Best Regards,

Artur

0 Kudos
Reply

‎04-22-2016 03:16 AM
739 Views
art
NXP Employee
NXP Employee

Please refer to the bottom row of the Table 5 in the attached document. It says that this is the known issue, but it was still under investigation at the moment of Lollipop 5.1.1 release. Now it seems to be fixed in the latest Marshmallow 6.0.1 release.


Have a great day,
Artur

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Preview file
260 KB
0 Kudos
Reply