Skip to content
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

Fix timeout units in events timing test #4314

Merged
merged 1 commit into from
May 15, 2017

Conversation

c1728p9
Copy link
Contributor

@c1728p9 c1728p9 commented May 12, 2017

A units mistake led to passing 20000 seconds instead of 20000 milliseconds to greentea. The would cause the test to spin for 6 hours if it got stuck anywhere.

Taken from commit 8b5dee8 in the CMSIS_5 branch.

A units mistake led to passing 20000 seconds instead of 20000 milliseconds
to greentea. The would cause the test to spin for 6 hours if it got stuck
anywhere.
@c1728p9 c1728p9 requested a review from geky May 12, 2017 20:08
@c1728p9
Copy link
Contributor Author

c1728p9 commented May 12, 2017

/morph test

@theotherjimmy
Copy link
Contributor

spin for 6 hours if it got stuck anywhere.

Ouch

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 205

All builds and test passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants