CY8CKIT_062S2_43012 Test Fails

[maclobdell]

Description of defect

The following test result in FAIL with CY8CKIT_062S2_43012 and Mbed OS 6.0.

| CY8CKIT_062S2_43012-ARMC6   | tests-mbed_hal-sleep                                                         | FAIL   |  16.98 |
| CY8CKIT_062S2_43012-ARMC6   | tests-mbed_hal-sleep_manager                                                 | FAIL   |  15.33 |
| CY8CKIT_062S2_43012-ARMC6   | features-feature_ble-targets-target_cordio-tests-cordio_hci-driver           | FAIL   |  34.17 |
| CY8CKIT_062S2_43012-GCC_ARM | tests-mbed_hal-sleep_manager                                                 | FAIL   |  15.46 |
| CY8CKIT_062S2_43012-GCC_ARM | tests-mbed_hal-sleep                                                         | FAIL   |  16.99 |
| CY8CKIT_062S2_43012-GCC_ARM | features-feature_ble-targets-target_cordio-tests-cordio_hci-driver           | FAIL   |  34.16 |

See full test summaries:
CY8CKIT_062S2_43012_GCC_ARM_results.txt
CY8CKIT_062S2_43012_ARM_results.txt

Target(s) affected by this defect ?

CY8CKIT_062S2_43012

Toolchain(s) (name and version) displaying this defect ?

GCC Arm compiler 9
Arm compiler 6

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.0.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed-cli 1.10.1
mbed-cloud-sdk 2.0.8
mbed-flasher 0.10.1
mbed-greentea 1.7.4
mbed-host-tests 1.5.10
mbed-ls 1.7.10
mbed-os-tools 0.0.12
full list of python packages

How is this defect reproduced ?

mbed import https://github.com/armmbed/mbed-os
mbed test -m CY8CKIT_062S2_43012 -t GCC_ARM
mbed test -m CY8CKIT_062S2_43012 -t ARM

[ciarmcom]

@maclobdell thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[0xc0170]

cc @ARMmbed/team-cypress

[kyle-cypress]

Not sure about the cordio failures yet, but the sleep failures are probably the same as #12434 (known issue, fix in progress).

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested?