All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Francisco Pedraza <francisco.j.pedraza.gonzalez@intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] oeqa/selftest: Adds verification for the integrity compressed images
Date: Thu, 08 Jun 2017 09:34:16 -0500	[thread overview]
Message-ID: <1496932456.26945.157.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbgJFFBPoF=CsOEYauBn1_uDX66hh1zvE5Xw81BiRmR4A@mail.gmail.com>

On Thu, 2017-06-08 at 11:51 +0100, Burton, Ross wrote:
> 
> On 6 June 2017 at 20:29, Francisco Pedraza
> <francisco.j.pedraza.gonzalez@intel.com> wrote:
>         Added verification for images compression divided in 3 steps.
>         1. Add IMAGE_FSTYPES += "[type(s)]" to ~/conf/local.conf
>         2. Build a "core-image-minimal" using this configuration.
>         3. Verify that the image compressed file is present in rootfs
>         directory.
>         YOCTO[#10745]
> 
> Still fails on the main AB:
> 
> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/911/steps/Running%20oe-selftest/logs/stdio
> 

perhaps the fails are expected as commented on 

https://bugzilla.yoctoproject.org/show_bug.cgi?id=10745#c9






> 
> Ross
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core




      reply	other threads:[~2017-06-08 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 19:29 [PATCH v3] oeqa/selftest: Adds verification for the integrity compressed images Francisco Pedraza
2017-06-08 10:51 ` Burton, Ross
2017-06-08 14:34   ` 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=1496932456.26945.157.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=francisco.j.pedraza.gonzalez@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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 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.