Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Ng, Wei Tee" <wei.tee.ng@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for initramfs-framework: include install module in recipe for installation
Date: Thu, 13 Jul 2017 09:49:44 -0500	[thread overview]
Message-ID: <1499957384.5349.67.camel@linux.intel.com> (raw)
In-Reply-To: <CBAEED2EB06BF94889E80B47A33FE329EDA5E3@PGSMSX105.gar.corp.intel.com>

On Thu, 2017-07-13 at 06:36 +0000, Ng, Wei Tee wrote:
> The reason for this patchtest failure is because of this patch have a dependency on another patch which is:
> 	initramfs-framework: module to support boot live image
> Here you go for the link of this patch: http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139570.html 
> 

Any reason for not having that missing patch in this series? patchtest
just tries to patch in latest master without taking into account any
pending patch pending on the ML.

Leo


> Regards,
> Wei Tee
> 
> -----Original Message-----
> From: Patchwork [mailto:patchwork@patchwork.openembedded.org] 
> Sent: Thursday, July 13, 2017 2:31 PM
> To: Ng, Wei Tee <wei.tee.ng@intel.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: ✗ patchtest: failure for initramfs-framework: include install module in recipe for installation
> 
> == Series Details ==
> 
> Series: initramfs-framework: include install module in recipe for installation
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/7726/
> 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 b1c4661742)
> 
> 
> 
> 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
> 




  reply	other threads:[~2017-07-13 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 23:01 [poky][master][PATCH 0/1] initramfs-framework: include install module in recipe for installation wei.tee.ng
2017-07-12 23:01 ` [PATCH 1/1] " wei.tee.ng
2017-07-14 17:13   ` Otavio Salvador
2017-07-17  2:18     ` Ng, Wei Tee
2017-07-13  6:31 ` ✗ patchtest: failure for " Patchwork
2017-07-13  6:36   ` Ng, Wei Tee
2017-07-13 14:49     ` Leonardo Sandoval [this message]
2017-07-17  1:18       ` Ng, Wei Tee

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=1499957384.5349.67.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wei.tee.ng@intel.com \
    /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