commits: 55d11f57 doc/dbus-api-design: fix wrong closing tag a96f417f CI: Run a detached pipeline for merge requests 9e0477fc CI: Only run for pushes to dbus 077f7e43 CI: Remove an obsolete workaround 07fe44f4 CI: Update Windows runners ec708d55 CI: Avoid using a no-op download location that gives a 403 error 45e6e93e dbus_message_iter_get_signature: Fix two memory leaks on OOM 0bb1942e dbus-internals: use `_DBUS_FUNCTION_NAME` in `_dbus_verbose()` 8df1b8be dbus-sysdeps-win: do not log function name twice 5c3a4e81 dbus-spawn-win: use `_DBUS_FUNCTION_NAME` instead of `__FUNCTION__` 8e457296 Update NEWS e1ffce17 Revert "CI: Remove an obsolete workaround" 40c0802f monitor test: Log the messages that we monitored a70c8f2f bus: Assign a serial number for messages from the driver 39b5c617 monitor test: Reproduce #457 f99e5de1 Update NEWS 21414587 AUTHORS: Update f90d4f16 Release v1.14.8
Ross Burton [Tue, 20 Jun 2023 12:34:04 +0000 (13:34 +0100)]
sysfsutils: don't install to base_libdir
This library now ships a pkgconfig file but $base_libdir isn't in the
search path, so can't be used.
As the base_libdir/libdir split is pretty meaningless these days, simply
stop installing into base_libdir. This was added to silence warnings
from pcmciautils[1] but PCMCIA isn't really a thing anymore so this
shouldn't be a problem.
Alberto Planas [Mon, 19 Jun 2023 06:42:48 +0000 (08:42 +0200)]
rpm2cpio.sh: update to the last 4.x version
openSUSE RPMs are compressing the RPM payload using zstd, that
correspond to the magic ID 0x28, 0xb5, 0x2f.
This patch update the script to the last version from the rpm project,
and add support to this compression format, and extract the cpio payload
using the "unzstd" binary.
Signed-off-by: Alberto Planas <aplanas@suse.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Chen Qi [Mon, 19 Jun 2023 04:35:56 +0000 (12:35 +0800)]
unzip: remove hardcoded LARGE_FILE_SUPPORT
Now that unzip's configure can correctly do the detection even in
case of cross compilation, there's no need to use this hardcoded
LARGE_FILE_SUPPORT flag.
Chen Qi [Mon, 19 Jun 2023 04:35:55 +0000 (12:35 +0800)]
unzip: fix configure check for cross compilation
The original configure runs a generated binary to determine
features. This is not correct for cross compilation. So change
the runtime tests into compile-time tests to fix the issue.
Chen Qi [Mon, 19 Jun 2023 04:35:54 +0000 (12:35 +0800)]
zip: remove unnecessary LARGE_FILE_SUPPORT CLFAGS
As the zip's configure has been updated to use compile-time
check, it now can do the check correctly, thus no need to
pass LARGE_FILE_SUPPORT to CFLAGS.
Chen Qi [Mon, 19 Jun 2023 04:35:53 +0000 (12:35 +0800)]
zip: fix configure check by using _Static_assert
It's incorrect to run a cross-compiled program on build machine
to check if some feature is available or not. As these two checks
in zip are basically just checking the size, we can use _Static_assert
and sizeof to do such check at compile time.
Khem Raj [Sun, 18 Jun 2023 21:48:24 +0000 (14:48 -0700)]
python3-bcrypt: Use BFD linker when building tests
Some of the tests use symbols from libpython3 e.g. PyBytes_FromStringAndSize
but does not add it to linker cmdline, its perhaps cargo which
should be fixed for that, this however is not something we can
fix in OE. So switch to using bfd linker explicitly when
building with ptests
runqemu: Stop passing bindir to the runqemu-ifup call
Since https://git.yoctoproject.org/poky/commit/?id=51063c1e6ac
we need to pass exactly 2 arguments to runqemu-ifup, otherwise
the script will return an error since bindir is no longer being
used.
However the call to runqemu-ifup from runqemu is still passing
bindir as an argument resulting in the error mentioned above,
remove the bindir argument to fix this issue.
[YOCTO #15150]
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Trevor Gamblin [Tue, 20 Jun 2023 17:59:13 +0000 (13:59 -0400)]
glib-networking: use correct error code in ptest
The eagain patch is currently using G_IO_ERROR_BUSY as part of the check
to retry when the simul_read_thread test fails during ptests, but the
actual error code is 27, which corresponds to G_IO_ERROR_WOULD_BLOCK.
Change the check so that it looks for the right code.
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 19 Jun 2023 13:40:55 +0000 (14:40 +0100)]
insane: Improve patch-status layer filtering
Now that we have layer overrides, we can easily enable patch-status in
ERROR_QA without the hardcoded code making it easier for other layers
to opt into the checks.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Mon, 19 Jun 2023 13:40:33 +0000 (14:40 +0100)]
bitbake.conf: Add layer-<layername> override support
Add a new layer specific override based upon the FILE_LAYERNAME support now present
in bitbake. In particular this allows layer specific QA warnings and errors to
be made more easily.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sun, 18 Jun 2023 23:00:25 +0000 (00:00 +0100)]
ptest-runner: Ensure data writes don't race
Currently the code can race as there is a read/write thread handling the stdio but
there is no guarantee that when the process exits, the thread has handled all the
data. This results in output where "END:" isn't actually at the end of the logs
but somewhere in the middle of the output.
Update to a revision with this fix.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Mon, 19 Jun 2023 11:49:27 +0000 (12:49 +0100)]
ghostscript: mostly rewrite recipe
This started as a patch cleanup but escalated rapidly.
Remove unneeded patches:
- mkdir-p.patch isn't needed now the Makefiles appear to have the correct
dependencies.
- ghostscript-9.15-parallel-make.patch appears to be unneeded for the same
reason
- base-genht.c-add-a-preprocessor-define-to-allow-fope.patch isn't needed
- cups-no-gcrypt.patch isn't needed
- do-not-check-local-libpng-source.patch can be replaced by deleting
the libpng/ directory, as is already done for jpeg/
- ghostscript-9.21-native-fix-disable-system-libtiff.patch is not needed
when we stop doing native builds (see below)
Remove the need for ghostscript-native to build and install tools that
are needed at target build-time: ghostscript can do this itself. Remove
the BBCLASSEXTEND and all of the native overrides.
Inherit pkgconfig and explicitly tell configure to use the pkgconfig
binary: unless told otherwise this configure will refuse to use an
unprefixed pkgconfig in cross builds.
Review DEPENDS and add missing freetype and zlib dependencies.
Ghostcript will use the embedded copies of libraries over system
libraries, so extend the deletion of jpeg and libpng to include expat,
freetype, and cups as we want to link to our build of those. We can't
delete zlib as it is explicitly used when building the native tools.
Add PACKAGECONFIGs for optional libidn and libpaper dependencies.
Remove HAVE_SYS_TIME_H assignments, the upstream bug was fixed in 2011.
Clean up comments: there's no need to explain how to use PACKAGECONFIG,
and justify the use of autotools-brokensep.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Chen Qi [Mon, 19 Jun 2023 07:41:10 +0000 (00:41 -0700)]
rpm: write macros under libdir
If we create a macros file under etc/, the populate_sdk task would
fail if 'package-management' is in SDKIMAGE_FEATURES and nativesdk-rpm-build
is installed.. The error message is like below:
unable to place /.../sdk/image/etc/rpm in final SDK location
This is because it's trying to move the etc/rpm dictory into the
host sysroot but the <host_sysroot>/etc/rpm has already exists.
To solve this problem, avoid creating /etc/rpm/macros for nativesdk-rpm-build,
use ${libdir}/macros instead. In this way, the macros file is hold
in nativesdk-rpm. As nativesdk-rpm-build depends on nativesdk-rpm,
the 'rpmbuild' command inside SDK can still correctly find find-debuginfo
binary.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sun, 18 Jun 2023 09:09:16 +0000 (10:09 +0100)]
ptest-runner: Pull in sync fix to improve log warnings
Pulls in:
utils: Ensure buffers are flushed after child exits
We currently wait for the child to exit but we don't flush the buffers.
This can mean the output ends up out of sync and the END: line isn't at
the end of the logs.
We've recently seen a lot of issues related to this on the autobuilder.
Add in a flush call for all fds to ensure buffers are in sync. This
does appear to improve warnings on the autobuilder now we started detecting
the issue.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
testimage: implement test artifacts retriever for failing tests
Add a basic artifacts retrievers in testimage class which:
- triggers when at least one runtime test fails but tests execution
encountered no major issue
- reads a list of paths to retrieve from TESTIMAGE_FAILED_QA_ARTIFACTS
- checks for artifacts presence on target
- retrieve those files over scp thanks to existing ssh class
- store those files in an "artifacts" directory in "tmp/log/oeqa/<image>"
This implementation assumes that the SSH or Qemu target has run and
finished gracefully. If tests do not finish because of an exception,
artifacts will not be retrieved
oeqa/core/runner: add helper to know about expected failures
Testing framework currently uses the unittest.expectedFailure decorator for
tests that can have intermittent failures (see PTEST_EXPECT_FAILURE = "1")
in core-image-ptest.bb. While it allows upper layers to run tests without
failing on "fragile" tests, it prevents those from knowing more about those
failing tests since they are not accounting as failures (for example we
could want to retrieve some logs about failed tests to improve them, and
eventually to drop expectFailure decorator)
Add a helper to allow upper layers to know about those failures which won't
make global testing session
Louis Rannou [Thu, 15 Jun 2023 11:43:55 +0000 (13:43 +0200)]
base-passwd: add the wheel group
The wheel group is not declared while it can be used to access the systemd
journal and to configure printers in CUPS. It can also be used for su and sudo
permissions.
So far it was created later in the rootfs postcommand systemd_create_users.
Signed-off-by: Louis Rannou <lrannou@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Louis Rannou [Thu, 15 Jun 2023 11:43:54 +0000 (13:43 +0200)]
systemd: replace the sysusers.d basic configuration
The default sysusers basic.conf.in file sets the root home directory to `/root`
and does not permit its configuration. Replace the file delivered by systemd so
the root home directory matches the `ROOT_HOME` variable.
Signed-off-by: Louis Rannou <lrannou@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Louis Rannou [Thu, 15 Jun 2023 11:43:53 +0000 (13:43 +0200)]
rootfs-postcommands: change sysusers.d command
The configuration in sysusers.d used to be parsed to create users/groups at
build time instead at runtime. This was leading to several conflicts with
users/groups defined in base-passwd recipe and specific definitions in recipes
inheriting the useradd class. Some of those conflicts raised unseen errors in
the do_rootfs command's logs.
As an example, the root home directory is set by default to `/home/root` but
systemd expects it as `/root`.
The new command `systemd_sysusers_check` checks each configuration for
users/groups and compare their properties to what is actually defined in the
`/etc/passwd` and `/etc/group` of the target rootfs.
Signed-off-by: Louis Rannou <lrannou@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 16 Jun 2023 16:12:46 +0000 (17:12 +0100)]
strace: Disable failing test
This test is failing for uncertain reasons. We have reported upstream, disable
it until we can work out why this happened. The point it started failing is
unclear due to other test framework issues.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Fri, 16 Jun 2023 15:41:43 +0000 (16:41 +0100)]
oeqa/logparser: Fix ptest No-section exception
Occasionally we see:
File "/media/build/poky/meta/lib/oeqa/runtime/cases/ptest.py", line 27, in test_ptestrunner_expectfail
self.do_ptestrunner()
File "/media/build/poky/meta/lib/oeqa/runtime/cases/ptest.py", line 77, in do_ptestrunner
results, sections = parser.parse(ptest_runner_log)
File "/media/build/poky/meta/lib/oeqa/utils/logparser.py", line 80, in parse
self.results[current_section['name']][result.group(1).strip()] = t
KeyError: 'No-section'
which occurs when there are "results" outside the main log section. The strace
tests do then upon failure as they dump logs there.
Add code to avoid the tracebacks and just make them warnings.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sat, 17 Jun 2023 10:30:16 +0000 (11:30 +0100)]
oeqa/selftest/oescripts: Fix qemu-helper selftest
The updated selftest was assuming qemu-bridge-helper was available on the host
system which isn't always the case. Tweak the test case to avoid this issue by
adding dedicated help output and checking for this specifically.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 15 Jun 2023 16:59:06 +0000 (17:59 +0100)]
runqemu/qemu-helper: Drop tunctl
ip tuntap provides the functionality that we obtained from tunctl. We only
needed tunctl when ifconfig was more available than ip. That isn't the case
now so we can drop tunctl and all the hoops we need to jump through to build
and provide it.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: BSD-3-Clause code removed in
https://github.com/sphinx-doc/sphinx/commit/a7f5d91c29d6f377b9fe7e926965c6f9d3e7b802
which was a part of 7.0.1 update
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Thu, 15 Jun 2023 12:30:43 +0000 (13:30 +0100)]
coreutils: fix build when the host has fr_FR.
There is a missing comma in an AC_TRY_RUN call which means it has no
fallback for cross-compilation, so if the host doesn't have a French
locale then AC_TRY_RUN fails.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
attr: package /etc/xattr.conf with the library that consumes it
This matters for example with latest coreutils where cp
wouldn't copy extended attributes by default if the config
file specifying that policy is not there, and so ptest fails.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
