From 6d8a17f4c50be292990e37de65630a6b84466ee6 Mon Sep 17 00:00:00 2001 From: Peter Marko Date: Wed, 7 Jun 2017 08:04:29 +0200 Subject: cve-check: do not parse error output Sometimes there are control messages in cve-check-tool printed to stderr. These lead to parsing error and thus failed build. This can happen for instance when cve database needs to be refreshed during build. Signed-off-by: Peter Marko Signed-off-by: Ross Burton --- meta/classes/cve-check.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/classes/cve-check.bbclass') diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass index 09487f1174..f5d73fdeba 100644 --- a/meta/classes/cve-check.bbclass +++ b/meta/classes/cve-check.bbclass @@ -176,7 +176,7 @@ def check_cves(d, patched_cves): f.write("%s,%s,%s," % (bpn, pv, cves)) cmd.append(faux) - output = subprocess.check_output(cmd, stderr=subprocess.STDOUT).decode("utf-8") + output = subprocess.check_output(cmd).decode("utf-8") bb.debug(2, "Output of command %s:\n%s" % ("\n".join(cmd), output)) except subprocess.CalledProcessError as e: bb.warn("Couldn't check for CVEs: %s (output %s)" % (e, e.output)) -- cgit 1.2.3-korg