Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Paulo Neves <ptsneves@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v2 4/4] testimage: Moved write_image_test_data to testimage bbclass.
Date: Wed, 03 Oct 2018 17:13:42 +0100	[thread overview]
Message-ID: <d30408c2c0f343fd1bbaaef8006820bfb6b7c686.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJO0J4gkXiv++K+aTHJF2O_Hq8MFDKPCpy+vWz6Ym1ZrLY00Bw@mail.gmail.com>

On Tue, 2018-10-02 at 10:19 +0200, Paulo Neves wrote:
> Would assure you if it generated the test data on image creation
> *and* on test task?

No, it wouldn't.

> If not please describe more or less how I could collect which
> variables write_image_test_data depends upon. Just a high level
> description would do.

I thought testdata contained a filtered list of variable keys but it
doesn't, its a complete dump of the data store with some variables
"broken" by the removal of TOPDIR. My proposal was based on my thought
that it was filtered so that won't work.

> I have really been in a good spirit to get this topic merged but I do
> not see a clear guidance for me to fix what was clearly broken.

It is not clearly broken. Its broken in the way you're trying to use it
and expect it to work.

The usage of testdata is alongside the image that is built, they're a
paired item. The image and the testdata go together. Either both are
rebuilt together or they're not.

Personally, I think testdata should get filtered to the list of
variables the testing code really needs, not just a dump of every
value.

I thought the tests had markup to indicate which variables they needed
for that reason, so a list of variables could be constructed. If we did
that, this would allow us to rewrite the file (and rebuild the rootfs)
when the values changed.

> Actually the current code put there by intel should should be
> reverted in my opinion, as it broke all the controllers besides
> simpleremote and qemu.

I would very much like to fix that and your other patches in this area
are good. Unfortunately you change a lot in the patches in one go
though and it was too difficult to review like that.

If you were able to split those into smaller pieces that make one
logical change/fix in each, that would help in getting those ones in at
least.

Improving the test coverage so that things don't get broken again would
also be very helpful.

Cheers,

Richard


      reply	other threads:[~2018-10-03 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 17:49 [meta-oe][PATCH v2 1/4] testimage: Refactoring and fixing Paulo Neves
2018-08-30 17:49 ` [meta-oe][PATCH v2 2/4] testimage: target.start exceptions not masked Paulo Neves
2018-08-30 17:49 ` [meta-oe][PATCH v2 3/4] masterimage: Check for rootfs path instead of file Paulo Neves
2018-08-30 17:49 ` [meta-oe][PATCH v2 4/4] testimage: Moved write_image_test_data to testimage bbclass Paulo Neves
2018-09-04 10:30   ` Richard Purdie
2018-10-02  8:19     ` Paulo Neves
2018-10-03 16:13       ` 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=d30408c2c0f343fd1bbaaef8006820bfb6b7c686.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ptsneves@gmail.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