-
Notifications
You must be signed in to change notification settings - Fork 3k
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
TESTS: update examples.json to enable testing #10625
Conversation
@jamesbeyond, thank you for your changes. |
Any more insight into how this might be used with custom targets? |
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 ok to me from a tools PoV.
@jamesbeyond Can you also add description to docs (we have there CI page) - what we are testing in the examples. This should cover how this is used. We have already something when tools were updated to include this (htrun/greentea or similar) ? @loverdeg-ep What are you after exactly - what we should not miss documenting? This is considered being used in internal CI setup, I would like to understand the use cases you are thinking about. |
We have our own internal CI/test setup based on gitlab and gitlab runners. We like to keep tabs on what the team is doing internally so we can come up beside you. I'm wondering what specifically this enables. |
This is mean for testing mbed-os-examples, and will be required to use with https://github.com/ARMmbed/mbed-os-example-blinky/tree/master/tests |
Sure, @0xc0170 I am adding docs to the CI page and adding them together to the CI tasks |
Please have docs ready this week at least as PR to reference here. I started CI job |
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.
Waiting for documentation reference
Note, 2 days to get in to 5.13 |
@0xc0170 Please don't hold this up over documentation. Creating an issue to capture that this will need documentation is fine with me. |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Talking offline to address documentation update |
Description
Update examples.json with
log compare
option to enable example tests.The built test_spce.json should be upload to S3.
This is targeted at mbed 5.13
Pull request type
Reviewers
@OPpuolitaival