public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 2/4] cve-check: do not parse error output
Date: Wed,  7 Jun 2017 08:04:29 +0200	[thread overview]
Message-ID: <1496815471-23075-3-git-send-email-peter.marko@siemens.com> (raw)
In-Reply-To: <1496815471-23075-1-git-send-email-peter.marko@siemens.com>
In-Reply-To: <1496647273-9693-1-git-send-email-peter.marko@siemens.com>

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>
---
 meta/classes/cve-check.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 660fe7a..1f0b691 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -172,7 +172,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))
-- 
2.1.4



  parent reply	other threads:[~2017-06-07  6:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  7:21 [PATCH 0/5] cve-check improvements Peter Marko
2017-06-05  7:21 ` [PATCH 1/5] cve-check: honor RM_OLD_IMAGE flag Peter Marko
2017-06-05 11:05   ` Marko, Peter
2017-06-05  7:21 ` [PATCH 2/5] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-05  7:21 ` [PATCH 3/5] cve-check: do not parse error output Peter Marko
2017-06-05  7:21 ` [PATCH 4/5] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-05  7:21 ` [PATCH 5/5] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07  6:04 ` [PATCH v2 0/4] cve-check improvements Peter Marko
2017-06-07  6:04 ` [PATCH v2 1/4] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-07  6:04 ` Peter Marko [this message]
2017-06-07  6:04 ` [PATCH v2 3/4] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-07  6:04 ` [PATCH v2 4/4] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07 16:03   ` Leonardo Sandoval
2017-06-07 16:20     ` Marko, Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1496815471-23075-3-git-send-email-peter.marko@siemens.com \
    --to=peter.marko@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox