Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Benjamin Esquivel <benjamin.esquivel@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] selftest/manifest.py: Test support for manifests
Date: Thu, 10 Sep 2015 16:41:14 -0500	[thread overview]
Message-ID: <1441921274.14702.2.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZWChOX1NRpFoc=FwYay76-mOXhmeMdJU6=0JuKQNzJdQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

Thanks for the notice, I'll check it up.
Benjamin
On Thu, 2015-09-10 at 10:52 +0100, Burton, Ross wrote:
> 
> On 2 September 2015 at 21:18, Benjamin Esquivel <
> benjamin.esquivel@linux.intel.com> wrote:
> > adding support for tests to verify manifest collections
> > (i.e. all the manifests found in a given dir) checking them
> > to provide entries that exist in an specified pkgdata dir
> > 
> > tests added:
> >  -adding an SDK manifest test
> >  -adding a core-image-minimal manifest test
> > test support written for future tests:
> >  -adding a setUpClass that supports other tests
> >  -a get dir from bb var function that verifies if the dir exists
> >  -an initial ManifestCollection and ManifestEntry classes defined
> >  -check for the paths and fail gracefully if not there
> >  -debug prints for failure analysis
> > 
> Just ran this on the autobuilder:
> 
> FAIL: test_image_manifest_entries
> (oeqa.selftest.manifest.VerifyManifest)
> Verifying the image manifest entries exist
> ---------------------------------------------------------------------
> -
> Traceback (most recent call last):
>   File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe
> -selftest/build/meta/lib/oeqa/selftest/manifest.py", line 165, in
> test_image_manifest_entries
>     if m_collection.errors: self.fail()
> AssertionError: None
> 
> Ross

[-- Attachment #2: Type: text/html, Size: 1920 bytes --]

  reply	other threads:[~2015-09-10 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 12:26 [PATCH] selftest/manifest.py: Test to verify rootfs manifest Benjamin Esquivel
2015-08-27  8:34 ` Paul Eggleton
2015-08-27 15:50   ` Benjamin Esquivel
2015-08-28  9:18     ` Paul Eggleton
2015-09-02 20:18       ` [PATCH v2] selftest/manifest.py: Test support for manifests Benjamin Esquivel
2015-09-10  9:52         ` Burton, Ross
2015-09-10 21:41           ` Benjamin Esquivel [this message]
2015-10-07 19:41             ` [PATCH V3] " Benjamin Esquivel
2015-10-16 16:20               ` Burton, Ross
2015-10-16 20:05                 ` Benjamin Esquivel

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=1441921274.14702.2.camel@linux.intel.com \
    --to=benjamin.esquivel@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox