-
Notifications
You must be signed in to change notification settings - Fork 3k
Add define to skip greentea sync #9835
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
Conversation
@orenc17, thank you for your changes. |
Hmm. @orenc17 Would you mind sharing how you'd expect this to be used? Does this new macro also need a Docs PR and Release Notes blurb? |
I also do not understand this change. What use case is there and why greentea would include "no greentea" macro? |
@ARMmbed/mbed-os-core Can you review, please |
This is the general idea: tests are usually run using greentea and this is very convenient , except when debugging them. if a test is complied for greentea it will wait for a green tea command before starting making debugging it a pain. for these scenarios it is useful to build the same test using exactly the same config but leave out the greentea setup call, which will yield a very similar binary, but one that doesn't wait on startup and is easy to debug. |
Hmm, considering that the use of this macro isn't new (https://github.com/ARMmbed/mbed-os/search?q=NO_GREENTEA&unscoped_q=NO_GREENTEA), I think it's fine to bring in. It's also curious that the ARM_MUSCA_A1 PR is also using it: https://github.com/ARMmbed/mbed-os/pull/9221/files#diff-088d539546fc854c07455c735a069539R441
Considering that this is already in use in the repo, this needs docs (CC @AnotherButler) |
features/frameworks/greentea-client/source/greentea_test_env.cpp
Outdated
Show resolved
Hide resolved
Co-Authored-By: orenc17 <[email protected]>
@cmonr good catch |
CI started whilst wainting on final reviews |
Test run: FAILEDSummary: 1 of 8 test jobs failed Failed test jobs:
|
Info: A CI config issue appears to be affecting Other build failures should still be investigated, if any. Will restart CI when appropriate. |
Only some small subset, used in psa/spm files . Anyway, looks fine to me and also used something similar previously. One last question before restarting CI: why not added as config as well with some help text. We got already config file there - if this macro is not documented (I would assume this would go only in the sources, not known to anyone). |
Not sure if we shall rename but this is what I understood from this PR and how it was used (thus used skip in the name). |
@0xc0170 the idea of putting this define in an mbed_lib.json crossed my mind, but the thing is for a user to actually change this, the user will need to compile his test with an mbed_app.json so i would like to stick with the very simple and stupid -DNO_GREENTEA |
Valid point. Will need to be documented (otherwise this is hidden feature :) ) @ARMmbed/mbed-os-core please review |
old build-ARM hook set green, so does not potentially cause issues when/if rebuilding without commits in between. |
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 this addition 👍
CI restarted. Afaik, restarting a single build job won't propigate successfully, so restarting from scratch |
Test run: SUCCESSSummary: 13 of 13 test jobs passed |
Description
Add a define to allow debuging greentea tests that do not require input from host without host-tests
Pull request type
Reviewers
Release Notes