diff options
| author |   Peter Marko <peter.marko@siemens.com> | 2017-06-07 08:04:29 +0200 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-06-12 15:04:08 +0100 |
| commit | 6d8a17f4c50be292990e37de65630a6b84466ee6 (patch) | |
| tree | 38c5910770a415e66fea74cb874756961463153f /meta/classes/cve-check.bbclass | |
| parent | 85b4941c71a0e3c08a8c48d52a94dfe2897d2c92 (diff) | |
| download | openembedded-core-contrib-6d8a17f4c50be292990e37de65630a6b84466ee6.tar.gz | |
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 <peter.marko@siemens.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes/cve-check.bbclass')
| -rw-r--r-- | meta/classes/cve-check.bbclass | 2 |
1 files changed, 1 insertions, 1 deletions
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)) |