CYESKIT_064B0S2_4343W UnicodeEncodeError: 'charmap' codec can't encode characters

[maclobdell]

Description of defect

After applying work-arounds for #13058 and #13027, I ran mbed os tests.

Several tests result in an UnicodeEncodeError and the results are not conclusive. In the test summary they show as SKIPPED.

See full test summary:
CYESKIT_064B0S2_4343W_GCC_ARM_test_results.txt

When I run a single test with verbose output, I can see the UnicodeEncodeError: 'charmap' codec can't encode characters in the output. Such as in this log:
cyeskit-test-events-queue.txt

Could this be caused by a clocking issue - causing corrupt serial characters during some tests?

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) ?

mbed-os-6.0.0-rc1

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 a single test suite
mbed test -m CYESKIT_064B0S2_4343W -t GCC_ARM -n tests-events-queue -v
-view the terminal output

[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

[ciarmcom]

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

[adbridge]

@maclobdell I've corrected 'mbed-os-6.0.0-rc-1' to 'mbed-os-6.0.0-rc1' to get the right tag!

[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?

[maclobdell]

tested production kit. I don't see this issue any longer. suspect there was a mis-configuration in the clock for the engineering sample kit, but it is resolved now on the production kit that superseded it.