From 728b96133dc52900a56ebacdb297622a8c3b5ad0 Mon Sep 17 00:00:00 2001 From: "Owen W. Taylor" Date: Thu, 29 Oct 2020 11:04:59 -0400 Subject: [PATCH] local builds: Don't call mock with -v Verbose output from mock is not useful for someone trying to figure out why their module build failed, and in fact makes it harder by adding quite a bit of extraneous noise. --- module_build_service/builder/MockModuleBuilder.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/module_build_service/builder/MockModuleBuilder.py b/module_build_service/builder/MockModuleBuilder.py index 370339c4..5ca4eb5e 100644 --- a/module_build_service/builder/MockModuleBuilder.py +++ b/module_build_service/builder/MockModuleBuilder.py @@ -655,7 +655,7 @@ class MockModuleBuilder(GenericBuilder): try: # Initialize mock. execute_cmd( - ["mock", "-v", "-r", mock_config, "--init"], + ["mock", "-r", mock_config, "--init"], output=mock_output_log, ) @@ -804,7 +804,7 @@ class BaseBuilder(object): def __init__(self, config, resultsdir): self.config = config self.resultsdir = resultsdir - self.cmd = ["mock", "-v", "-r", config, "--no-clean", "--resultdir=%s" % resultsdir] + self.cmd = ["mock", "-r", config, "--no-clean", "--resultdir=%s" % resultsdir] def build(self, output): execute_cmd(self.cmd, output=output)