== Series Details ==
Series: linux-yocto_5.2.bb: Fix build races in kernel-selftests
Revision: 1
URL : https://patchwork.openembedded.org/series/19553/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests
Signed-off-by: Khem Raj
Cc: Bruce Ashfield
---
...x-test_verifier-test_maps-make-depen.patch | 58 +
...ructure-test_-progs-maps-verifier-te.patch | 86 +++
meta/recipes-kernel/linux/linux-yocto_5.2.bb | 3 +
3 files changed, 147 insertions(+)
create mode 100644
Signed-off-by: Zang Ruochen
---
meta/recipes-extended/libsolv/{libsolv_0.7.5.bb => libsolv_0.7.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/libsolv/{libsolv_0.7.5.bb => libsolv_0.7.6.bb}
(93%)
diff --git
On Wed, Aug 28, 2019 at 10:14 PM wrote:
>
> From: Bruce Ashfield
>
> The upstream kernel can now handle python3 for the perf scripts, coupled
> with the impending EOL of python2, we switch the dependencies in perf
> (scripting) to python3.
>
> Outside of dependency changes, we also pass the
On 8/28/19 5:41 PM, Richard Purdie wrote:
On Wed, 2019-08-28 at 15:24 -0500, Jason Wessel wrote:
On 8/27/19 7:15 PM, richard.pur...@linuxfoundation.org wrote:
On Tue, 2019-08-27 at 19:03 -0500, Jason Wessel wrote:
On 8/27/19 5:58 PM, Richard Purdie wrote:
Hi Jason,
Somehow this change is
From: Bruce Ashfield
The upstream kernel can now handle python3 for the perf scripts, coupled
with the impending EOL of python2, we switch the dependencies in perf
(scripting) to python3.
Outside of dependency changes, we also pass the following two variables
to the perf build: PYTHON=python3
From: Limeng
commit 3613b2780a6b5d5d70ea6802be5060a8214cbdb5 from
git://github.com/renesas-rcar/meta-renesas
Signed-off-by: Meng Li
---
meta/conf/machine/include/tune-cortexa57.inc | 18 ++
1 file changed, 18 insertions(+)
create mode 100644
From: Limeng
Recently, I am working on renesas-rcar platform based on yocto-2.7,
and I found there are no arm-cortexa57 and arm-cortexa57-cortexa53
tunes for some Renesas SoC.
Therefore, add 2 kinds of ARM-Cortex-Tune.
Detail patches as below:
From: Limeng
commit 3613b2780a6b5d5d70ea6802be5060a8214cbdb5 from
git://github.com/renesas-rcar/meta-renesas
There are 2 types cores in renesas rcar SoC H3/M3, so add a tune
for ARM Cortex-A53-Cortex-A57.
Signed-off-by: Meng Li
---
.../include/tune-cortexa57-cortexa53.inc | 18
On Wed, Aug 28, 2019 at 8:32 PM Bruce Ashfield wrote:
>
> On Wed, Aug 28, 2019 at 3:28 PM wrote:
> >
> > From: Bruce Ashfield
> >
> > In the 5.3+ perf builds, there are multiple unistd.h files that need
> > to be kept in sync. So not only do we update one, we update both to
> > ensure that
On Wed, Aug 28, 2019 at 8:27 PM Bruce Ashfield wrote:
>
> On Wed, Aug 28, 2019 at 8:24 PM Bruce Ashfield
> wrote:
> >
> > On Wed, Aug 28, 2019 at 8:18 PM Mittal, Anuj wrote:
> > >
> > > On Wed, 2019-08-28 at 20:13 -0400, Bruce Ashfield wrote:
> > > > > On Wed, Aug 28, 2019 at 8:01 PM Mittal,
On Wed, Aug 28, 2019 at 3:28 PM wrote:
>
> From: Bruce Ashfield
>
> In the 5.3+ perf builds, there are multiple unistd.h files that need
> to be kept in sync. So not only do we update one, we update both to
> ensure that libc-headers and the perf build are in sync.
>
> perf checks some key files
On Wed, Aug 28, 2019 at 8:24 PM Bruce Ashfield wrote:
>
> On Wed, Aug 28, 2019 at 8:18 PM Mittal, Anuj wrote:
> >
> > On Wed, 2019-08-28 at 20:13 -0400, Bruce Ashfield wrote:
> > > > On Wed, Aug 28, 2019 at 8:01 PM Mittal, Anuj
> > > wrote:
> > > This is causing failure for 5.0 kernels probably
On Wed, Aug 28, 2019 at 8:18 PM Mittal, Anuj wrote:
>
> On Wed, 2019-08-28 at 20:13 -0400, Bruce Ashfield wrote:
> > > On Wed, Aug 28, 2019 at 8:01 PM Mittal, Anuj
> > wrote:
> > This is causing failure for 5.0 kernels probably because the attr.py
> > > python -> python3 changes are not there
On Wed, 2019-08-28 at 20:13 -0400, Bruce Ashfield wrote:
> > On Wed, Aug 28, 2019 at 8:01 PM Mittal, Anuj
> wrote:
> This is causing failure for 5.0 kernels probably because the attr.py
> > python -> python3 changes are not there ...
> >
> > ERROR: perf-1.0-r9 do_package_qa: QA Issue:
On Wed, Aug 28, 2019 at 8:01 PM Mittal, Anuj wrote:
>
> This is causing failure for 5.0 kernels probably because the attr.py
> python -> python3 changes are not there ...
>
> ERROR: perf-1.0-r9 do_package_qa: QA Issue: /usr/libexec/perf-
> core/tests/attr.py contained in package perf-tests
This is causing failure for 5.0 kernels probably because the attr.py
python -> python3 changes are not there ...
ERROR: perf-1.0-r9 do_package_qa: QA Issue: /usr/libexec/perf-
core/tests/attr.py contained in package perf-tests requires
/usr/bin/python, but no providers found in
On Wed, 2019-08-28 at 15:24 -0500, Jason Wessel wrote:
> On 8/27/19 7:15 PM, richard.pur...@linuxfoundation.org wrote:
> > On Tue, 2019-08-27 at 19:03 -0500, Jason Wessel wrote:
> > > On 8/27/19 5:58 PM, Richard Purdie wrote:
> > > > Hi Jason,
> > > > Somehow this change is responsible for this
On Wed, 2019-08-28 at 15:24 -0500, Jason Wessel wrote:
> On 8/27/19 7:15 PM, richard.pur...@linuxfoundation.org wrote:
> > On Tue, 2019-08-27 at 19:03 -0500, Jason Wessel wrote:
> > > On 8/27/19 5:58 PM, Richard Purdie wrote:
> > > > Hi Jason,
> > > > Somehow this change is responsible for this
On Wed, Aug 28, 2019 at 5:58 PM Adrian Bunk wrote:
>
> On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote:
> >...
> > There's zero risk to these, and no reason to sit on them.
>
> What range of LTS kernels is covered by the "zero risk"?
It has nothing to do with LTS kernels.
Cheers,
== Series Details ==
Series: bitbake: cooker: Ensure bbappends are found in stable order
Revision: 1
URL : https://patchwork.openembedded.org/series/19547/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote:
>...
> There's zero risk to these, and no reason to sit on them.
What range of LTS kernels is covered by the "zero risk"?
> Bruce
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the
Thanks to wildcards in bbappend filenames, it's possible to have
multiple bbappends that apply to the same recipe in the same directory.
In order to get sstate hits between different workspaces, we want to
apply those bbappend files in a consistent order. Since readdir()
returns files in a
On Wed, 28 Aug 2019 at 22:12, wrote:
> > Yocto 3.0 ships and supports Python 2.7, so there is no urgent need
> > for
> > last-minute Python 2 -> 3 changes.
>
> Removal of 2.X dependencies where we can was an objective of 3.0 and
> 2.X is EOL and will expire in the lifetime of 3.0. I'd say this
Signed-off-by: Alexander Kanavin
---
...thon3-everywhere-to-run-python-scrip.patch | 161 ++
meta/recipes-extended/ltp/ltp_20190517.bb | 3 +-
2 files changed, 163 insertions(+), 1 deletion(-)
create mode 100644
On 8/27/19 7:15 PM, richard.pur...@linuxfoundation.org wrote:
On Tue, 2019-08-27 at 19:03 -0500, Jason Wessel wrote:
On 8/27/19 5:58 PM, Richard Purdie wrote:
Hi Jason,
Somehow this change is responsible for this build failure:
On Wed, 2019-08-28 at 23:05 +0300, Adrian Bunk wrote:
> On Wed, Aug 28, 2019 at 03:28:38PM -0400, bruce.ashfi...@gmail.com
> wrote:
> > From: Bruce Ashfield
> >
> > Witht the approaching EOL of python2, the kernel packages need to
> > be updated to depend on python3.
> > ...
>
> Yocto 3.0 ships
On Wed, Aug 28, 2019 at 4:05 PM Adrian Bunk wrote:
>
> On Wed, Aug 28, 2019 at 03:28:38PM -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Witht the approaching EOL of python2, the kernel packages need to
> > be updated to depend on python3.
> >...
>
> Yocto 3.0 ships and
From: Bruce Ashfield
Introducing the 5.2 linux-yocto reference kernels. 5.0 is EOL and will
be removed, leaving 4.19 (LTS) and 5.2 as the reference kernels.
This has been build/boot tested on all qemu architectures for
core-image-kernel-dev, and graphics tesed via core-image-sato. No
blocking
On Wed, Aug 28, 2019 at 4:00 PM Adrian Bunk wrote:
>
> On Wed, Aug 28, 2019 at 03:28:36PM -0400, bruce.ashfi...@gmail.com wrote:
> >...
> > --- /dev/null
> > +++ b/meta/recipes-kernel/linux/files/0001-foo.patch
> > @@ -0,0 +1,25 @@
> > +From 9ddc5e377434e28f1f3c74c9be011b0c9dfb1de4 Mon Sep 17
On Wed, Aug 28, 2019 at 03:28:38PM -0400, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Witht the approaching EOL of python2, the kernel packages need to
> be updated to depend on python3.
>...
Yocto 3.0 ships and supports Python 2.7, so there is no urgent need for
last-minute
On Wed, Aug 28, 2019 at 03:28:36PM -0400, bruce.ashfi...@gmail.com wrote:
>...
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/files/0001-foo.patch
> @@ -0,0 +1,25 @@
> +From 9ddc5e377434e28f1f3c74c9be011b0c9dfb1de4 Mon Sep 17 00:00:00 2001
> +From: Bruce Ashfield
> +Date: Fri, 1 Mar 2019
== Series Details ==
Series: kernel/kernel-yocto: consolidated M3 feature pull request
Revision: 1
URL : https://patchwork.openembedded.org/series/19543/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
From: Bruce Ashfield
We need to include a few more small files for on target module
builds for 5.3+ kernels.
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/kernel-devsrc.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
From: Bruce Ashfield
Signed-off-by: Bruce Ashfield
---
meta/conf/machine/include/x86-base.inc | 2 +-
meta/conf/machine/qemuarmv5.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/conf/machine/include/x86-base.inc
b/meta/conf/machine/include/x86-base.inc
From: Bruce Ashfield
In the 5.3+ perf builds, there are multiple unistd.h files that need
to be kept in sync. So not only do we update one, we update both to
ensure that libc-headers and the perf build are in sync.
perf checks some key files itself to be sure they are in sync, and
bits.h can be
From: Bruce Ashfield
The upstream kernel can now handle python3 for the perf scripts, coupled
with the impending EOL of python2, we switch the dependencies in perf
(scripting) to python3.
Outside of dependency changes, we also pass the following two variables
to the perf build: PYTHON=python3
From: Bruce Ashfield
Backporting the following upstream commit to fix the build against
kernel 5.2+ headers:
[
Subject: [PATCH] tools: Fix build after y2038 changes in glibc
The 32-bit SIOCGSTAMP has been deprecated. Use the deprecated name
to fix the build.
]
Upstream-Status:
From: Bruce Ashfield
Introducing the 5.2 linux-yocto reference kernels. 5.0 is EOL and will
be removed, leaving 4.19 (LTS) and 5.2 as the reference kernels.
This has been build/boot tested on all qemu architectures for
core-image-kernel-dev, and graphics tesed via core-image-sato. No
blockin
From: Bruce Ashfield
Witht the approaching EOL of python2, the kernel packages need to
be updated to depend on python3.
The core kernel scripts are now python3 safe, making the RDEPENDS
change relatively simple.
but
There are some scripts that are captured in the devsrc files that
are not
From: Bruce Ashfield
We drop the patch
0001-arm64-sve-uapi-asm-ptrace.h-should-not-depend-on-uap.patch
since it was a backport and is already part of the 5.2 headers
Signed-off-by: Bruce Ashfield
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
From: Bruce Ashfield
Hi all,
Sorry for this being slightly after the M3 feature cutoff, I ended up having
to churn through a lot of extra builds keeping up with master, dealing with
header issues, and working through the python3 changes at the same time.
With this series, we get an update of
It's become more commone for files to be named "readme" or "Readme" on github
servers
in recent time. So adjust the scanning to allow any mix of case.
Signed-off-by: Mark Hatle
---
scripts/lib/checklayer/cases/common.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, Aug 28, 2019 at 3:05 AM Christophe PRIOUZEAU
wrote:
>
> Using the generic BSD-2-CLAUSE license as specified on
> https://opensource.org/licenses/BSD-2-Clause
Fixing these kind of issues has been discussed before. I think the
consensus was that a wider ranging cleanup is needed. The
On 8/28/19 11:09 AM, Richard Purdie wrote:
On Tue, 2019-08-27 at 07:45 -0500, Joshua Watt wrote:
gettext is required to generate the glibc locales in do_compile. If not
present, glibc will skip the generation which isn't reproducible.
Signed-off-by: Joshua Watt
---
On Tue, 2019-08-27 at 07:45 -0500, Joshua Watt wrote:
> gettext is required to generate the glibc locales in do_compile. If not
> present, glibc will skip the generation which isn't reproducible.
>
> Signed-off-by: Joshua Watt
> ---
> meta/recipes-core/glibc/glibc.inc | 2 +-
> 1 file changed,
On Wed, 2019-08-28 at 09:29 +0800, Kang Kai wrote:
> On 2019/8/28 上午7:29, richard.pur...@linuxfoundation.org wrote:
> > On Tue, 2019-08-27 at 17:43 +0800, Kang Kai wrote:
> > > Hi Richard,
> > >
> > > This patch could fix the test_image failure with systemd. Would
> > > like
> > > to
> > > try
It was found to crash the X server on startup under qemu.
Signed-off-by: Alexander Kanavin
---
meta/conf/machine/qemux86-64.conf | 5 -
meta/recipes-graphics/mesa/mesa.inc | 3 +++
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/meta/conf/machine/qemux86-64.conf
This is the qemu default since qemu 2.2, is generally supported better,
and is recommended by upstream. It also has already been in use for arm/risc
and ovmf.
Additional information:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466
This is perhaps not the most elegant patch but it be dropped
once rpm is updated to the soon-to-be-released version 4.15
where upstream has removed mono dependency resolution altogether.
Signed-off-by: Alexander Kanavin
---
...es-requires-do-not-use-monodis-from-.patch | 58 +++
There was a discussion about what amount of RAM is appropriate for a
default; the outcome was that for now it is still 256M. Some qemu machine
definitions have however set this to 512M so for the sake of
treating all architectures fairly, they are reset back to 256M.
Also runqemu is adjusted to
On Wed, 2019-08-28 at 05:06 +, Nathan Rossi wrote:
> Create the do_check task to the binutils-cross include. This task can
> be
> used to execute the binutils test suite for the cross target
> binutils.
> By default this executes all the check targets of the binutils
> Makefile,
> this can
On Wed, 2019-08-28 at 05:06 +, Nathan Rossi wrote:
> Create the do_check task to the binutils-cross include. This task can be
> used to execute the binutils test suite for the cross target binutils.
> By default this executes all the check targets of the binutils Makefile,
> this can however
few build regressions
https://errors.yoctoproject.org/Errors/Details/266071/
https://errors.yoctoproject.org/Errors/Details/266060/
On Mon, Aug 26, 2019 at 7:26 AM Alexander Kanavin
wrote:
>
> Some notes:
> - bjam bootstrap scripts were changed, and the patch for that had to be
> adjusted.
On Wed, 2019-08-28 at 13:41 +0200, Daniel Klauer wrote:
> bitbake removes cleandirs once per prefunc and then again for the actual
> task.
That commit message isn't correct.
It removes cleandirs for the prefunc at the start of the prefunc and
cleandirs for the main function at the start of that
bitbake removes cleandirs once per prefunc and then again for the actual
task. By moving the concat_dtb step here from prefunc to main task we can
add
do_deploy[cleandirs] = "${DEPLOYDIR}"
to deploy.bbclass without losing the files produced by concat_dtb.
It looks like using
It seems convenient for do_deploy to clean up ${DEPLOYDIR} (its output
directory) before running, just like do_install cleans up ${D} before
running. This way we can be sure that a recipe's do_deploy output is not
accidentally contaminated by previously existing files in DEPLOYDIR in
case of
Hi,
I think this patch is not needed anymore since both patches have already been
backported to the latest stable version of systemd v242. To include these
patches in the yocto builds we need to update the SRCREV to the latest commit
in the v242-stable branch of systemd/systemd-stable
Signed-off-by: Robert Yang
---
meta/recipes-devtools/ccache/{ccache_3.7.1.bb => ccache_3.7.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_3.7.1.bb => ccache_3.7.3.bb} (45%)
diff --git a/meta/recipes-devtools/ccache/ccache_3.7.1.bb
- Remove 0001-Do-not-pass-null-pointer-to-freeaddrinfo.patch, the new api
can check the pointer before free it.
- Rmove 0001-makefile.am-update-the-path-of-libnfs.a.patch, it is already in
the source.
- Rmove nfs-utils-musl-limits.patch, it is already fixed.
- Rebased the following
The following changes since commit 9b1c150573ffd0e68d37772d5f47482d86ddde6d:
commands.py: fix typo (2019-08-27 22:52:41 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/pu
Using the generic BSD-2-CLAUSE license as specified on
https://opensource.org/licenses/BSD-2-Clause
Signed-off-by: Christophe Priouzeau
---
meta/files/common-licenses/BSD-2-Clause | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git
Hi,
thanks for the new testing instructions, I ran the builds this morning and
everything worked fine. Let me know if I can do anything else to verify the
builds or help otherwise in the process.
Cheers,
Jan
> On 27. Aug 2019, at 19:11, Randy MacLeod wrote:
>
> On 8/27/19 12:15 PM, Jan
ping
On 8/19/19 11:22 AM, changqing...@windriver.com wrote:
From: Changqing Li
Configuration:
IMAGE_INSTALL_append = " bash"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
Reproduce cmd:
bitbake core-image-minimal -c populate_sdk
Error
On Wed, 28 Aug 2019 at 07:46, wrote:
> By default qemu use -device VGA,edid=on but in some case cannot use
> display because of it.
> +elif arg == 'gtk':
> +self.qemu_opt_script += ' -device virtio-gpu-pci'
>
This also needs:
a) '-display gtk, gl=off' should be
On Wed, 28 Aug 2019 at 07:46, wrote:
> By default qemu use -device VGA,edid=on but in some case cannot use
> display because of it.
> +elif arg == 'gtk':
> +self.qemu_opt_script += ' -device virtio-gpu-pci'
>
We would prefer to use standard vga, and enable virtio
On Wed, 28 Aug 2019 at 06:36, wrote:
> If using qemu-system-aarch64 or qemu-system-arm with the options, an error
> occured as follows:
>
> qemu-system-aarch64: Virtio VGA not available
>
> this commit fixes the error to use -device virtio-gpu-pci instead of
> -vga virtio.
>
Can you please
From: He Zhe
Backport a patch to fix the following error.
safe_file_ops.c:219: BROK: Expected 3 conversions got 2 at meltdown.c:272
Signed-off-by: He Zhe
---
v2: Adjust context based on top of ltp in oe-core
...-cve-meltdown.c-Fix-kernel-symbol-finding.patch | 81 ++
On 8/27/19 11:56 PM, Richard Purdie wrote:
> On Tue, 2019-08-27 at 12:38 +0800, zhe...@windriver.com wrote:
>> From: He Zhe
>>
>> Backport a patch to fix the following error.
>> safe_file_ops.c:219: BROK: Expected 3 conversions got 2 at
>> meltdown.c:272
>>
>> Signed-off-by: He Zhe
>> ---
>>
69 matches
Mail list logo
