Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Fix multiple CVEs
Date: Wed, 14 Jun 2017 15:31:38 -0000	[thread overview]
Message-ID: <20170614153138.1043.27099@do.openembedded.org> (raw)
In-Reply-To: <1497454006-13902-1-git-send-email-andrej.valek@siemens.com>

== Series Details ==

Series: Fix multiple CVEs
Revision: 1
URL   : https://patchwork.openembedded.org/series/7243/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue             Series cannot be parsed correctly due to malformed diff lines [test_mbox_format] 
  Suggested fix    Create the series again using git-format-patch and ensure it can be applied using git am
  Diff line         diff --git a/meta/recipes-core/libxml/libxml2_2.9.4.bb b/meta/recipes-core/libxml/libxml2_2.9.4.bb


* Issue             Series does not apply on top of target branch [test_series_merge_on_head] 
  Suggested fix    Rebase your series on top of targeted branch
  Targeted branch  master (currently at 059846662f)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe



  parent reply	other threads:[~2017-06-14 15:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 15:26 [PATCH 0/7] Fix multiple CVEs Andrej Valek
2017-06-14 15:26 ` [PATCH 1/7] libxml2-2.9.4: Disable LeakSanitizer when running API testsFix CVE-2016-4658 Andrej Valek
2017-06-14 16:37   ` Burton, Ross
2017-06-14 15:26 ` [PATCH 2/7] libxml2-2.9.4: Avoid reparsing and simplify control flow in xmlParseStartTag2 Andrej Valek
2017-06-14 15:26 ` [PATCH 3/7] libxml2: Fix CVE-2017-9047 and CVE-2017-9048 Andrej Valek
2017-06-14 15:26 ` [PATCH 4/7] libxml2: Fix CVE-2017-9049 and CVE-2017-9050 Andrej Valek
2017-06-14 15:26 ` [PATCH 5/7] libxml2-2.9.4: Fix CVE-2017-5969 Andrej Valek
2017-06-14 15:26 ` [PATCH 6/7] libxml2: Fix CVE-2017-0663 Andrej Valek
2017-06-14 15:26 ` [PATCH 7/7] libxml2: Revert "Add an XML_PARSE_NOXXE flag to block all entities loading even local" Andrej Valek
2017-06-14 15:31 ` Patchwork [this message]
2017-06-15  6:34 ` [PATCH v2 0/7] libxml2: Fix multiple CVEs Andrej Valek
2017-06-15  6:34 ` [PATCH v2 1/7] libxml2: Disable LeakSanitizer when running API tests Andrej Valek
2017-06-15 11:31   ` Burton, Ross
2017-06-15 11:42     ` Andrej Valek
2017-06-15 11:47       ` Burton, Ross
2017-06-15 12:13         ` Andrej Valek
2017-06-15  6:34 ` [PATCH v2 2/7] libxml2: Avoid reparsing and simplify control flow in xmlParseStartTag2 Andrej Valek
2017-06-15  6:34 ` [PATCH v2 3/7] libxml2: Fix CVE-2017-9047 and CVE-2017-9048 Andrej Valek
2017-06-15  6:34 ` [PATCH v2 4/7] libxml2: Fix CVE-2017-9049 and CVE-2017-9050 Andrej Valek
2017-06-15  6:34 ` [PATCH v2 5/7] libxml2: Fix CVE-2017-5969 Andrej Valek
2017-06-15  6:34 ` [PATCH v2 6/7] libxml2: Fix CVE-2017-0663 Andrej Valek
2017-06-15  6:34 ` [PATCH v2 7/7] libxml2: Revert "Add an XML_PARSE_NOXXE flag to block all entities loading even local" Andrej Valek

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=20170614153138.1043.27099@do.openembedded.org \
    --to=patchwork@patchwork.openembedded.org \
    --cc=andrej.valek@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