Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for mesa: etnaviv: fix shader miscompilation with more than 16 labels
Date: Thu, 06 Jul 2017 12:32:36 -0500	[thread overview]
Message-ID: <1499362356.24688.21.camel@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqjoFomAmUjRpvAQEZmsFDmc9REmBaSrJbBxQx5Oq1XJQ@mail.gmail.com>

On Thu, 2017-07-06 at 14:01 -0300, Otavio Salvador wrote:
> On Wed, Jul 5, 2017 at 7:01 PM, Patchwork
> <patchwork@patchwork.openembedded.org> wrote:
> > == Series Details ==
> >
> > Series: mesa: etnaviv: fix shader miscompilation with more than 16 labels
> > Revision: 1
> > URL   : https://patchwork.openembedded.org/series/7589/
> > 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 de79149545)
> 
> Checking the commit it has tried to apply it was indeed going to fail.
> As I mentioned on the commit itself it required the upgrade which has
> been merged on master. Just triggering the test again should work just
> fine.

patchtest is pretty stupid, it just tries to merge on current master's
HEAD (not to other stable branches even if patch specifies it).
patchtest executes every half an hour, so unless you send another series
revision to the ML (which I believe there is no need for the reason you
mentioned) it will be retested.

Leo

> 
> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750




      reply	other threads:[~2017-07-06 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 21:36 [PATCH] mesa: etnaviv: fix shader miscompilation with more than 16 labels Otavio Salvador
2017-07-05 22:01 ` ✗ patchtest: failure for " Patchwork
2017-07-06 17:01   ` Otavio Salvador
2017-07-06 17:32     ` 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=1499362356.24688.21.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    /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