-
Notifications
You must be signed in to change notification settings - Fork 25
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
MDBF-786 - Make build output verbose, as a rule #557
base: dev
Are you sure you want to change the base?
MDBF-786 - Make build output verbose, as a rule #557
Conversation
Enabled VERBOSE=1 for quick builders.
Please can we try to determine (roughly) the amount of storage increase (db and artifact wise) that comes with this? |
@fauust Artifact wise shouldn't be a problem as this is the From my tests, the log output doubles (~1 more line per Make output) but I need to find out how to estimate the size. |
@@ -201,7 +201,7 @@ def getBuildFactoryPreTest(build_type="RelWithDebInfo", additional_args=""): | |||
"additional_args", default=f"{additional_args}" | |||
), | |||
create_package=util.Property("create_package", default="package"), | |||
verbose_build=util.Property("verbose_build", default=""), | |||
verbose_build=util.Property("verbose_build", default="VERBOSE=1"), |
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.
with #606 merged I think --output-sync=target
can be added to this as no bintar builder uses f_quick_build.
d7eb898
to
4be5d7c
Compare
Enabled VERBOSE=1 for quick builders as per request in MDBF-786.