Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Jagadeesh Krishnanjanappa <jkrishnanjanappa@mvista.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "[ROCKO] sqlite3: CVE-2017-1528..." and 33 more
Date: Wed, 22 Aug 2018 11:41:14 -0000	[thread overview]
Message-ID: <20180822114114.13844.65522@do.openembedded.org> (raw)
In-Reply-To: <1534936692-11736-1-git-send-email-jkrishnanjanappa@mvista.com>

== Series Details ==

Series: "[ROCKO] sqlite3: CVE-2017-1528..." and 33 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/13659/
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            [ROCKO,16/34] Qemu CVE-2018-11806 slirp-heap-buffer-overflow
 Issue             Shortlog does not follow expected format [test_shortlog_format] 
  Suggested fix    Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"

* Patch            [ROCKO,32/34] 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             Upstream-Status is in incorrect format [test_upstream_status_presence_format] 
  Suggested fix    Fix Upstream-Status format in 0001-CVE-2018-11806-QEMU-slirp-heap-buffer-overflow.patch
  Current          Upstream-status: Backport
  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



      parent reply	other threads:[~2018-08-22 11:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 11:17 [ROCKO][PATCH 01/34] sqlite3: CVE-2017-15286 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 02/34] busybox: CVE-2017-16544 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 03/34] libsndfile1: CVE-2017-14245 CVE-2017-14246 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 04/34] libvorbis: CVE-2017-14160 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 05/34] rpm: CVE-2017-7501 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 06/34] coreutils: CVE-2017-18018 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 07/34] gdk-pixbuf: CVE-2017-1000422 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 08/34] util-linux: CVE-2018-7738 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 09/34] python: CVE-2018-1000030 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 10/34] perl: CVE-2018-6798 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 11/34] curl: CVE-2018-1000300 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 12/34] curl: CVE-2018-1000301 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 13/34] procps: CVE-2018-1124 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 14/34] gnupg: CVE-2018-12020 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 15/34] curl: CVE-2018-0500 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 16/34] Qemu CVE-2018-11806 slirp-heap-buffer-overflow Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 17/34] qemu: CVE-2017-15119 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 18/34] pcmanfm: CVE-2017-8934 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 19/34] openssh: CVE-2017-15906 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 20/34] git: CVE-2017-15298 Jagadeesh Krishnanjanappa
2018-08-22 11:17 ` [ROCKO][PATCH 21/34] libsndfile1: CVE-2017-14634 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 22/34] libarchive: CVE-2017-14503 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 23/34] qemu: CVE-2017-18043 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 24/34] qemu: CVE-2018-7550 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 25/34] qemu: CVE-2018-12617 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 26/34] shadow: CVE-2018-7169 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 27/34] perl: CVE-2018-6797 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 28/34] perl: CVE-2018-6913 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 29/34] wget: CVE-2018-0494 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 30/34] flac: CVE-2017-6888 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 31/34] git: CVE-2018-11235 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 32/34] openssl: CVE-2018-0732 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 33/34] perl: CVE-2018-12015 Jagadeesh Krishnanjanappa
2018-08-22 11:18 ` [ROCKO][PATCH 34/34] 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=20180822114114.13844.65522@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