-
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
Add CTest support for mbed-drivers-ticker
greentea test
#14892
Conversation
@rwalton-arm, thank you for your changes. |
Ready for review now. |
93e3498
to
e17ead1
Compare
e17ead1
to
792f2e3
Compare
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.
@rwalton-arm Thanks, this looks and works really well! I just added some comments.
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.
I've added a few more comments
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.
Verified on K64F, after rebasing the PR to have the greentea-client I/O fix.
792f2e3
to
442b1bc
Compare
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.
Thanks for the update, I just added one question.
8501ef1
to
9686d1d
Compare
We weren't setting the "supported_application_profiles" correctly for some baremetal supported targets. This didn't cause build failures with mbed-cli 1 as it just seems to ignore this config parameter. In our CMake build system we have added a hard dependency on the supported_application_profiles; we fail the build if the profile we're trying to build isn't in the list.
The github workflow to test building multiple executables was using the soon to be deprecated docker image "mbedos/mbed-os-env:latest". This commit points it at the new docker image on ghcr.io.
14042b2
to
1a7a89a
Compare
CI restarted |
Jenkins CI Test : ❌ FAILEDBuild Number: 4 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Don't panic. This was the aborted run. |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 5 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Following approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest.
Following approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest.
Following approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/equeue requires MBED_EXTENDED_TESTS. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Following the approach defined in ARMmbed#14892 and ARMmbed#14902, events greentea tests are ported to enable running with CTest. events/queue and events/timing both require DEVICE_USTICKER.
Summary of changes
This PR adds CTest support for greentea tests, and enables it for the
mbed-drivers-ticker
test.This PR makes the following changes:
BUILD_GREENTEA_TESTS
option to enable greentea testsmbed-drivers-ticker
test, usingmbedhtrun
to run the testMBED_HTRUN_ARGUMENTS
cache variable which is a list of options to forward tombedhtrun
Checks have been added in
mbed_greentea.cmake
to keep the old flow working.These checks should be removed once all tests are reworked.
Fixes #14852
Impact of changes
Migration actions required
Documentation
#14854
Pull request type
Test results
Reviewers