From: Patchwork <patchwork@patchwork.openembedded.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "oe-selftest: extend virgl gtk ..." and 13 more
Date: Wed, 27 Nov 2019 17:02:11 -0000 [thread overview]
Message-ID: <20191127170211.2277.94745@do> (raw)
In-Reply-To: <20191127164003.115980-1-alex.kanavin@gmail.com>
== Series Details ==
Series: "oe-selftest: extend virgl gtk ..." and 13 more
Revision: 1
URL : https://patchwork.openembedded.org/series/21385/
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 [13/14] flex: update to 2.6.4
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 Upstream-Status is in incorrect format [test_upstream_status_presence_format]
Suggested fix Fix Upstream-Status format in 0001-rpmfc.c-do-not-run-file-classification-in-parallel.patch
Current Upstream-Status: Inapppropriate [upstream wants a proper fix]
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-11-27 17:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 16:39 [PATCH 01/14] oe-selftest: extend virgl gtk test to also check the SDL option Alexander Kanavin
2019-11-27 16:39 ` [PATCH 02/14] rpm: upgrade to 4.15.1 Alexander Kanavin
2019-11-28 15:22 ` akuster808
2019-11-28 17:27 ` Alexander Kanavin
2019-11-27 16:39 ` [PATCH 03/14] libdnf: upgrade 0.28.1 -> 0.38.1 Alexander Kanavin
2019-11-27 16:39 ` [PATCH 04/14] dnf: upgrade 4.2.2 -> 4.2.16 Alexander Kanavin
2019-11-27 16:39 ` [PATCH 05/14] rpm: fix spelling in one of the patches' Upstream-Status Alexander Kanavin
2019-11-27 16:39 ` [PATCH 06/14] dummy-sdk-package.inc: do not include files into RREPLACES Alexander Kanavin
2020-01-02 10:17 ` Kang Kai
2020-01-02 18:06 ` Alexander Kanavin
2020-01-03 0:48 ` Kang Kai
2020-01-06 11:34 ` Alexander Kanavin
2020-01-09 2:23 ` Kang Kai
2019-11-27 16:39 ` [PATCH 07/14] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-27 16:39 ` [PATCH 08/14] gettext: " Alexander Kanavin
2019-11-28 15:18 ` akuster808
2019-11-28 17:47 ` Alexander Kanavin
2019-11-27 16:39 ` [PATCH 09/14] lrzsz: fix issues with newer versions of gettext Alexander Kanavin
2019-11-27 16:39 ` [PATCH 10/14] p11-kit: convert to meson Alexander Kanavin
2019-11-27 16:40 ` [PATCH 11/14] sed: upgrade to 4.7 Alexander Kanavin
2019-11-27 16:40 ` [PATCH 12/14] bind: update 9.11.5-P4 -> 9.11.13 Alexander Kanavin
2019-11-27 20:25 ` akuster808
2019-11-28 11:26 ` Alexander Kanavin
2019-11-27 16:40 ` [PATCH 13/14] flex: update to 2.6.4 Alexander Kanavin
2019-11-28 15:14 ` akuster808
2019-11-28 15:26 ` Khem Raj
2019-11-28 15:53 ` Alexander Kanavin
2019-11-27 16:40 ` [PATCH 14/14] gettext: fix failing ptests Alexander Kanavin
2019-11-27 17: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=20191127170211.2277.94745@do \
--to=patchwork@patchwork.openembedded.org \
--cc=alex.kanavin@gmail.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