All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] meta-selftest: Add qemux86copy machine
Date: Wed, 30 Sep 2015 18:19:31 +0200	[thread overview]
Message-ID: <20150930161931.GD2405@jama> (raw)
In-Reply-To: <1443628787.5162.122.camel@linuxfoundation.org>

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

On Wed, Sep 30, 2015 at 04:59:47PM +0100, Richard Purdie wrote:
> On Wed, 2015-09-30 at 16:28 +0200, Martin Jansa wrote:
> > On Wed, Sep 30, 2015 at 02:47:13PM +0100, Richard Purdie wrote:
> > > I know Martin finds something like this useful for testing sstate signatures,
> > > this adds one to meta-selftest so we can use it from oe-selftest in the sstate
> > > tests there too.
> > > 
> > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > 
> > > diff --git a/meta-selftest/conf/machine/qemux86copy.conf b/meta-selftest/conf/machine/qemux86copy.conf
> > > new file mode 100644
> > > index 0000000..bcce2f5
> > > --- /dev/null
> > > +++ b/meta-selftest/conf/machine/qemux86copy.conf
> > > @@ -0,0 +1,3 @@
> > > +require conf/machine/qemux86.conf
> > > +
> > > +MACHINEOVERRIDES .= ":qemux86"
> > 
> > I wasn't changing MACHINEOVERRIDES (in case this would hide some
> > possible sstate differences),
> 
> I think this actually makes it more likely to highlight differences, but
> either way, the tests I ran did highlight a raft of issues and it seems
> to be good enough to find several problems. I've sent enough fixes to
> make the new selftest pass.
> 
> >  instead I had to duplicate couple qemux86
> > overrides in linux-yocto, but this is still useful.
> > 
> > I'll drop my version after testing with sstate-diff-machines.sh that
> > both return the same results.
> 
> Sounds good.
> 
> FWIW you can run the new test with:
> 
> oe-selftest --run-tests sstatetests.SStateTests.test_sstate_sametune_samesigs
> 
> in case that isn't clear. It doesn't rely on building anything so is
> comparatively fast.

same as ssstate-diff-machines.sh --analyze :)

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2015-09-30 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 13:47 [PATCH] meta-selftest: Add qemux86copy machine Richard Purdie
2015-09-30 14:28 ` Martin Jansa
2015-09-30 15:59   ` Richard Purdie
2015-09-30 16:19     ` Martin Jansa [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=20150930161931.GD2405@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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.