Re: ✗ patchtest: failure for "README.qemu: qemuppc64 is not ..." and 1 more

[Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>]

On Mon, 16 Oct 2017 14:39:45 -0400
Randy MacLeod <randy.macleod@windriver.com> wrote:

> On 2017-10-16 12:00 PM, Patchwork wrote:
> > == Series Details ==
> > 
> > Series: "README.qemu: qemuppc64 is not ..." and 1 more
> > Revision: 1
> > URL   : https://patchwork.openembedded.org/series/9358/
> > 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             Added patch file is missing Upstream-Status in the header [test_upstream_status_presence]
> >    Suggested fix    Add Upstream-Status: <status> to the header of meta/recipes-connectivity/openssl/openssl-1.0.2l/0001-openssl-force-soft-link-to-avoid-rare-race.patch (possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)
> > 
> 
> I have:
>     Upstream-status: Inappropriate [build rules rewrite in progress]
> 
> patchtest rules should be case insensitive most of the time and
> particularly for the first character of words in a labels so
>   [Uu]pstream-[Ss]tatus: is okay but not uPsTrEaM-sTaTuS:

This is a topic what have been discussed before and agreed to be strict and make it case sensitive. One of the reason (perhaps not the strongest) for the latter is that it makes much easier the scripting part but there may be other reasons that I can recall.

> 
> Also is there a list server for privately reviewing a patch by email?
> I looked at setting up patchtest locally but got distracted when the
> setup seemed to take more than a few minutes. Maybe I just need
> to focus for longer...

on your current branch, just run the patchtest script located at scripts/contrib/, that would provide basically the same log as the one gotten from patchwork.

> 
> 
> ../Randy
> 
> > 
> > 
> > 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
> > 
> > 
> 
> 
> -- 
> # Randy MacLeod.  WR Linux
> # Wind River an Intel Company
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>