- 
                Notifications
    You must be signed in to change notification settings 
- Fork 3k
add mbed-os-example-aws to the example list #13070
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
add mbed-os-example-aws to the example list #13070
Conversation
| @ithinuel, thank you for your changes. | 
        
          
                tools/test/examples/examples.json
              
                Outdated
          
        
      | "compile" : true, | ||
| "export": true, | ||
| "test" : false, | ||
| "baud_rate": 9600, | 
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.
It should be 115200 bauds
See https://github.com/ARMmbed/mbed-os-example-aws/blob/master/mbed_app.json#L25
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.
Good catch!
| Blocked by ARMmbed/mbed-os-example-for-aws#3 | 
| 
 To verify, I'll trigger now CI , should fail | 
| Test run: FAILEDSummary: 2 of 3 test jobs failed Failed test jobs: 
 | 
| CI confirmed, blocked by ARMmbed/mbed-os-example-for-aws#3 | 
| 
 Fixed now, this PR should work. Could you trigger the CI again? @0xc0170 | 
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.
LGTM
| Looks like GCC ARM already failed, please review (logs will be published once arm also completes) | 
| Test run: FAILEDSummary: 2 of 3 test jobs failed Failed test jobs: 
 | 
| @0xc0170 Looks like we have duplicated copies of the  During the Greentea stage, the CI script added that library into the  But it doesn't seem to clean it up afterwards. When it came to testing our AWS example, the example fetched  | 
| In fact, mbed-os-example-wifi relies on the  If we add a step to clean it up, I suppose the AWS example will work but the WiFi example will not compile in CI anymore... We need to align them I guess. | 
| @LDong-Arm please talk to @jamesbeyond how to address this wifi copy/clean up issue | 
| "sub-repo-example": false, | ||
| "subs": [], | ||
| "features" : [], | ||
| "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.
Should we limit the targets? For example, the previous CI run also tried to build for NUCLEO_F411RE and failed, and I don't think it's a WiFi or Ethernet target.
It's due to the lack of TRNG on this target, see ARMmbed/mbed-os-example-tls-socket#34
For the WiFi example (line 120) we only build it for one target.
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.
Maybe K64F (Ethernet), and one WiFi target TBC
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.
We should limit to a few targets with supported HW. @jamesbeyond
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.
Do we have a blocker created for this ? To my understanding this should be in 6.1 correct?
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.
This needs to go in 6.1.
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.
Okay if we set targets in the future, since the example is disabled for now...
| 
 @LDong-Arm Please let us know how to proceed here. I've reviewed the dependencies and it's not clear to me (providing the status here would help). If we can resolve this by end of today it would be great. | 
| 
 We agreed to set "targets" to DISCO_L475VG_IOT01A and K64F and "compile" to false pending updates to CI that will be done post 6.1. | 
| CI started | 
| "sub-repo-example": false, | ||
| "subs": [], | ||
| "features" : [], | ||
| "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.
Okay if we set targets in the future, since the example is disabled for now...
| Test run: SUCCESSSummary: 6 of 6 test jobs passed | 
Summary of changes
This PR adds armmbed/mbed-os-example-aws to the CI build test list.
Impact of changes
None
Migration actions required
None
Documentation
None
Pull request type
Test results
Reviewers