[OE-core] [PATCH v2][dunfell] systemd: update from 244.3 to 244.5 stable release

2020-12-14 Thread Mikko Rapeli
Brings in a number of fixes from upstream stable tree: $ git log --format="%h %s" v244.3..v244.5 3ceaa81c61 kernel-install/90-loaderentry: fix when /boot is not mountpoint ecbb5a4f67 nspawn: fix fd leak on failure path a09947ddd4 nspawn: check return of setsid() 334f8e2e8f dissect:

[OE-core] [PATCH] systemd: update from 244.3 to 244.5 stable release

2020-12-14 Thread Mikko Rapeli
Brings in a number of fixes from upstream stable tree: $ git log --format="%h %s" v244.3..v244.5 3ceaa81c61 kernel-install/90-loaderentry: fix when /boot is not mountpoint ecbb5a4f67 nspawn: fix fd leak on failure path a09947ddd4 nspawn: check return of setsid() 334f8e2e8f dissect:

[OE-core] [PATCH 3/4] bzip2: run ptests without valgrind

2020-12-14 Thread Alexander Kanavin
Otherwise, valgrind significantly slows them down, and actually even causes ptest timeouts on arm64. Signed-off-by: Alexander Kanavin --- meta/recipes-extended/bzip2/bzip2/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 4/4] lttng-tools: disable more failing ptests

2020-12-14 Thread Alexander Kanavin
Signed-off-by: Alexander Kanavin --- ...ression-disable-the-tools-live-tests.patch | 35 +++ 1 file changed, 28 insertions(+), 7 deletions(-) diff --git a/meta/recipes-kernel/lttng/lttng-tools/0001-tests-regression-disable-the-tools-live-tests.patch

[OE-core] [PATCH 1/4] kea: upgrade 1.7.10 -> 1.8.1

2020-12-14 Thread Alexander Kanavin
Signed-off-by: Alexander Kanavin --- meta/recipes-connectivity/kea/{kea_1.7.10.bb => kea_1.8.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/kea/{kea_1.7.10.bb => kea_1.8.1.bb} (97%) diff --git a/meta/recipes-connectivity/kea/kea_1.7.10.bb

[OE-core] [PATCH 2/4] valgrind: exclude bar_bad/bar_bad_xml from ptests

2020-12-14 Thread Alexander Kanavin
The tests' output is non-deterministic and sometimes doesn't match the sample output. This has been reported at https://bugs.kde.org/show_bug.cgi?id=430321 (see also an earlier related bug https://bugs.kde.org/show_bug.cgi?id=358213) Until upstream figures out how to fix this, let's not run the

<    1   2