-
Notifications
You must be signed in to change notification settings - Fork 3k
Coding convention changes #3268
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
Coding convention changes #3268
Conversation
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
Signed-off-by: Mahadevan Mahesh <[email protected]>
/morph test-nightly |
We were moving some of the CI machines around and the server cable got bumped, so the nightly job got stopped unfortunately. I will restart it now. /morph test-nightly |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
@bridadan I don't understand the reason for the test failure. |
The test failure seems to be spurious, the event queue took a little longer to service an event than it normally does on one of the boards (NCS36510), though the board shouldn't have been affected by this change set. And I was unable to reproduce the failure locally after performing the same merges that the CI did. So I don't think its necessary to run the nightly again. I'll just run the mbed 2 tests now and then it should be good to come in. |
@mbed-bot: TEST HOST_OSES=ALL |
[Build 1122] |
Can this be merged in please. Thank you. |
Description
Coding convention changes
Status
**READY