-
Notifications
You must be signed in to change notification settings - Fork 3k
tools: Add explicit target for NVStore example #6919
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
Conversation
@davidsaada If there are other targets that are explicitly supported, please let us know (similar to this: b61912c). @ARMmbed/mbed-os-maintainers This could also be why export tests have taken a bit longer, since this example is currently being built against all exported targets instead of a subset. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me if David's happy
/morph build |
Build was stuck trying to start on a node that was never brought online... |
/morph build |
Build : SUCCESSBuild number : 2041 Triggering tests/morph test |
Test : SUCCESSBuild number : 1857 |
Exporter Build : FAILUREBuild number : 1690 |
/morph export-build |
Exporter Build : SUCCESSBuild number : 1693 |
Description
Realized with this PR (#6879) that nvstore was being compiled and tested against all targets. Limited example building for K64F, since example only calls out K64F.
Pull request type