Skip to content

Conversation

RazvanLiviuVarzaru
Copy link
Collaborator

Enabled VERBOSE=1 for quick builders as per request in MDBF-786.

Enabled VERBOSE=1 for quick builders.
@fauust
Copy link
Collaborator

fauust commented Sep 10, 2024

Please can we try to determine (roughly) the amount of storage increase (db and artifact wise) that comes with this?

@RazvanLiviuVarzaru
Copy link
Collaborator Author

RazvanLiviuVarzaru commented Sep 19, 2024

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 Compile step and the output it's not saved on CI.
As for DB let me quickly check in the database what's the average size of the compile log X number of builders with this enabled.

From my tests, the log output doubles (~1 more line per Make output) but I need to find out how to estimate the size.

@RazvanLiviuVarzaru RazvanLiviuVarzaru deleted the feature/verbose-builds branch September 29, 2024 12:58
@RazvanLiviuVarzaru RazvanLiviuVarzaru restored the feature/verbose-builds branch September 29, 2024 12:58
@@ -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"),
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants