[OE-core] [meta-oe][PATCH V1] cpio: add ptest

2023-02-06 Thread Yan Xin Kuan
From: Yan enable the ptest function for cpio. cpio takes 1 second maybe less, so it is fast. you will get ptest result like this: PASS: symlink SKIP: symlink-bad-length .. Signed-off-by: Yan --- .../distro/include/ptest-packagelists.inc | 1 +

[OE-core] Current high bug count owners for Yocto Project 4.2

2023-02-06 Thread Stephen Jolley
All, Below is the list as of top 32 bug owners as of the end of WW05 of who have open medium or higher bugs and enhancements against YP 4.2. There are 57 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com 33

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-02-06 Thread Stephen Jolley
All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main package for SDK

2023-02-06 Thread Khem Raj
On Mon, Feb 6, 2023 at 1:36 PM Tom Hochstein wrote: > > Oops, I don’t often send for non OE-Core and I forgot there was a separate > mailing list for that. I usually just cut and paste from here: > > > > http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_patches > > >

Re: [OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main package for SDK

2023-02-06 Thread Tom Hochstein
Oops, I don't often send for non OE-Core and I forgot there was a separate mailing list for that. I usually just cut and paste from here: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_patches Which makes it easy to overlook the mailing list requirement. There

Re: [OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main package for SDK

2023-02-06 Thread Martin Jansa
Wrong ML and why do you want to install empty package? Add nlohmann-json-dev to imx-gpu-sdk recipe instead. On Mon, Feb 6, 2023 at 10:09 PM Tom Hochstein wrote: > The header-only package cannot be included in the SDK without marking > the main package with ALLOW_EMPTY. > > Fixes rootfs problem:

[OE-core] [meta-oe][PATCH] nlohmann-json: Allow empty main package for SDK

2023-02-06 Thread Tom Hochstein
The header-only package cannot be included in the SDK without marking the main package with ALLOW_EMPTY. Fixes rootfs problem: ``` The following packages have unmet dependencies: imx-gpu-sdk : Depends: nlohmann-json but it is not installable E: Unable to correct problems, you have held broken

Re: [OE-core] SPDX 3 and OE-core CycloneDX support

2023-02-06 Thread Alex Stewart
Thanks for the context; I'll feed this back into our internal discussions. Looks like I just missed the general meeting for this month. I've joined the ML and I'll try to attend in the future. On 2/5/23 05:08, Joshua Watt wrote: On Fri, Feb 3, 2023 at 12:26 PM Alex Stewart wrote: Hey Josh,

[OE-core] [PATCH] meta/lib/oeqa/selftest/cases/wic: Add tests for kernel installation and skip-kernel-install in wic plugin.

2023-02-06 Thread Kareem Zarka
This commit adds two tests to the wic plugin to verify that the kernel is installed correctly when `skip-kernel-install` is not provided and not installed when `skip-kernel-install=true`. These tests ensure that the wic plugin is working correctly and will help catch any future issues with kernel

[OE-core] [PATCH] wic/plugins/source/bootimg-efi: Skip installing kernel-image into boot.

2023-02-06 Thread Kareem Zarka
The issue with installing the kernel-image to both rootfs and boot partition is that some systems rely on the kernel-image in rootfs and not in the boot partition. This leads to duplication of the kernel-image, which can cause unnecessary storage usage and potential compatibility issues. This

Re: [OE-core] SPDX 3 and OE-core CycloneDX support

2023-02-06 Thread Alex Stewart
On 2/5/23 08:11, Richard Purdie wrote: On Sat, 2023-02-04 at 15:47 -0600, Alex Stewart wrote: On 2/3/23 17:06, Richard Purdie wrote: On Fri, 2023-02-03 at 12:26 -0600, Alex Stewart wrote: Hey Josh, I have been roadmapping SBOM generation for NI's yocto distro and have a few open questions

Re: [OE-core][PATCH] libgit: add ptest for libgit2

2023-02-06 Thread jason.lau
Hi Alex, >//Thanks, can you add this to the the patch description? Is it possible to add >the installation rules into it as well, and then offer the patch upstream? I thinks you are right, I should try to send the patch the libgit2 upstream first. >// It's probably time we split slow ptests

Re: [OE-core][PATCH] libgit: add ptest for libgit2

2023-02-06 Thread Alexander Kanavin
Thanks, can you add this to the the patch description? Is it possible to add the installation rules into it as well, and then offer the patch upstream? It's probably time we split slow ptests into subsets and test them in parallel with two different image recipes. Can you look into that please?

Re: [OE-core][PATCH] libgit: add ptest for libgit2

2023-02-06 Thread jason.lau
HI Alex >// Did you use kvm? 21 minutes looks excessive, and I'm not sure we want to >lengthen the ptest by this much. libgit2 is not at the core of the typical >linux stack. I have tested libgit2 on a intel board with "Intel(R) Genuine Intel(R) CPU", not KVM. It took so much time because

Re: [OE-core][PATCH] libgit: add ptest for libgit2

2023-02-06 Thread Alexander Kanavin
Did you use kvm? 21 minutes looks excessive, and I'm not sure we want to lengthen the ptest by this much. libgit2 is not at the core of the typical linux stack. The added patch needs a better commit message. What does it add or change and why? Why is it inappropriate for upstream submission?

[OE-core][PATCH] libgit: add ptest for libgit2

2023-02-06 Thread jason.lau
Add ptest for libgit2. ALl test passed on a trial run and it took around 21m56s to execute so added curl-ptest to PTESTS_SLOW. Signed-off-by: Liu Haitao --- .../distro/include/ptest-packagelists.inc | 1 + ...ests-add-CLAR_FIXTURES_DIR-for-ptest.patch | 54 +++