linux/meta-openembedded.git/meta-python/recipes-core/images, branch styheadMirror of git.openembedded.org/meta-openembeddedhttps://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=styhead2024-09-15T23:02:38+00:00python3-fastjsonschema: Add missing rdeps for ptests2024-09-15T23:02:38+00:00Khem Rajraj.khem@gmail.com2024-09-15T19:35:42+00:00urn:sha1:0bc332a0418281a20435f7fa3c712ad1e1807337
Allocated 5G RAM to qemu when running the ptest to avoid OOMs
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-python-image-ptest: Use 2G RAM for some demanding tests2024-03-31T15:32:39+00:00Khem Rajraj.khem@gmail.com2024-03-31T15:29:45+00:00urn:sha1:a81c30edea91180f93572ddbc1471d16ee1a18f4
scrypt/fastjsonschema/pillow run into OOM on some qemu
architectures e.g. RISCV64. Raise the memory to be atleast 2G
for running these ptest images
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-python-image-ptest: add PTESTS_PROBLEMS_META_PYTHON2024-02-22T15:38:42+00:00Tim Orlingtim.orling@konsulko.com2024-02-22T04:26:31+00:00urn:sha1:1e853f5c5f8db616baac7dd17634cf4807a70e7d
In oe-core, PTESTS_PROBLEMS are also enabled, so even though
the recipe might have failures or the ptests do not run cleanly,
the BBCLASSEXTEND still works.
Enable the same behavior for meta-python.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ptest-image: Switch to using core-image-minimal2023-10-06T15:37:21+00:00Khem Rajraj.khem@gmail.com2023-10-05T05:37:37+00:00urn:sha1:d8d5444c25475f48df910888703e65edfece59db
Keeps the dependencies really to minimum.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
images: Rename ptest images to rhyme with oe-core ptest images2023-10-06T15:37:21+00:00Khem Rajraj.khem@gmail.com2023-10-05T02:08:36+00:00urn:sha1:7b5cb622b4e40ceb7b150c83ee98c40fd24ab9aa
Easy to understand for new-comers.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
images: Rename <layer>-image to <layer>-image-all2023-10-06T15:37:21+00:00Khem Rajraj.khem@gmail.com2023-10-05T02:03:05+00:00urn:sha1:0cb018059499f7531749ee1d5d1cbb02a6cf3f0a
These are test images to build all recipes in layer. Renaming them makes
them refect what they are. Moreover we can rename the ptest images to
match OE-Core naming conventions for meta-oe/meta-perl/meta-python
Signed-off-by: Khem Raj <raj.khem@gmail.com>
images: Delete layer specific base images2023-10-06T15:37:21+00:00Khem Rajraj.khem@gmail.com2023-10-05T01:52:17+00:00urn:sha1:e88b777cbecd85ff7d2916209774354a6a458101
These were essentially duplicates of core-image-minimal, however
core-image-base is a better baseline for upper layers, so switched the
consumers of these images to use core-image-base
Signed-off-by: Khem Raj <raj.khem@gmail.com>
images: Inherit from core-image-base2023-10-06T15:37:21+00:00Khem Rajraj.khem@gmail.com2023-10-05T01:33:22+00:00urn:sha1:ef9d73fced12e7b2dab485f0443cec84e55d016b
We really do not need to define base images which already exist in core
layer, reuse them here.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-python-ptest*-image: enable BBCLASSEXTEND parallel execution2023-04-04T20:39:45+00:00Tim Orlingticotimo@gmail.com2023-04-02T22:29:38+00:00urn:sha1:80e9601cc87a705f9f9d585fb2aa631e6e7e41db
Similar to "core-image-ptest: Switch to BBCLASSEXTEND parallel execution"
Refactor meta-python-ptest-image.bb for an image per ptest in the form of
meta-python-ptest-image-XXX using class extensions.
* Add meta-python-ptest-all-image.bb depends on ALL meta-python-ptest-image-XXX in meta-python
* Add meta-python-ptest-fast-image.bb depends on meta-python ptests which take less than ~30s
This allows parallel execution of the tests.
The downside to this approach is the parsing time of an image generating
this number of class extensions is slow but making it easier to execute
and collect test data should outweigh that.
A useful advantage is that the dependencies of each ptest package are
checked/tested individually.
Add to local.conf:
IMAGE_CLASSES += "testimage"
All the meta-python-ptest-image-XXX can be built with:
$ bitbake meta-python-ptest-all-image
Subsequently, all the ptest images can be run with:
$ bitbake -c testimage meta-python-ptest-all-image
You will likely want to limit the number of parallel image tests:
BB_NUMBER_THREADS = "4"
based on the number of TAP devices you have defined or the number of simultaneous
QEMU sessions your server can support.
Results can be summarized with:
$ resulttool report tmp/log/oeqa/testresults.json
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-python-image,meta-python-ptest-image: Use python3 packagegroups2020-09-10T08:24:34+00:00Khem Rajraj.khem@gmail.com2020-09-02T19:11:09+00:00urn:sha1:e43a9898fc536d1d3bc726180d5c2afd15db0b19
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>