From: Patchwork <patchwork@patchwork.openembedded.org>
To: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "[SUMO] libsndfile1: CVE-2017-1..." and 18 more
Date: Wed, 22 Aug 2018 11:41:13 -0000 [thread overview]
Message-ID: <20180822114113.13841.98112@do.openembedded.org> (raw)
In-Reply-To: <1534936615-11658-1-git-send-email-jkrishnanjanappa@mvista.com>
== Series Details ==
Series: "[SUMO] libsndfile1: CVE-2017-1..." and 18 more
Revision: 1
URL : https://patchwork.openembedded.org/series/13658/
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:
* Patch [SUMO,17/19] openssl: CVE-2018-0732
Issue Missing or incorrectly formatted CVE tag in included patch file [test_cve_tag_format]
Suggested fix Correct or include the CVE tag on cve patch with format: "CVE: CVE-YYYY-XXXX"
* Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence]
Suggested fix Sign off the added patch file (meta/recipes-extended/libarchive/libarchive/CVE-2017-14503.patch)
* Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format]
Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-extended/libarchive/libarchive/CVE-2017-14503.patch
Standard format Upstream-Status: <Valid status>
Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]
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] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
prev parent reply other threads:[~2018-08-22 11:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 11:16 [SUMO][PATCH 01/19] libsndfile1: CVE-2017-14245 CVE-2017-14246 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 02/19] libvorbis: CVE-2017-14160 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 03/19] coreutils: CVE-2017-18018 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 04/19] python: CVE-2018-1000030 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 05/19] perl: CVE-2018-6798 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 06/19] procps: CVE-2018-1124 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 07/19] gnupg: CVE-2018-12020 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 08/19] libsndfile1: CVE-2017-14634 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 09/19] libarchive: CVE-2017-14503 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 10/19] qemu: CVE-2018-7550 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 11/19] qemu: CVE-2018-12617 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 12/19] shadow: CVE-2018-7169 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 13/19] perl: CVE-2018-6797 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 14/19] perl: CVE-2018-6913 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 15/19] flac: CVE-2017-6888 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 16/19] git: CVE-2018-11235 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 17/19] openssl: CVE-2018-0732 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 18/19] perl: CVE-2018-12015 Jagadeesh Krishnanjanappa
2018-08-22 11:16 ` [SUMO][PATCH 19/19] libgcrypt: CVE-2018-0495 Jagadeesh Krishnanjanappa
2018-08-22 11:41 ` Patchwork [this message]
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=20180822114113.13841.98112@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=jkrishnanjanappa@mvista.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