From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
Jussi Kukkonen <jussi.kukkonen@intel.com>
Subject: Re: ✗ patchtest: failure for Fix cve-check (for recipe sysroots)
Date: Thu, 9 Feb 2017 15:41:54 -0600 [thread overview]
Message-ID: <17a51da2-5095-2262-bc91-7eb472c557f8@linux.intel.com> (raw)
In-Reply-To: <20170209195950.9311.78142@do.openembedded.org>
This is a false positive, your series is fine.
The presence of CVE tags on the commit message area must only be done if
the CVE tag is present on the commit subject, not the whole payload.
On 02/09/2017 01:59 PM, Patchwork wrote:
> == Series Details ==
>
> Series: Fix cve-check (for recipe sysroots)
> Revision: 1
> URL : https://patchwork.openembedded.org/series/5241/
> 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 [3/3] cve-check-tool: Use CA cert bundle in correct sysroot
> Issue Missing or incorrectly formatted CVE tag in commit message [test_cve_presence_in_commit_message]
> Suggested fix Include a "CVE-xxxx-xxxx" tag in the commit message
>
>
>
> 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] -> ...).
>
> ---
> Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
>
next prev parent reply other threads:[~2017-02-09 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 19:38 [PATCH 0/3] Fix cve-check (for recipe sysroots) Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 1/3] cve-check.bbclass: Fix dependencies Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 2/3] cve-check-tool: Fixes for recipe sysroots Jussi Kukkonen
2017-02-09 19:38 ` [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot Jussi Kukkonen
2017-11-21 8:04 ` native CA cert bundles (was: Re: [PATCH 3/3] cve-check-tool: Use CA cert bundle in correct sysroot) Patrick Ohly
2017-11-21 12:06 ` Otavio Salvador
2017-11-21 12:21 ` Patrick Ohly
2017-11-21 12:52 ` Otavio Salvador
2017-02-09 19:59 ` ✗ patchtest: failure for Fix cve-check (for recipe sysroots) Patchwork
2017-02-09 21:41 ` Leonardo Sandoval [this message]
2017-02-10 11:55 ` [PATCH 0/3] " Alexander Kanavin
2017-02-10 13:04 ` Burton, Ross
2017-02-10 13:11 ` Alexander Kanavin
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=17a51da2-5095-2262-bc91-7eb472c557f8@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=jussi.kukkonen@intel.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