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 V3] selftest/manifest.py: Test support for manifests
Date: Fri, 16 Oct 2015 15:05:21 -0500 [thread overview]
Message-ID: <1445025921.6970.19.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaA-QhLiy5aUno_AAZpFAEnajOLEXuZU5+kPoPFRqeYow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
this test does a one way check from the .manifest to the pkgdata dir.
This test is looking for entries in the manifest that do not exist in
the pkgdata dir. The bug you mention is the other way around, things
that are installed in the rootfs but not listed in the manifest. I
believe a test for this would be necessary too though I am not sure
that the bug is a genuine error yet.
Benjamin
On Fri, 2015-10-16 at 17:20 +0100, Burton, Ross wrote:
> On 7 October 2015 at 20:41, Benjamin Esquivel <
> benjamin.esquivel@linux.intel.com> wrote:
> > tests added:
> > - manifest.VerifyManifest.test_image_manifest_entries
> >
> This test case isn't exposing a known bug in the manifests, where the
> installed package list and the manifest don't match, specifically the
> manifest is missing the locale packages (8444).
>
> Ross
[-- Attachment #2: Type: text/html, Size: 1330 bytes --]
prev parent reply other threads:[~2015-10-16 20:05 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
2015-10-07 19:41 ` [PATCH V3] " Benjamin Esquivel
2015-10-16 16:20 ` Burton, Ross
2015-10-16 20:05 ` Benjamin Esquivel [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=1445025921.6970.19.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