Fix lots of Greentea test warnings #365
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
Ever since I've started on Mbed CE, there have been ludicrous amounts of warnings every time the greentea tests are compiled. The vast majority of these are due to tests using deprecated API, especially legacy RTOS functions that don't use chrono types. This PR fixes at least 90% of these warnings, so the greentea build is now a much more warning-free experience. There are still a few here and there but it's a lot better now at least.
Someday I want to fix all of the warnings and then make the CI builds use -Werror but... not today.
Impact of changes
Way less warnings in Greentea test builds
Migration actions required
Documentation
None
Pull request type
Test results