[OE-core] ✗ patchtest: failure for libgcrypt: CVE-2019-12904 fix Status: Backport Sign off: Shubham Agrawal<shuagr at microsoft.com>

[Patchwork]

== Series Details ==

Series: libgcrypt: CVE-2019-12904 fix Status: Backport Sign off: Shubham Agrawal<shuagr at microsoft.com>
Revision: 1
URL   : https://patchwork.openembedded.org/series/20838/
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            [thud] libgcrypt: CVE-2019-12904 fix Status: Backport Sign off: Shubham Agrawal<shuagr at microsoft.com>
 Issue             Commit shortlog is too long [test_shortlog_length] 
  Suggested fix    Edit shortlog so that it is 90 characters or less (currently 94 characters)

* Patch            [thud] libgcrypt: CVE-2019-12904 fix Status: Backport Sign off: Shubham Agrawal<shuagr at microsoft.com>
 Issue             Patch is missing Signed-off-by [test_signed_off_by_presence] 
  Suggested fix    Sign off the patch (either manually or with "git commit --amend -s")

* Patch            [thud] libgcrypt: CVE-2019-12904 fix Status: Backport Sign off: Shubham Agrawal<shuagr at microsoft.com>
 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             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-support/libgcrypt/files/CVE-2019-12904_p1.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 at 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