All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for "libxml2: fix CVE-2018-9251 and..." and 1 more
Date: Fri, 17 Aug 2018 15:37:24 +0800	[thread overview]
Message-ID: <064dc928-7bbb-b537-75a4-273ecc1dfcfb@windriver.com> (raw)
In-Reply-To: <20180817073257.13840.94208@do.openembedded.org>

On 2018年08月17日 15:32, Patchwork wrote:
> == Series Details ==
>
> Series: "libxml2: fix CVE-2018-9251 and..." and 1 more
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/13574/
> 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_presence_format]
>    Suggested fix    Fix Upstream-Status format in 0001-Verify-that-we-are-not-reading-past-end-of-a-buffer.patch
>    Current          Upstream-Status: Cherry pick from upstream bugzilla [https://bugzilla.nasm.us/show_bug.cgi?id=3392447]
>    Standard format  Upstream-Status: <Valid status>
>    Valid status     Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]

I am not sure which one to choose, the patch is not from
upstream, but its bugzilla, so `Backport' is not accurate

//Hongxu

>
>
> 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
>



  reply	other threads:[~2018-08-17  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  7:22 [PATCH 1/2] libxml2: fix CVE-2018-9251 and CVE-2018-14567 Hongxu Jia
2018-08-17  7:22 ` [PATCH 2/2] nasm: fix CVE-2018-8883 & CVE-2018-8882 & CVE-2018-10016 & CVE-2018-10316 Hongxu Jia
2018-08-17  7:32 ` ✗ patchtest: failure for "libxml2: fix CVE-2018-9251 and..." and 1 more Patchwork
2018-08-17  7:37   ` Hongxu Jia [this message]
2018-08-19 22:16     ` Richard Purdie

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=064dc928-7bbb-b537-75a4-273ecc1dfcfb@windriver.com \
    --to=hongxu.jia@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.