-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CYESKIT_064B0S2_4343W Mbed OS 6 Test fails #13075
Comments
@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. 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. |
cc @ARMmbed/team-cypress |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
I updated the description with the commit hash instead of the tag name. |
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. |
Tested production kit. everything but the cordio test passes now. that is covered by #13295. closing this one. |
Description of defect
After applying work-arounds for #13058 and #13027, I ran mbed os tests.
The following test result in FAIL or TIMEOUT:
features-feature_ble-targets-target_cordio-tests-cordio_hci-driver | FAIL | 57.14
tests-mbed_drivers-reset_reason | TIMEOUT | 130.08
tests-mbed_drivers-timeout | FAIL | 41.08
tests-mbed_hal-reset_reason | TIMEOUT | 130.03
tests-mbed_hal-rtc_reset | TIMEOUT | 154.11
See full test summary:
CYESKIT_064B0S2_4343W_GCC_ARM_test_results.txt
Target(s) affected by this defect ?
CYESKIT_064B0S2_4343W
Toolchain(s) (name and version) displaying this defect ?
GCC Arm compiler 9
What version of Mbed-os are you using (tag or sha) ?
9a8c9e2
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 ?
-get a board, provision it
-import mbed os
-apply workarounds as noted in above issues
-run tests
mbed test -m CYESKIT_064B0S2_4343W -t GCC_ARM
-view the terminal output
The text was updated successfully, but these errors were encountered: