Mbed-os: Add CI for CY8CKIT_062_WIFI_BT - FPGA_CI

[yarbcy]

Description of defect

Add Continious integration test for CY8CKIT_062_WIFI_BT - FPGA_CI (Test Shield).
Test regresion was detected by https://github.com/ARMmbed/mbed-os/issues/12687
SPI test cases changed from PASS state to FAIL. Ii is because of new code change to file: "mbed-os\TESTS\mbed_hal_fpga_ci_test_shield\spi\main.cpp"

Target(s) affected by this defect ?

CY8CKIT_062_WIFI_BT

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

GCC_ARM

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

ecf4008

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

N/A

How is this defect reproduced ?

1. Run FPGA CI Automated tests.
2. Connect FPGA CI board
3. mbed test -m CY8CKIT_062_WIFI_BT -t GCC_ARM -n tests-mbed_hal_fpga_ci_test_shield-spi

[yarbcy]

@adbridge Please review.

[adbridge]

@yarbcy
'How is this defect reproduced ?'
This should be a list of steps run to reproduce the failure

[yarbcy]

@yarbcy
'How is this defect reproduced ?'
This should be a list of steps run to reproduce the failure

Done.

[0xc0170]

@yarbcy This is the request to add a new target to CI nightly? That is how I understand the initial report.

[ciarmcom]

@yarbcy thank you for the update.It appears however that there is still some missing information:

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 .
E.g. 'https://github.com/ARMmbed/mbed-os/commit/5d64e558801940b3be547c3d059f28eaabc23f95' is not a unique single snapshot.
Please update the issue header with the missing information.
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.

[yarbcy]

@yarbcy This is the request to add a new target to CI nightly? That is how I understand the initial report.

Yes it is.

[ciarmcom]

@yarbcy thank you for the update.It appears however that there is still some missing information:

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 .
E.g. 'https://github.com/ARMmbed/mbed-os/commit/5d64e558801940b3be547c3d059f28eaabc23f95' is not a unique single snapshot.
Please update the issue header with the missing information.
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.

[ciarmcom]

@yarbcy 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 .
E.g. 'https://github.com/ARMmbed/mbed-os/commit/5d64e558801940b3be547c3d059f28eaabc23f95' has not been matched as a valid tag or sha.
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.

[adbridge]

@yarbcy where does your commit hash come from? The script looks for a PR that has been merged to master that contains that hash. If it cannot find one then it raised the above comment...

[ciarmcom]

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

[ciarmcom]

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

[ciarmcom]

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

[yarbcy]

Fixed.

[0xc0170]

@ARMmbed/mbed-os-test Please review

[jamesbeyond]

We are waiting for the new order of FPGA shileds

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2437