[OE-core] [meta-oe][PATCH v2 4/4] testimage: Moved write_image_test_data to testimage bbclass.

richard.purdie at linuxfoundation.org richard.purdie at linuxfoundation.org
Wed Oct 3 16:13:42 UTC 2018


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



More information about the Openembedded-core mailing list