Several of the tests in oe-selftest invoke bitbake with recipe targets, in many cases building relatively complex recipes with non-trivial dependency chains. For several tests fetching and building isn't strictly necessary and the needs of the test could be as easily met with an artificial recipe in meta-selftest which uses a local file as its source, one immediate example which prompted this report is oescripts.TestScripts.test_cleanup_workdir We should review the targets bitbake is invoked with in oe-selftest and aim to: * use artificial recipes, with a local file source, where possible * reduce reliance on recipes being present in oe-core, i.e. where practical oe-selftest should use recipes contained in meta-selftest to ensure the results are easily repeatable and independent of unrelated changes to oe-core i.e. the recent (at time of reporting) removal of GPLv2 recipes.
Moving to 2.5 and reassign this bug to Jair as he will be working on oeqa enhancements
So e.g. a simple helloworld.c + recipe should be added to oe-core?
found this one here: poky/meta-skeleton/recipes-skeleton/hello-single -> should this then moved/copied to meta-selftest/recipes-test ?
Thomas, If you don't get an answer here by early next week, try the email list, perhaps with a patch to focus the discussion. Joshua is mostly on leave for weeks or maybe 2 months so he may not reply quickly if at all. (I'm away next week as well).
Hi, just was working on this today again, so what I found: bbtests.BitbakeTests.test_event_handler is using this: bitbake('m4-native') running just this test takes orig: Ran 1 test in 75.741s replaced with hello (copied from oe-skel...) mod: Ran 1 test in 678.986s -> so it seems that building a native version will speed up already this a lot. -> trying hello-native: 29.84s Wondering if we should always just use -native recipes, then? Other locations I found, but did not replace or check them, yet: test_recipe = 'zlib' test_recipe = 'ed' bitbake('hicolor-icon-theme') testrecipe = 'lighttpd' IMO it makes sense to have a fast hello world (-native?) recipe in meta-selftest /recipes-test to use in some tests where m4-native, zlib, ed... is used! Or may there is even a faster idea? It really just depends on the specific test, what should be tested. Please, any thoughts on this? Also, I will create a patch for this and post it to the mailing list for discussion as a next step.
https://lists.openembedded.org/g/openembedded-core/message/181181?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Coeqa%2C20%2C2%2C0%2C98847654
https://lists.openembedded.org/g/openembedded-core/message/181486
https://git.yoctoproject.org/poky/commit/?id=6c8fe83bb5d1aaa11307253e8ab33c2d7f1a4a3f