[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] =?utf-8?q?=E2=9C=97_patchtest=3A_failure_for_libgcrypt?= =?utf-8?q?=3A_CVE-2019-12904_fix_
From:       Patchwork <patchwork () patchwork ! openembedded ! org>
Date:       2019-10-31 18:32:53
Message-ID: 20191031183253.2332.18474 () do
[Download RAW message or body]

== Series Details ==

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

* Patch            [thud] libgcrypt: CVE-2019-12904 fix Upstream-Status: Backport \
Signed-off-by: Shubham Agrawal<shuagr@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")

* Issue             Upstream-Status is in incorrect format \
[test_upstream_status_presence_format]   Suggested fix    Fix Upstream-Status format \
in CVE-2019-12904_p2.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

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[prev in list] [next in list] [prev in thread] [next in thread]