-
Notifications
You must be signed in to change notification settings - Fork 3k
tools: add silent option to build #11457
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
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.
Why is this required? It would be helpful if the PR description explained this.
Title should provide be more descriptive plus as well the commits if we add/remove something (to answer there a question "why are these being added/removed"). |
Reason added |
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.
Mixing few not relevant things but LGTM
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.
Some general comments for going forward though:
- PRs should generally contain only self contained fixes (or certainly in specific commits anyway). Do not mix new changes with general tidy ups etc
- Where is the new flag used ? Would be good to have something in the description covering what the knock on effects are of this?
While this is in CI, please add details to the above review |
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
@mark-edgeworth @madchutney Can you please review if all good here? |
It's set as refactor, thus 5.15 ? |
@mark-edgeworth @madchutney bump... |
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.
Looks ok to me.
As this is test code @jamesbeyond may want to comment too... |
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.
--silent
already there is the build CLI, this make sense if we have the same CLI option for the test, especially it improves the test performance
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
Add silent option in test.py and remove some not needed lines. Silent option is need to make CI build faster without logs. If build fails then it will be rebuild with verbose flag. Most of builds success, so then this save time
Pull request type
Reviewers
@adbridge @madchutney
Release Notes