Corrected the targets value in json file as CI uses real board names

[deepikabhavnani]

Description

Sockets examples were not tested in CI, as CI uses real board names and not macros.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@OPpuolitaival

[ciarmcom]

@deepikabhavnani, thank you for your changes.
@OPpuolitaival @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

[bridadan]

This is more of maintainer's file than a tools file, but looks ok. It does looks like sometimes a K64F was chosen instead of a K66F, any reason for that? Or more general, how come certain targets are included for certain examples and not for others?

[deepikabhavnani]

It does looks like sometimes a K64F was chosen instead of a K66F, any reason for that? Or more general, how come certain targets are included for certain examples and not for others?

All of the test are socket related, so instead of performing test on single target selected different ones for each test.

[cmonr]

CI started

[mbed-ci]

Test run: FAILED

Summary: 1 of 8 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_build-ARMC6

[alekla01]

Restarted CI

[0xc0170]

The previous values were not valid, and only these updated targets were selected anyway

[OPpuolitaival]

Looks very good!

[mbed-ci]

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test

[0xc0170]

CI restarted, it timeouted

[cmonr]

CI job restarted: jenkins-ci/greentea-test

It appears to have timed out, but not sure 100%...