From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for "README.qemu: qemuppc64 is not ..." and 1 more
Date: Tue, 17 Oct 2017 12:53:57 -0500 [thread overview]
Message-ID: <20171017125357.29113803f44029838af18f7d@linux.intel.com> (raw)
In-Reply-To: <20171016141306.418e7a6502139ed4c2e180c3@linux.intel.com>
>
> >
> > 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,
just test the patchtest script under contrib and I see some exceptions coming from the execution which turn into failures and false positives. this script creates a virtual environment then clones repos and start testing patches starting from master to HEAD. This virtual environment is what is causing problems. I will fix it soon but for the time being a server is doing the test for you :)
Leo
>
> >
> >
> > ../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>
> --
> _______________________________________________
> 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>
prev parent reply other threads:[~2017-10-17 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 15:00 [PATCH 1/2] README.qemu: qemuppc64 is not supported Randy MacLeod
2017-10-16 15:00 ` [PATCH 2/2] openssl: force soft link to avoid rare race Randy MacLeod
2017-10-16 15:24 ` Randy MacLeod
2017-10-16 16:00 ` ✗ patchtest: failure for "README.qemu: qemuppc64 is not ..." and 1 more Patchwork
2017-10-16 18:39 ` Randy MacLeod
2017-10-16 19:13 ` Leonardo Sandoval
2017-10-17 17:53 ` 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=20171017125357.29113803f44029838af18f7d@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