From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for Vulkan improvements
Date: Wed, 05 Jul 2017 09:52:37 -0500 [thread overview]
Message-ID: <1499266357.24688.13.camel@linux.intel.com> (raw)
In-Reply-To: <20170705123124.2383.65519@do.openembedded.org>
On Wed, 2017-07-05 at 12:31 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: Vulkan improvements
> Revision: 1
> URL : https://patchwork.openembedded.org/series/7583/
> 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:
>
>
>
> * Issue Upstream-Status is in incorrect format [test_upstream_status_format]
> Suggested fix Fix Upstream-Status format in meta/recipes-graphics/vulkan/vulkan-demos/0001-Don-t-build-demos-with-questionably-licensed-data.patch so it is one of: Pending, Submitted, Accepted, Backport, Denied, Inappropriate
>
Jussi, just checking this issue an apparently you misspelled the
upstream-status. In the other hand, I have improved the output of this
check so it would be easier to see what went wrong (will show current
status and valid ones in separate lines).
Leo
>
>
> 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
>
prev parent reply other threads:[~2017-07-05 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:28 [PATCH 0/6] Vulkan improvements Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 1/6] vulkan: Upgrade 1.0.39.1 -> 1.0.51.0 Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 2/6] assimp: Add as dependency of vulkan-demos Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 3/6] vulkan-demos: Add recipe Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 4/6] gstreamer1.0-plugins-bad: Add vulkan PACKAGECONFIG Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 5/6] mesa, gstreamer: Add "vulkan" DISTRO_FEATURE Jussi Kukkonen
2017-07-05 12:28 ` [PATCH 6/6] vulkan: RRECOMMEND mesa drivers Jussi Kukkonen
2017-07-05 12:31 ` ✗ patchtest: failure for Vulkan improvements Patchwork
2017-07-05 14:52 ` Leonardo Sandoval [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=1499266357.24688.13.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.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