On 13 July 2017 at 21:38, Patchwork <patchw...@patchwork.openembedded.org> wrote:
> == Series Details == > > Series: libgcrypt: fix CVE-2017-9526 (rev2) > Revision: 2 > Not sure if this should be a patchwork bug or not? This patch is showing up as a revision 2 of the other patch when in reality they are patches for two separate branches. - Jussi > URL : https://patchwork.openembedded.org/series/7732/ > 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 [pyro] libgcrypt: fix CVE-2017-9526 > 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 > > > > 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 > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
