Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3_M3.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.3_M3.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowBoard Turbot - 32bit

Re: [OE-core] [PATCH 1/3] linux/generate-cve-exclusions: fix mishandling of boundary values

On 2023/09/08 19:57, Ross Burton via lists.openembedded.org wrote: > On 6 Sep 2023, at 13:30, Ross Burton via lists.openembedded.org > wrote: On 5 Sep 2023, at 08:29, Yuta Hayama wrote: > > affected_versions in kernel_cves.json does not mean "first affected > version > to

Re: [OE-core] [langdale][kirkstone][PATCH] go-mod.bbclass: Allow network in do_compile

On Sun, Mar 12, 2023 at 10:15 AM Martin Jansa via lists.openembedded.org wrote: > On Tue, Jan 3, 2023 at 5:03 PM Lukas Funke < > lukas.funke-...@weidmueller.com> wrote: > >> Martin, >> >> first of all: thank you for testing the patches. As usual the corner >> cases are the most tricky ones. >>

Re: [OE-core] [PATCH] defaultsetup: Inherit create-spdx by default

https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/7743/steps/11/logs/stdio :( On 10/09/2023 09:25:56+0100, Richard Purdie wrote: > This has been tested in poky by default for a while and ew've hopefully > resolved > most of the gremlins. THis is the direction we're

Re: [OE-core] OE-core CVE metrics for master on Sun 10 Sep 2023 01:00:01 AM HST

On Sun, Sep 10, 2023 at 8:54 AM Marta Rybczynska wrote: > > > On Sun, 10 Sept 2023, 17:14 Khem Raj, wrote: > >> On Sun, Sep 10, 2023 at 4:18 AM Steve Sakoman wrote: >> > >> > Branch: master >> > >> > New this week: 10 CVEs >> > CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 >>

[OE-core][PATCH v6 12/12] docs: cover devtool ide

Signed-off-by: Adrian Freihofer --- documentation/sdk-manual/extensible.rst | 97 - 1 file changed, 96 insertions(+), 1 deletion(-) diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index 9e08e57a4e7..d05d4e36aa7 100644 ---

[OE-core][PATCH v6 11/12] oe-selftest devtool: ide tests

Signed-off-by: Adrian Freihofer --- meta/lib/oeqa/selftest/cases/devtool.py | 179 1 file changed, 179 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/devtool.py b/meta/lib/oeqa/selftest/cases/devtool.py index b577f6d62a1..158e016b895 100644 ---

[OE-core][PATCH v6 10/12] oe-selftest devtool: refactor runqemu pre-requisites

Split runqemu pre-requisites into a function which can be re-used by other tests as well. Signed-off-by: Adrian Freihofer --- meta/lib/oeqa/selftest/cases/devtool.py | 48 + 1 file changed, 26 insertions(+), 22 deletions(-) diff --git

[OE-core][PATCH v6 08/12] devtool: refactor deploy-target

Signed-off-by: Adrian Freihofer --- scripts/lib/devtool/__init__.py | 5 +- scripts/lib/devtool/deploy.py | 230 +--- 2 files changed, 124 insertions(+), 111 deletions(-) diff --git a/scripts/lib/devtool/__init__.py b/scripts/lib/devtool/__init__.py index

[OE-core][PATCH v6 09/12] devtool: ide make deploy-target quicker

Instead of calling devtool deploy-target which starts a bitbake server to get some variables the previous refactoring allows to generate a simple script which does no longer depend on variables from bitbake. This is much faster. --- scripts/lib/devtool/ide.py | 115

[OE-core][PATCH v6 07/12] refactor: make strip_execs callable without d

This allows to call strip_execs function from devtool without going via tinfoil and a bitbake server process. Signed-off-by: Adrian Freihofer --- meta/classes-global/staging.bbclass | 3 ++- meta/lib/oe/package.py | 7 --- 2 files changed, 6 insertions(+), 4 deletions(-) diff

[OE-core][PATCH v6 06/12] refactor: make multiprocess_launch callable without d

This is a preparation for making the strip_execs function callable from devtool without going via tinfoil and a bitbake server process. Signed-off-by: Adrian Freihofer --- meta/conf/bitbake.conf | 2 +- meta/lib/oe/utils.py | 12 +--- 2 files changed, 10 insertions(+), 4 deletions(-)

[OE-core][PATCH v6 05/12] cpp-example: workaround for pseudo breakeage

Signed-off-by: Adrian Freihofer --- meta-selftest/recipes-test/cpp/cmake-example.bb | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta-selftest/recipes-test/cpp/cmake-example.bb b/meta-selftest/recipes-test/cpp/cmake-example.bb index 96d543180b4..fbf1f266721 100644 ---

[OE-core][PATCH v6 04/12] tests: add a C++ example recipe

This simple C++ project supports compilation with cmake and with meson. It's supposed to be used with oe-selftest for the devtool ide plugin. Signed-off-by: Adrian Freihofer --- meta-selftest/recipes-test/cpp/.gitignore | 1 + .../recipes-test/cpp/cmake-example.bb | 17 ++

[OE-core][PATCH v6 03/12] devtool: new ide plugin

The new devtool ide plugin configures an IDE to work with the eSDK. With this initial implementation VSCode is the default IDE. The plugin works for recipes inheriting the cmake or the meson bbclass. Support for more programming languages and build tools may be added in the future. Using the

[OE-core][PATCH v6 02/12] cmake.bbclass: support qemu

Define the CMAKE_CROSSCOMPILING_EMULATOR variable similar to what the meson bbclass does. This allows for example to execute cross compilied unit tests on the build machine. CMAKE_CROSSCOMPILING_EMULATOR is a semi colon separated list of paramters which could directly handle the -L and the -E

[OE-core][PATCH v6 01/12] vscode: add minimal configuration

It is essential to configure VSCode indexer plugins to ignore the build folder of bitbake. Otherwise, the indexer plugins run with 100% CPU load until an OOM exception occurs. In practice, this makes VSCode more or less unusable for working with Yocto until a file like the one added by this commit

[OE-core][PATCH v6 00/12] devtool ide plugin

Changes in comparison to v5: Fix the oe-selftests AssertionError: 127 != 0 : cmake-example failed: sh: cmake-example: not found and AssertionError: 127 != 0 : mesonex failed: sh: mesonex: not found Since v1 of this patchset, there has been more than one problem that caused the

Re: [OE-core] OE-core CVE metrics for master on Sun 10 Sep 2023 01:00:01 AM HST

On Sun, 10 Sept 2023, 17:14 Khem Raj, wrote: > On Sun, Sep 10, 2023 at 4:18 AM Steve Sakoman wrote: > > > > Branch: master > > > > New this week: 10 CVEs > > CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 * > > CVE-2022-3637 (CVSS3:

Re: [OE-core] OE-core CVE metrics for master on Sun 10 Sep 2023 01:00:01 AM HST

On Sun, Sep 10, 2023 at 4:18 AM Steve Sakoman wrote: > > Branch: master > > New this week: 10 CVEs > CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 * > CVE-2022-3637 (CVSS3: 5.5 MEDIUM): bluez5 >

[OE-core] OE-core CVE metrics for mickledore on Sun 10 Sep 2023 04:00:01 AM HST

Branch: mickledore New this week: 8 CVEs CVE-2023-4733 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4733 * CVE-2023-4734 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4734 * CVE-2023-4735 (CVSS3: 7.8 HIGH): vim

[OE-core] OE-core CVE metrics for kirkstone on Sun 10 Sep 2023 03:00:01 AM HST

Branch: kirkstone New this week: 8 CVEs CVE-2023-4733 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4733 * CVE-2023-4734 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4734 * CVE-2023-4735 (CVSS3: 7.8 HIGH): vim

[OE-core] OE-core CVE metrics for dunfell on Sun 10 Sep 2023 02:00:01 AM HST

Branch: dunfell New this week: 8 CVEs CVE-2023-4733 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4733 * CVE-2023-4734 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4734 * CVE-2023-4735 (CVSS3: 7.8 HIGH): vim

[OE-core] OE-core CVE metrics for master on Sun 10 Sep 2023 01:00:01 AM HST

Branch: master New this week: 10 CVEs CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 * CVE-2022-3637 (CVSS3: 5.5 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3637 * CVE-2023-4733 (CVSS3: 7.8 HIGH): vim

[OE-core] [PATCH] defaultsetup: Inherit create-spdx by default

This has been tested in poky by default for a while and ew've hopefully resolved most of the gremlins. THis is the direction we're recommending for license/manifest requirements so set it by default for OE. Signed-off-by: Richard Purdie --- meta/conf/distro/defaultsetup.conf | 2 +- 1 file