yocto@lists.yoctoproject.org

Home Messages Hashtags Subgroups

Expanded

Between

and

[layerindex-web][PATCH 1/6] Dockerfile: add captcha dependencies Tim Orling #58824 From: Michael Halstead <mhalstead@...> The current version of django-simple-captcha requires libz and freetype development libraries. Signed-off-by: Michael Halstead <mhalstead@...> Refactor to apply. Fix typo. Fix previous mixed use of space vs tab. Signed-off-by: Tim Orling <tim.orling@...> --- Dockerfile \| 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Dockerfile b/Dockerfile index 4b2870a..a6c7ad2 100644 --- a/Dockerfile +++ b/Dockerfile @@ -31,7 +31,9 @@ RUN DEBIAN_FRONTEND=noninteractive apt-get update \ python3-mysqldb \ python3-dev \ python3-pil \ - python3-wheel \ + python3-wheel \ + libz-dev \ + libfreetype6-dev \ libjpeg-dev \ libmariadbclient-dev \ locales \ -- 2.34.1
More All Messages By This Member
[layerindex-web][PATCH 0/6] Patches from mailing list and fixes Tim Orling #58823 This series catches up on some patches that had already been sent to the mailing list, just re-iterating them here exactly as they will be merged, as well as a couple new patches. A big "Thank You!" to Robert Yang for sharing fixes that Wind River was carrying internally. One new patch, sent on Michael Halstead's behalf, represents the current production instance changes in order to meet the Python 3.8 minimum version requirement for current bitbake. One additional new patch replaces deprecated distutils usage (which was only used for LooseVersion), with pkg_resources.parse_version instead. The following changes since commit d8ab1beebeb5b49693b522d8618393620495bd74: layerindex/utils.py: ignore 'core' in BBFILES_COLLECTIONS (2022-04-28 08:15:22 -0700) are available in the Git repository at: https://git.yoctoproject.org/layerindex-web timo/mailing-list-patches http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=timo/mailing-list-patches Michael Halstead (2): Dockerfile: add captcha dependencies Dockerfile: switch to ubuntu:jammy for >python3.8 Robert Yang (3): utils.py: Use get_layer_var() to get BBFILE_COLLECTIONS admin.py: Remove has_delete_permission() utils.py: Fix for is_commit_ancestor() Tim Orling (1): global: replace deprecated distutils Dockerfile \| 23 ++++++++++++----------- layerindex/admin.py \| 17 ----------------- layerindex/recipedesc.py \| 1 - layerindex/tools/import_classic.py \| 1 - layerindex/tools/import_otherdistro.py \| 1 - layerindex/update.py \| 4 ++-- layerindex/update_layer.py \| 6 +++--- layerindex/utils.py \| 20 +++++++++++--------- layerindex/views.py \| 6 ++---- rrs/tools/upgrade_history_internal.py \| 4 ++-- 10 files changed, 32 insertions(+), 51 deletions(-) -- 2.34.1
More All Messages By This Member
[meta-zephyr][PATCH 2/2][kirkstone] CI: add tags to all jobs Peter Hoyes #58822 From: Peter Hoyes <Peter.Hoyes@...> Tag all jobs with the DEFAULT_TAG variable so each instance can control what tags the jobs have. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 03bd9c9..e88d6e5 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,6 +2,7 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 variables: CPU_REQUEST: "" + DEFAULT_TAG: "" # These are needed as the k8s executor doesn't respect the container # entrypoint by default FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 @@ -13,6 +14,8 @@ stages: =20 # Common job fragment to get a worker ready .setup: + tags: + - $DEFAULT_TAG stage: build interruptible: true variables: @@ -65,7 +68,8 @@ machine-coverage: script: - ./ci/check-machine-coverage coverage: '/Coverage: \d+/' - + tags: + - $DEFAULT_TAG =20 # # Build stage, the actual build jobs --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 1/2][kirkstone] CI: Add variables needed for k8s runners Peter Hoyes #58821 From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this needs to be tuned per-deployment. CPU_REQUEST has no value outside of Arm Corp. Gitlab CI allows for variables to be overridden by default. So, we can give it a default value of NULL/empty and have everything work internally and externally by default. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 8d22654..03bd9c9 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,5 +1,12 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 +variables: + CPU_REQUEST: "" + # These are needed as the k8s executor doesn't respect the container + # entrypoint by default + FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 + FF_KUBERNETES_HONOR_ENTRYPOINT: 1 + stages: - prep - build @@ -24,6 +31,8 @@ stages: # Generalised fragment to do a Kas build .build: extends: .setup + variables: + KUBERNETES_CPU_REQUEST: $CPU_REQUEST script: - KASFILES=3D$(./ci/jobs-to-kas "$CI_JOB_NAME") - kas shell --update --force-checkout $KASFILES -c 'cat conf/*.conf' --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 5/5][langdale] zephyr-core/zephyr-kernel: Inhibit packaging steps with the Zephyr SDK Peter Hoyes #58820 From: Peter Hoyes <Peter.Hoyes@...> The packaging step includes post-processing of elf files using objcopy and strip from the Yocto toolchain. When using the Zephyr SDK, the Yocto toolchain is explicitly not built so it is not possible to run these steps. Therefore, inhibit them in zephyr-toolchain-zephyr.inc Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .../recipes-kernel/zephyr-kernel/zephyr-toolchain-zephyr.inc \| 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolcha= in-zephyr.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-tool= chain-zephyr.inc index 9987e3c..a193314 100644 --- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolchain-zeph= yr.inc +++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolchain-zeph= yr.inc @@ -13,3 +13,7 @@ deltask generate_toolchain_file # Provide a suitable location to store the toolchain capabilites cache ZEPHYR_USER_CACHE_DIR =3D "${B}/.cache" EXTRA_OECMAKE:append =3D " -DUSER_CACHE_DIR=3D${ZEPHYR_USER_CACHE_DIR}" + +# Inhibit packaging steps that require the Yocto toolchain +INHIBIT_PACKAGE_DEBUG_SPLIT =3D "1" +INHIBIT_PACKAGE_STRIP =3D "1" --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 4/5][langdale] zephyr-core/zephyr-kernel: Use layer-relative require for version file Peter Hoyes #58819 From: Peter Hoyes <Peter.Hoyes@...> The inclusion of the Zephyr version-specific .inc file is currently using a local include. Change to be layer-relative to support including files in other layers. Change to use 'require' instead of 'include' so that an earlier error is printed if the file does not exist. Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .../recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc \| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-= src.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src= .inc index f28d1d4..3383894 100644 --- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc +++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc @@ -13,4 +13,4 @@ S =3D "${WORKDIR}/git" =20 # Default to a stable version PREFERRED_VERSION_zephyr-kernel ??=3D "3.1.0" -include zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc +require recipes-kernel/zephyr-kernel/zephyr-kernel-src-${PREFERRED_VERSI= ON_zephyr-kernel}.inc --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 3/5][langdale] CI: Set default branch to langdale Peter Hoyes #58818 From: Peter Hoyes <Peter.Hoyes@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- ci/base.yml \| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci/base.yml b/ci/base.yml index 70adac1..7b2203e 100644 --- a/ci/base.yml +++ b/ci/base.yml @@ -7,7 +7,7 @@ distro: zephyr =20 defaults: repos: - refspec: master + refspec: langdale =20 repos: meta-zephyr: --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 2/5][langdale] CI: add tags to all jobs Peter Hoyes #58817 From: Peter Hoyes <Peter.Hoyes@...> Tag all jobs with the DEFAULT_TAG variable so each instance can control what tags the jobs have. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 616626a..7ec0bd0 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,6 +2,7 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 variables: CPU_REQUEST: "" + DEFAULT_TAG: "" # These are needed as the k8s executor doesn't respect the container # entrypoint by default FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 @@ -13,6 +14,8 @@ stages: =20 # Common job fragment to get a worker ready .setup: + tags: + - $DEFAULT_TAG stage: build interruptible: true variables: @@ -65,7 +68,8 @@ machine-coverage: script: - ./ci/check-machine-coverage coverage: '/Coverage: \d+/' - + tags: + - $DEFAULT_TAG =20 # # Build stage, the actual build jobs --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 1/5][langdale] CI: Add variables needed for k8s runners Peter Hoyes #58816 From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this needs to be tuned per-deployment. CPU_REQUEST has no value outside of Arm Corp. Gitlab CI allows for variables to be overridden by default. So, we can give it a default value of NULL/empty and have everything work internally and externally by default. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 3f0e319..616626a 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,5 +1,12 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 +variables: + CPU_REQUEST: "" + # These are needed as the k8s executor doesn't respect the container + # entrypoint by default + FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 + FF_KUBERNETES_HONOR_ENTRYPOINT: 1 + stages: - prep - build @@ -24,6 +31,8 @@ stages: # Generalised fragment to do a Kas build .build: extends: .setup + variables: + KUBERNETES_CPU_REQUEST: $CPU_REQUEST script: - KASFILES=3D$(./ci/jobs-to-kas "$CI_JOB_NAME") - kas shell --update --force-checkout $KASFILES -c 'cat conf/*.conf' --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 5/5] zephyr-core: Add addpylib declaration Peter Hoyes #58815 From: Peter Hoyes <Peter.Hoyes@...> OE-core 4901c9d471cab99d52876842980222ce271b66e4 "base: Switch to use addpylib directive and BB_GLOBAL_PYMODULES" means that ${LAYERDIR}/lib is no longer searched by default when loading test controllers. meta-zephyr-core defines some custom test controllers for testing FVPs, so add an addpylib directive to meta-zephyr-core/conf/layer.conf to fix testimage. Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- meta-zephyr-core/conf/layer.conf \| 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-zephyr-core/conf/layer.conf b/meta-zephyr-core/conf/lay= er.conf index 3d1e57b..2b1c821 100644 --- a/meta-zephyr-core/conf/layer.conf +++ b/meta-zephyr-core/conf/layer.conf @@ -20,3 +20,5 @@ LAYERSERIES_COMPAT_zephyrcore =3D "dunfell gatesgarth h= ardknott honister kirkstone X86_TUNE_DIR =3D "${@bb.utils.contains_any('LAYERSERIES_CORENAMES', 'hon= ister kirkstone langdale', 'include/x86', 'include', d)}" =20 PYTHON3_NATIVE_SITEPACKAGES_DIR =3D "${libdir_native}/${PYTHON3_DIR}/sit= e-packages" + +addpylib ${LAYERDIR}/lib oeqa --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 4/5] zephyr-core/zephyr-kernel: Inhibit packaging steps with the Zephyr SDK Peter Hoyes #58814 From: Peter Hoyes <Peter.Hoyes@...> The packaging step includes post-processing of elf files using objcopy and strip from the Yocto toolchain. When using the Zephyr SDK, the Yocto toolchain is explicitly not built so it is not possible to run these steps. Therefore, inhibit them in zephyr-toolchain-zephyr.inc Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .../recipes-kernel/zephyr-kernel/zephyr-toolchain-zephyr.inc \| 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolcha= in-zephyr.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-tool= chain-zephyr.inc index 9987e3c..a193314 100644 --- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolchain-zeph= yr.inc +++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-toolchain-zeph= yr.inc @@ -13,3 +13,7 @@ deltask generate_toolchain_file # Provide a suitable location to store the toolchain capabilites cache ZEPHYR_USER_CACHE_DIR =3D "${B}/.cache" EXTRA_OECMAKE:append =3D " -DUSER_CACHE_DIR=3D${ZEPHYR_USER_CACHE_DIR}" + +# Inhibit packaging steps that require the Yocto toolchain +INHIBIT_PACKAGE_DEBUG_SPLIT =3D "1" +INHIBIT_PACKAGE_STRIP =3D "1" --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 3/5] zephyr-core/zephyr-kernel: Use layer-relative require for version file Peter Hoyes #58813 From: Peter Hoyes <Peter.Hoyes@...> The inclusion of the Zephyr version-specific .inc file is currently using a local include. Change to be layer-relative to support including files in other layers. Change to use 'require' instead of 'include' so that an earlier error is printed if the file does not exist. Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .../recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc \| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-= src.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src= .inc index aa299e0..a19d074 100644 --- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc +++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc @@ -13,4 +13,4 @@ S =3D "${WORKDIR}/git" =20 # Default to a stable version PREFERRED_VERSION_zephyr-kernel ??=3D "3.2.0" -include zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc +require recipes-kernel/zephyr-kernel/zephyr-kernel-src-${PREFERRED_VERSI= ON_zephyr-kernel}.inc --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 2/5] CI: add tags to all jobs Peter Hoyes #58812 From: Peter Hoyes <Peter.Hoyes@...> Tag all jobs with the DEFAULT_TAG variable so each instance can control what tags the jobs have. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 616626a..7ec0bd0 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -2,6 +2,7 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 variables: CPU_REQUEST: "" + DEFAULT_TAG: "" # These are needed as the k8s executor doesn't respect the container # entrypoint by default FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 @@ -13,6 +14,8 @@ stages: =20 # Common job fragment to get a worker ready .setup: + tags: + - $DEFAULT_TAG stage: build interruptible: true variables: @@ -65,7 +68,8 @@ machine-coverage: script: - ./ci/check-machine-coverage coverage: '/Coverage: \d+/' - + tags: + - $DEFAULT_TAG =20 # # Build stage, the actual build jobs --=20 2.25.1
More All Messages By This Member
[meta-zephyr][PATCH 1/5] CI: Add variables needed for k8s runners Peter Hoyes #58811 From: Peter Hoyes <Peter.Hoyes@...> The Kas container needs to use the entrypoint as that is where the user changes from root to a normal user. Also set the KUBERNETES_CPU_REQUEST to the variable CPU_REQUEST as this needs to be tuned per-deployment. CPU_REQUEST has no value outside of Arm Corp. Gitlab CI allows for variables to be overridden by default. So, we can give it a default value of NULL/empty and have everything work internally and externally by default. Signed-off-by: Ross Burton <ross.burton@...> Signed-off-by: Jon Mason <jon.mason@...> Signed-off-by: Peter Hoyes <Peter.Hoyes@...> --- .gitlab-ci.yml \| 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 3f0e319..616626a 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,5 +1,12 @@ image: ghcr.io/siemens/kas/kas:latest-release =20 +variables: + CPU_REQUEST: "" + # These are needed as the k8s executor doesn't respect the container + # entrypoint by default + FF_USE_LEGACY_KUBERNETES_EXECUTION_STRATEGY: 0 + FF_KUBERNETES_HONOR_ENTRYPOINT: 1 + stages: - prep - build @@ -24,6 +31,8 @@ stages: # Generalised fragment to do a Kas build .build: extends: .setup + variables: + KUBERNETES_CPU_REQUEST: $CPU_REQUEST script: - KASFILES=3D$(./ci/jobs-to-kas "$CI_JOB_NAME") - kas shell --update --force-checkout $KASFILES -c 'cat conf/*.conf' --=20 2.25.1
More All Messages By This Member
Re: Ownership issue during do_image Frederic Martinsons <frederic.martinsons@...> #58810 Hello, some news about this issue. Tim pointed me to the docker and the reason why crops container have some UID:GID manipulation: see there. I used an ubuntu 20.04 VM to setup a build without docker and I fall into the exact same problem. But finally, I found that a workaround by creating and using another working directory inside my image creation command (though I clearly don't know why this work and the former way don't, despite it worked with yocto warrior) Before that, I have a working directory that was created in the bbclass : `SQSHDIR = "${S}/sqshimg/${MACHINE}" do_image_tapos_sqshimg[dirs] += "${SQSHDIR}" do_image_tapos_sqshimg[cleandirs] += "${SQSHDIR}" do_image_tapos_sqshimg[recrdeptask] += "do_deploy" IMAGE_CMD_tapos-sqshimg() { install -d ${SQSHDIR}` I simply replaced the creation command by: `IMAGE_CMD_tapos-sqshimg() { SQSHDIR_WORKDIR=$(mktemp -d)` and voilà !
More All Messages By This Member
Minutes: Yocto Project Weekly Triage Meeting 12/15/2022 sakib.sajal@... #58809 Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Richard Purdie, Steve Sakoman, Stephen Jolley, Randy Macleod, Joshua Watt, Ross Burton, Alexandre Belloni, Tim Orling, Michael Opdenacker, Bruce Ashfield, Pavel Zhukov, Ryan Eatmon ARs: email David Reyna and Michael Halstead regarding assigned mediums with milestones. Notes: Medium+ 4.2 Unassigned Enhancements/Bugs: 70 (Last week 70) Medium+ 4.99 Unassigned Enhancements/Bugs: 43 (Last week 44) AB Bugs: 59 (Last week 58)
More All Messages By This Member
Minutes: Yocto Project Weekly Triage Meeting 12/15/2022 sakib.sajal@... #58808 Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Richard Purdie, Steve Sakoman, Stephen Jolley, Randy Macleod, Joshua Watt, Ross Burton, Alexandre Belloni, Tim Orling, Michael Opdenacker, Bruce Ashfield, Pavel Zhukov, Ryan Eatmon ARs: email David Reyna and Michael Halstead regarding assigned mediums with milestones. Notes: Medium+ 4.2 Unassigned Enhancements/Bugs: 70 (Last week 70) Medium+ 4.99 Unassigned Enhancements/Bugs: 43 (Last week 44) AB Bugs: 59 (Last week 58)
More All Messages By This Member
[PATCH yocto-autobuilder2] config.py: add knowledge of meta-clang Ross Burton #58807 We'd like to start building meta-clang as part of the autobuilder matrix, so add knowledge of meta-clang to builtbot. Signed-off-by: Ross Burton <ross.burton@...> --- config.py \| 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/config.py b/config.py index 3c67351..b6609a7 100644 --- a/config.py +++ b/config.py @@ -20,6 +20,7 @@ buildertorepos =3D { "meta-arm": ["poky", "meta-arm"], "meta-agl-core": ["poky", "meta-agl"], "meta-aws": ["poky", "meta-aws", "meta-openembedded"], + "meta-clang": ["poky", "meta-clang"], "qemuarm-oecore": ["oecore", "bitbake"], "checkuri": ["poky"], "check-layer": ["poky", "meta-mingw", "meta-gplv2"], @@ -54,7 +55,8 @@ repos =3D { "meta-gplv2": ["ssh://git@.../meta-gplv2", "master= "], "meta-openembedded": ["git://git.openembedded.org/meta-openembedded"= , "master"], "meta-virtualization": ["ssh://git@.../meta-virtua= lization", "master"], - "yocto-docs": ["ssh://git@.../yocto-docs", "master= "] + "yocto-docs": ["ssh://git@.../yocto-docs", "master= "], + "meta-clang": ["https://github.com/kraj/meta-clang.git", "master"], } =20 trigger_builders_wait_shared =3D [ --=20 2.34.1
More All Messages By This Member
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.6.rc1) Jing Hui Tham #58806 Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.6.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. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4. TGL NUC 11 5. Edgerouter 6. Beaglebone ETA for completion next Tuesday, December 20. Best regards, Jing Hui toggle quoted message Show quoted text -----Original Message----- From: qa-build-notification@... <qa-build- notification@...> On Behalf Of Pokybuild User Sent: Wednesday, 14 December, 2022 7:12 AM To: yocto@... Cc: qa-build-notification@... Subject: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.0.6.rc1) A build flagged for QA (yocto-4.0.6.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.0.6.rc1 Build hash information: bitbake: 7e268c107bb0240d583d2c34e24a71e373382509 meta-agl: 5e3a4f5fa0e9adeae54a2a47d1daa80c64c7363a meta-arm: 67578fcfcd8ee8efcaef67ed7db1dfd55105872e meta-aws: 09db18354cfe358e38913754d24b71685f2a3ed3 meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a meta-intel: f529e0594a784546926e89ce8e78385e00d0b0a9 meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 meta-openembedded: 50d4a8d2a983a68383ef1ffec2c8e21adf0c1a79 meta-virtualization: a0d0f4ff48f874703d9e24a5d969d816b524c8b8 oecore: 45a8b4101b14453aa3020d3f2b8a76b4dc0ae3f2 poky: c4e08719a782fd4119eaf643907b80cebf57f88f This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
More All Messages By This Member
Re: QA notification for completed autobuilder build (yocto-4.2_M1.rc1) Jing Hui Tham #58805 Hi All, QA for yocto-4.2_M1.rc1 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. No new issue found. Thanks, Jing Hui toggle quoted message Show quoted text -----Original Message----- From: yocto@... <yocto@...> On Behalf Of Pokybuild User Sent: Friday, 9 December, 2022 3:39 AM To: yocto@... Cc: qa-build-notification@... Subject: [yocto] QA notification for completed autobuilder build (yocto- 4.2_M1.rc1) A build flagged for QA (yocto-4.2_M1.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.2_M1.rc1 Build hash information: bitbake: 6709aedccbb2e7ddbb1b2e7e4893481a7b536436 meta-agl: e2c31ebda224bf6813ff861df9a51e8fc46944e5 meta-arm: 02b430d045b50d5e5cab9a52b786d1134ba17c19 meta-aws: da36bf8bc3f5a1cbb9396e8d28559c422cd96412 meta-intel: de59d48ad2ce88ebe331a8355e742fce7c3b428c meta-mingw: 4a066511a944ec946efa7a4571029c992cf0ae00 meta-openembedded: 8c58f419c299fe3764482ebe4f366e25533ea23f meta-virtualization: cb5dfda6f6d862a575f029ee8ded0bc3db6bc766 oecore: 96ff9baa8ead57504f40f362ed3a4aaa776d1b58 poky: 4d19594b8bdacde6d809d3f2a25cff7c5a42295e This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
More All Messages By This Member

1341 - 1360 of 60111

Home Hashtags Subgroups Terms