All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Date: Tue, 25 Apr 2017 11:06:09 -0500	[thread overview]
Message-ID: <1493136369.1798.26.camel@linux.intel.com> (raw)
In-Reply-To: <20170420010154.26296.84391@do.openembedded.org>

On Thu, 2017-04-20 at 01:01 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/6429/
> 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            busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
>  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

Andre,

there is no need to send a second revision due to the above patchtest
issue. The system detected the CVE on shortlog thus triggering the check
on the commit message, but for this case there is no need. Will fix
this.

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
> 




  reply	other threads:[~2017-04-25 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  0:47 [PATCH] busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag Andre McCurdy
2017-04-20  1:01 ` ✗ patchtest: failure for " Patchwork
2017-04-25 16:06   ` Leonardo Sandoval [this message]
2017-04-25 21:11     ` Andre McCurdy

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=1493136369.1798.26.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 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.