From: Mark Hatle <mark.hatle@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Cc: peter.kjellerstedt@axis.com
Subject: Re: [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro
Date: Wed, 16 Aug 2017 10:37:46 -0500 [thread overview]
Message-ID: <e285fe7c-320d-db44-98fd-ff1d06df5706@windriver.com> (raw)
In-Reply-To: <1502890461.13978.127.camel@linuxfoundation.org>
On 8/16/17 8:34 AM, Richard Purdie wrote:
> On Tue, 2017-08-15 at 16:41 -0500, Mark Hatle wrote:
>> From the comments to the original patch, the only not addressed was
>> adding an OE self-test for this behavior. I tried to do this, but I
>> don't see any existing tests that build a recipe and inspect the
>> results of the built package. I'm not sure of any other way to
>> identify if things are working or not.
> oe-selftest can do this.
>
Are there any examples? I was looking there and simply didn't see any. I saw
the packaging for instance exercised python interfaces, version comparison
tools, etc.. but nothing that built a recipe/package and then verified the
contents were 'correct'.
Ideally the test would be to fabricate something with a known set of file
dependencies, produce a package from it and then verify that the package
properly included those dependencies.
I had looked at just picking some random library out of the deploy directory,
and doing a pattern search on it's provides.. but I'm not sure that type of test
would be very robust.
--Mark
next prev parent reply other threads:[~2017-08-16 15:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 21:41 [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro Mark Hatle
2017-08-15 21:41 ` [PATCH 1/6 v2] rpm: Add dependencies on bash, perl and python3-core Mark Hatle
2017-08-15 21:41 ` [PATCH 2/6 v2] git: Do not install git cvsserver and git svn by default Mark Hatle
2017-08-15 21:41 ` [PATCH 3/6 v2] texinfo: Avoid a problem with a dependency on perl(Locale::gettext_xs) Mark Hatle
2017-08-15 21:41 ` [PATCH 4/6 v2] package_rpm.bbclass: Filter out unwanted file deps for nativesdk packages Mark Hatle
2017-08-15 21:41 ` [PATCH 5/6 v2] package.bbclass: Restore functionality to detect RPM dependencies Mark Hatle
2017-08-15 21:41 ` [PATCH 6/6 v2] rpm: Disable perl dependency generation Mark Hatle
2017-08-16 5:19 ` [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro akuster808
2017-08-16 13:43 ` Richard Purdie
2017-08-16 20:43 ` Peter Kjellerstedt
2017-08-16 13:34 ` Richard Purdie
2017-08-16 15:18 ` Mark Hatle
2017-08-16 15:37 ` Mark Hatle [this message]
2017-08-17 10:53 ` Alexander Kanavin
2017-08-17 13:01 ` Peter Kjellerstedt
2017-08-17 13:17 ` Alexander Kanavin
2017-08-17 14:41 ` Mark Hatle
2017-08-17 14:37 ` Mark Hatle
2017-08-16 15:32 ` ✗ patchtest: failure for Fix RPM4 regressions based on Pyro (rev2) Patchwork
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=e285fe7c-320d-db44-98fd-ff1d06df5706@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.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 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.