From: Patchwork <patchwork@patchwork.openembedded.org>
To: Anuj Mittal <anuj.mittal@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for zeus review/pull request
Date: Fri, 22 Nov 2019 12:02:08 -0000 [thread overview]
Message-ID: <20191122120208.2329.39691@do> (raw)
In-Reply-To: <cover.1574422359.git.anuj.mittal@intel.com>
== Series Details ==
Series: zeus review/pull request
Revision: 1
URL : https://patchwork.openembedded.org/series/21313/
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 [zeus,01/15] lz4: Whitelist CVE-2014-4715
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"
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-11-22 12:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 11:38 [zeus][PATCH 00/15] zeus review/pull request Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 01/15] lz4: Whitelist CVE-2014-4715 Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 02/15] libsoup: set CVE_PRODUCT Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 03/15] cve-check: we don't actually need to unpack to check Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 04/15] cve-update-db-native: don't refresh more than once an hour Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 05/15] cve-update-db-native: don't hardcode the database name Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 06/15] cve-update-db-native: add an index on the CVE ID column Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 07/15] cve-update-db-native: clean up proxy handling Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 08/15] cve-check: rewrite look to fix false negatives Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 09/15] cve-check: neaten get_cve_info Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 10/15] cve-check: fetch CVE data once at a time instead of in a single call Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 11/15] boost: fix build for x32 Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 12/15] Revert "devtool/standard.py: Not filtering devtool workspace for devtool finish" Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 13/15] python: update to 2.7.17 Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 14/15] tiff: Refresh patch Anuj Mittal
2019-11-22 11:39 ` [zeus][PATCH 15/15] bind: fix CVE-2019-6471 and CVE-2018-5743 Anuj Mittal
2019-11-22 12:02 ` 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=20191122120208.2329.39691@do \
--to=patchwork@patchwork.openembedded.org \
--cc=anuj.mittal@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