From: Patchwork <patchwork@patchwork.openembedded.org>
To: shuagr97@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for libgcrypt: CVE-2019-12904 fix Upstream-Status: Backport Signed-off-by: Shubham Agrawal<shuagr@microsoft.com>
Date: Thu, 31 Oct 2019 18:32:53 -0000 [thread overview]
Message-ID: <20191031183253.2332.18474@do> (raw)
In-Reply-To: <1572545645-64707-1-git-send-email-shuagr@microsoft.com>
== 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
prev parent reply other threads:[~2019-10-31 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 18:14 [thud][PATCH] libgcrypt: CVE-2019-12904 fix Upstream-Status: Backport Signed-off-by: Shubham Agrawal<shuagr@microsoft.com> shuagr97
2019-10-31 18:32 ` 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=20191031183253.2332.18474@do \
--to=patchwork@patchwork.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=shuagr97@gmail.com \
/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