You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for Mbed OS PSA tests to be picked up, the following command line is needed:
mbed test -t <TOOLCHAIN> -m <TARGET> --app-config TESTS/configs/experimental.json
where <TARGET> needs to have PSA enabled (e.g. K64F or K66F). It's because the tests are inside FEATURE_EXPERIMENTAL_API and not visible unless EXPERIMENTAL_API is added to the list of features using experimental.json.
Since non-experimental tests are already covered by regular Greentea testing, we may use a filter -n platform-feature_experimental_api-* to limit the scope.
Target(s) affected by this defect ?
K64F/K66F (one target is probably sufficient)
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM and ARM (use the versions available in CI)
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.10.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.5
How is this defect reproduced ?
There's currently no CI coverage of mbed test with --app-config TESTS/configs/experimental.json.
The text was updated successfully, but these errors were encountered:
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-3980
Description of defect
In order for Mbed OS PSA tests to be picked up, the following command line is needed:
where
<TARGET>
needs to have PSA enabled (e.g. K64F or K66F). It's because the tests are insideFEATURE_EXPERIMENTAL_API
and not visible unlessEXPERIMENTAL_API
is added to the list of features usingexperimental.json
.Since non-experimental tests are already covered by regular Greentea testing, we may use a filter
-n platform-feature_experimental_api-*
to limit the scope.Target(s) affected by this defect ?
K64F/K66F (one target is probably sufficient)
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM and ARM (use the versions available in CI)
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.10.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.5
How is this defect reproduced ?
There's currently no CI coverage of
mbed test
with--app-config TESTS/configs/experimental.json
.The text was updated successfully, but these errors were encountered: