All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Joe MacDonald <Joe_MacDonald@mentor.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for radvd: 2.14 -> 2.17
Date: Mon, 24 Jul 2017 09:27:46 -0500	[thread overview]
Message-ID: <1500906466.2230.16.camel@linux.intel.com> (raw)
In-Reply-To: <20170724124450.4ta2qpzta6u2gqa5@mentor.com>

On Mon, 2017-07-24 at 08:44 -0400, Joe MacDonald wrote:
> Please note that the advice from patchtest, in this case, may be
> misleading.  The main issue, I think, is this went to the wrong mailing
> list.
> 
You are right, message is misleading. There was a problem with the test
that checks the correct mailing list, hopefully future messages will
provide better info.

Leo


> -J.
> 
> [[OE-core] ✗ patchtest: failure for radvd: 2.14 -> 2.17] On 17.07.24 (Mon 06:01) Patchwork wrote:
> 
> > == Series Details ==
> > 
> > Series: radvd: 2.14 -> 2.17
> > Revision: 1
> > URL   : https://patchwork.openembedded.org/series/7876/
> > 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             Series does not apply on top of target branch [test_series_merge_on_head] 
> >   Suggested fix    Rebase your series on top of targeted branch
> >   Targeted branch  master (currently at 514e9be6b0)
> > 
> > 
> > 
> > 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




      reply	other threads:[~2017-07-24 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  5:58 [meta-networking] [PATCH] radvd: 2.14 -> 2.17 Huang Qiyu
2017-07-24  6:01 ` ✗ patchtest: failure for " Patchwork
2017-07-24 12:44   ` Joe MacDonald
2017-07-24 14:27     ` 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=1500906466.2230.16.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=Joe_MacDonald@mentor.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.