Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for Avoid build failures due to setscene errors
Date: Tue, 29 Aug 2017 20:25:50 +0000	[thread overview]
Message-ID: <36fcdba0fe5f4161b32cc01d9bf87985@XBOX02.axis.com> (raw)
In-Reply-To: <20170829200453.2382.2374@do.openembedded.org>

> -----Original Message-----
> From: Patchwork [mailto:patchwork@patchwork.openembedded.org]
> Sent: den 29 augusti 2017 22:05
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: ✗ patchtest: failure for Avoid build failures due to setscene
> errors
> 
> == Series Details ==
> 
> Series: Avoid build failures due to setscene errors
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/8575/
> 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 2454019844)

Argh, why can't this handle combined bitbake and OE-Core changes, i.e., 
changes for Poky. Oh well, separate patches coming up...

> 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

//Peter


  reply	other threads:[~2017-08-29 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 20:00 [PATCH 0/2] Avoid build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 1/2] bitbake: fetch2: Allow Fetch.download() to warn instead of error Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 2/2] sstate.bbclass: Do not cause build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:04 ` ✗ patchtest: failure for Avoid " Patchwork
2017-08-29 20:25   ` Peter Kjellerstedt [this message]
2017-08-29 22:35     ` Philip Balister
2017-08-30  7:41       ` Peter Kjellerstedt
2017-08-29 20:38 ` [PATCH 0/2] " Andre McCurdy
2017-08-29 20:59   ` Peter Kjellerstedt
2017-08-29 21:49     ` Richard Purdie
2017-08-30  6:44       ` Peter Kjellerstedt
2017-08-30  7:54         ` Martin Jansa
2019-11-29 16:48           ` Martin Jansa
2020-01-09 12:26             ` Ricardo Ribalda Delgado
2017-08-30  8:02         ` Richard Purdie
2017-08-30  9:52           ` Peter Kjellerstedt
2017-08-29 22:03     ` Andre McCurdy
2017-08-30  9:55       ` Peter Kjellerstedt

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=36fcdba0fe5f4161b32cc01d9bf87985@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.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