From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] oeqa/selftest/sstatetests: Add test that MACHINE doesn't change target sigs
Date: Wed, 30 Sep 2015 17:43:32 +0100 [thread overview]
Message-ID: <1443631412.5162.130.camel@linuxfoundation.org> (raw)
In-Reply-To: <20150930162101.GE2405@jama>
On Wed, 2015-09-30 at 18:21 +0200, Martin Jansa wrote:
> On Wed, Sep 30, 2015 at 02:49:23PM +0100, Richard Purdie wrote:
> > When we change between two machines with the same tune, we shouldn't see
> > rebuilds of binaries. This adds a test for this using the qemux86copy
> > machine. We also extend the test to cover multilibs.
>
> 2nd level of this test is to verify that all allarch recipes have the
> same signatures even for 2 MACHINEs with different tunes.
>
> Thanks for looking into this.
There is already another test in the file which covers that and some
nativesdk constraints too.
Cheers,
Richard
prev parent reply other threads:[~2015-09-30 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:49 [PATCH] oeqa/selftest/sstatetests: Add test that MACHINE doesn't change target sigs Richard Purdie
2015-09-30 16:21 ` Martin Jansa
2015-09-30 16:43 ` Richard Purdie [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=1443631412.5162.130.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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.