Tim Orling [Fri, 18 Nov 2022 17:52:07 +0000 (09:52 -0800)]
liburi-perl: upgrade 5.08 -> 5.17
* Author changed back from ETHER to OALDERS
* Use CPAN_MIRROR for SRC_URI
* Update HOMEPAGE
* Update RPEPENDS for -ptest
* Patch to skip TODO test cases
For changes, see:
https://metacpan.org/release/OALDERS/URI-5.17/changes
License-Update: whitespace changes
Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tim Orling [Fri, 18 Nov 2022 17:52:06 +0000 (09:52 -0800)]
libtest-warnings-perl: move from meta-perl
liburi-perl in oe-core now RDEPENDS on libtest-warnings-perl for ptest
* Update HOMEPAGE; fix syntax
* Add SUMMARY
* Add BUGTRACKER
* Use CPAN_MIRROR for SRC_URI
* Use actual LICENCE file for LIC_FILES_CHKSUM
* Add RDEPENDS
* Add RDEPENDS on perl-modules for ptest
- Too many hidden dependencies that fail silently, but pass
with full perl-modules
* Add self as maintainer
* Add to ptest-packagelists (fast)
Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Chen Qi [Fri, 18 Nov 2022 13:38:55 +0000 (21:38 +0800)]
dhcpcd: fix to work with systemd
Currently, dhcpcd does not work well with systemd. When using dhcpcd
to configure network, the /etc/resolv.conf contents are not correct.
This issue could easily be reproduced by using 'qemu + slirp' to
start a systemd based image and using dhcpcd to configure network.
The expected 'nameserver 10.0.2.3' is not in /etc/resolv.conf.
The root cause of this problem is that dhcpcd assumes the resolvconf
should recognize .protocol suffix[1]. But systemd's resolvconf (which
is a symlink to resolvectl) has a limited support for traditional
resolvconf interface[2], and "may not work with all clients"[3]. This
of cource includes the clients that use the .protocol suffix.
The current situation is:
1. systemd is not going to support the .protocol suffix in the foreseeable
near future[4].
2. dhcpcd does not want to merge systemd specific patch and insists
systemd needs to consider the .protocol suffix[5][6].
It's a normal thing that people have different opinions. As a build system
that supports such combination, however, we do need to come up with a
solution to fix this typical integration problem, making dhcpcd and systemd
work together.
This patch solves this integration problem by relying on dhcpcd's ability
to manage its own resolv.conf contents. But instead of letting it to write
to /etc/resolv.conf directly, we supply the generated contents to resolvconf.
In this way, the resolvconf still stands in the central place and dhcpcd remains
a supplier to it. And the /etc/resolv.conf can get the correct contents.
With this patch, dhcpcd could work with both sysvinit and systemd.
Sergei Zhmylev [Fri, 18 Nov 2022 13:30:20 +0000 (16:30 +0300)]
oeqa/qemurunner: implement vmdk images support
Qemurunner should not pass rootfs to runqemu in case
rootfs is not a filesystem itself. Some images could
be built into some disk format like vmdk and this
commit makes qemurunner handle such images properly.
Signed-off-by: Sergei Zhmylev <s.zhmylev@yadro.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tim Orling [Thu, 17 Nov 2022 23:15:35 +0000 (15:15 -0800)]
at-spi2-core: upgrade 2.44.1 -> 2.46.0
* Both atk and at-spi2-atk are now merged into this project.
- drop atk_2.38.0.bb
- drop at-spi2-atk_2.38.0.bb
- PROVIDES += "atk at-spi2-atk"
- RPROVIDES:${PN} += "atk at-spi2-atk"
* DEPENDS on libxml2
* Ships:
${libdir}/gnome-settings-daemon-3.0/gtk-modules/at-spi2-atk.desktop
${libdir}/gtk-2.0/modules/libatk-bridge.so
What's new in at-spi2-core 2.46.0:
* Fix GetInterfaces documentation on org.a11y.atspi.Accessible
interface.
What's new in at-spi2-core 2.45.91:
* Send device event controller events using the same signature as other
events.
* Document the Accessible, Action, and Cache dbus interfaces.
* Fix license of atspi-gmain.c (#87).
What's new in at-spi2-core 2.45.90:
* xml: Add some documentation.
* xml: Fix event arguments.
* xml: Add some missing DeviceEventController methods.
* Bind the AT-SPI bus to the graphical session.
* Mark bus service as belonging to the session slice.
* Add ATSPI_ROLE_PUSH_BUTTON_MENU.
* Add an "announcement" event/signal to allow objects to send
notifications (!63).
* Various code clean-ups and test improvements.
What's new in at-spi2-core 2.45.1:
* Atk and at-spi2-atk are now merged into this project.
* Now requires meson 0.56.2 and glib 2.67.4.
* at-spi2-atk: Expose the accessible hierarchy via dbus introspection.
* Properly escape the AT-SPI bus address; fixes warnings about the
address not containing a colon (!55).
* Add a text value to AtspiValue, so that a value can expose a textual
description, as in the new Atk value API.
* Add atspi_event_listener_register_with_app, to allow an event listener
to be registered only for a given application (!52).
Chen Qi [Thu, 17 Nov 2022 11:14:10 +0000 (19:14 +0800)]
resolvconf: make it work
The current resolvconf does not work. Make it work with the
following changes.
1. Install normalize-resolvconf, which is used by resolvconf.
2. Add dependencies: sed, util-linux-flock.
util-linux-flock is needed by our busybox does not support '-w'
by default. sed is needed because we want to avoid package
QA issue complaining sed is needed by no one provides it.
3. Add a patch to replace 'readlink -m' with 'readlink -l'.
This could avoid the runtime dependency on coreutils. The replacement
is safe as /etc always exits in OE's system.
4. Remove allarch inheritage. This is because the above RDEPENDS
change does not allow this any more. test_sstate_allarch_samesigs
would fail if we don't do this.
Chen Qi [Thu, 17 Nov 2022 04:11:55 +0000 (12:11 +0800)]
kernel.bbclass: make KERNEL_DEBUG_TIMESTAMPS work at rebuild
Currently, the KERNEL_DEBUG_TIMESTAMPS is not working as expected
at rebuild. That is, even if we set it to "1", the kernel build time
is not changed. The problem could be reproduced by the following steps.
1. bitbake core-image-minimal; start image and check `uname -a` output.
2. set in local.conf: KERNEL_DEBUG_TIMESTAMPS = "1"
3. bitbake core-image-minimal; start image and check `uname -a` output.
It's expected that after enabling KERNEL_DEBUG_TIMESTAMPS, the kernel
build time will be set to current date. But it's not. This is because
the compile.h was not re-generated when do_compile task was re-executed.
In mkcompile_h, we have:
"""
# Only replace the real compile.h if the new one is different,
# in order to preserve the timestamp and avoid unnecessary
# recompilations.
# We don't consider the file changed if only the date/time changed,
# unless KBUILD_BUILD_TIMESTAMP was explicitly set (e.g. for
# reproducible builds with that value referring to a commit timestamp).
# A kernel config change will increase the generation number, thus
# causing compile.h to be updated (including date/time) due to the
# changed comment in the
# first line.
"""
It has made it very clear that it will not be re-generated unless
we have KBUILD_BUILD_TIMESTAMP set explicitly. So we set this variable
explicitly in do_compile to fix this issue.
Joshua Watt [Wed, 16 Nov 2022 18:49:19 +0000 (12:49 -0600)]
qemu-helper-native: Correctly pass program name as argv[0]
The previous version of this wasn't correctly passing the program name
as argv[0], and was also over-complicated anyway because argv[] is
guaranteed to be terminated with a NULL pointer, so it can be passed
directly to the execv'd process without needing to be copied.
| Manifest [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot not found in imx8mm_dummy cortexa53-mx8mm cortexa53 armv8a-crc armv8a aarch64 allarch x86_64_x86_64-nativesdk (variant '')?
are fatal now and cannot be ignored but must be debugged.
Unfortunately, the currently emitted error message is a bit imprecise
with telling the reader what has actually gone wrong.
This commit:
* adds the word 'sstate' to the error message to clarify the scope we
are dealing with ('sstate manifests', since there are other manifests,
too)
* does not randomly print the last manifest file searched for as THE
manifest file that could not be found
Instead, we print the name of the task the sstate was searched for
* adds the word 'multilib' to variant to make clear which variant we are
talking about
* adds a separate line noting the searched pkgarchs and adds explicitly
mentions this word ('pkgarchs')
* prints a list of ALL manifest file locations attempted
* removes the '?' at the end of the message since such errors indeed
leave the question of what is the cause but the error message itself
is more like a statement.
The result for the exact same issue as noted above then looks as
follows:
| The sstate manifest for task 'dbus:populate_sysroot' (multilib variant '') could not be found.
| The pkgarchs considered were: imx8mm_dummy, cortexa53-mx8mm, cortexa53, armv8a-crc, armv8a, aarch64, allarch, x86_64_x86_64-nativesdk.
| But none of these manifests exists:
| [..]/tmp/sstate-control/manifest-imx8mm_dummy-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-cortexa53-mx8mm-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-cortexa53-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-armv8a-crc-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-armv8a-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-aarch64-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-allarch-dbus.populate_sysroot
| [..]/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-dbus.populate_sysroot
Wang Mingyu [Wed, 16 Nov 2022 05:19:56 +0000 (13:19 +0800)]
libpipeline: upgrade 1.5.6 -> 1.5.7
Changelog:
============
* Add notes to libpipeline(3) of when functions were added.
* Transferred Git repository to https://gitlab.com/libpipeline/libpipeline.
* Make `socketpair` tests used by `./configure --enable-socketpair-pipe`
compatible with C23.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Wed, 16 Nov 2022 05:13:08 +0000 (13:13 +0800)]
btrfs-tools: upgrade 6.0 -> 6.0.1
Changelog:
==========
* send: minor speed up for v2 due to increased buffer size
* resize: invalid command line options fail with error code
* quota rescan:
* add long options --status and --wait
* new option to wait but don't start rescan
* qgroup show: print path by default, updated format
* qgroup: new subcommand clear-stale, remove qgroups without their subvolumes
* experimental:
* add warnings to commands that have it enabled (mkfs, image, btrfstune)
* other:
* documentation, help text, error message updates
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Tim Orling [Tue, 15 Nov 2022 16:51:34 +0000 (08:51 -0800)]
python3-hypothesis: upgrade 6.56.4 -> 6.57.1
6.57.1 - 2022-11-14
This patch updates some internal type annotations and fixes a formatting bug
in the explain phase reporting.
6.57.0 - 2022-11-14
Hypothesis now raises an error if you passed a strategy as the alphabet=
argument to text(), and it generated something which was not a length-one
string. This has never been supported, we’re just adding explicit validation
to catch cases like this StackOverflow question.
Mikko Rapeli [Mon, 14 Nov 2022 15:50:38 +0000 (17:50 +0200)]
runqemu: limit slirp host port forwarding to localhost 127.0.0.1
With default slirp port forwarding config qemu listens on TCP ports
2222 and 2323 on all IP addresses available on the build host. Most
use cases with runqemu only need it for localhost and it is not
safe to run qemu images with root login without password enabled
and listening on all available, possibly Internet reachable network
interfaces. Limit qemu port forwarding to localhost 127.0.0.1 IP
address. Now qemu machine SSH and telnet ports are only
reachable from the build host machine, not full Internet.
If qemu machine needs to be reachable from network, then it can
be enabled via local.conf or machine config variable QB_SLIRP_OPT:
Mikko Rapeli [Mon, 14 Nov 2022 15:50:37 +0000 (17:50 +0200)]
qemurunner.py: support setting slirp host IP address
By default host side IP address is not set and qemu listens
on all IP addresses on the host machine which is not a good
idea when images have root login enabled without password.
It make sense to listen only on localhost IP address 127.0.0.1 using
config change like:
This config works for qemu itself, but breaks runqemu which tries to
parse the host side port number from qemu process command line arguments.
So change the runqemu side hostfwd parsing for port number to ignore
the host IP address field.
mesa: do not rely on native llvm-config in target sysroot
Sadly the magic is not perfect: llvm-config contains a hardcoded
value for the libdir from the native configuration, and things will
break if the target build installs libraries somewhere else (e.g. lib64).
llvm-config in target bindir also needs a rpath adjustment,
otherwise it simply won't even run when e.g. building for arm on x86.
To avoid patching llvm-source let's simply add more cases to the
llvm-config wrapper script, so that falling through to llvm-config binary
is avoided. Fortunately those cases are all static in what they return,
even though llvm-config binary does poke around the file tree to arrive
at them (which is where breakage happens if native and target don't match
exactly wrt libdir).
I verified that this works by building mesa with llvm enabled for
qemuarm64 and with baselib set to 'lib64' - so that both the target
architecture and target libdir differ from native ones.
Enable-more-tests-while-cross-compiling.patch
replaced with a request to upstream to solve
this correctly with meson's exe_wrapper:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3067
https://github.com/mesonbuild/meson/issues/11029
License-update: formatting
Make needed adjustments to ptests.
Backport a couple of patches to address musl failures.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Mon, 14 Nov 2022 03:20:38 +0000 (11:20 +0800)]
libsoup: upgrade 3.2.1 -> 3.2.2
Changelog:
==========
* Various HTTP/2 Fixes:
* Fix `content-sniffed` not being emitted for resources without content
* Fix leak of SoupServerConnection when stolen
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Mon, 14 Nov 2022 03:19:33 +0000 (11:19 +0800)]
iso-codes: upgrade 4.11.0 -> 4.12.0
Changelog:
=========
- ISO 3166-1: Update name for TR. Fixes #38
- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-2. Closes: #1020633
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Peter Marko [Sun, 13 Nov 2022 14:33:05 +0000 (15:33 +0100)]
systemd: add group render to udev package
From NEWS for v236:
* The "uaccess" udev tag has been dropped from /dev/kvm and
/dev/dri/renderD*. These devices now have the 0666 permissions by
default (but this may be changed at build-time). /dev/dri/renderD*
will now be owned by the "render" group along with /dev/kfd.
Without the group systemd-udevd startup logs:
/lib/udev/rules.d/50-udev-default.rules:39 Unknown group 'render', ignoring
/lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring
Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:12:17 +0000 (11:12 +0800)]
sysstat: upgrade 12.6.0 -> 12.6.1
Changelog:
==========
* Fix possible overflow in sa_common.c (GHSL-2022-074).
* sa_conv.c: Make size of statistics structures from older sysstat
versions immutable.
* Declare sadc dependency on libsyscom.a.
* Fix gcc v11.2 warnings.
* Various cosmetic fixes.
* sar: Remove `-I int_list` from man-page and help.
* Consolidate systemctl commands in README file.
* Remove whitespace characters at the end of lines.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:11:37 +0000 (11:11 +0800)]
sudo: upgrade 1.9.12 -> 1.9.12p1
mips-fix.patch
removed since it's included in 1.9.12p1
Changelog:
=========
*Sudo's configure script now does a better job of detecting when the
-fstack-clash-protection compiler option does not work. GitHub issue #191.
*Fixed CVE-2022-43995, a potential out-of-bounds write for passwords smaller
than 8 characters when passwd authentication is enabled. This does not affect
configurations that use other authentication methods such as PAM, AIX
authentication or BSD authentication.
*Fixed a build error with some configurations compiling host_port.c.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:10:29 +0000 (11:10 +0800)]
sed: update 4.8 -> 4.9
License-Update:
-URL of license changed from
https://www.gnu.org/philosophy/why-not-lgpl.html
to https://www.gnu.org/licenses/why-not-lgpl.htm
-Copyright year updated to 2022
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:08:10 +0000 (11:08 +0800)]
python3-wheel: upgrade 0.38.0 -> 0.38.4
Changelog:
===========
-Fixed PKG-INFO conversion in bdist_wheel mangling UTF-8 header values in METADATA
-Fixed install failure when used with --no-binary, reported on Ubuntu 20.04,
by removing setup_requires from setup.cfg
-Fixed regression introduced in v0.38.1 which broke parsing of wheel file names
with multiple platform tags
-Removed install dependency on setuptools
-The future-proof fix in 0.36.0 for converting PyPy's SOABI into a abi tag was
faulty. Fixed so that future changes in the SOABI will not change the tag.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:06:02 +0000 (11:06 +0800)]
python3-subunit: upgrade 1.4.0 -> 1.4.1
Changelog:
=========
IMPROVEMENTS
-------------
* Add support for Python 3.9
* Add support for Python 3.10
* Drop support for Python 2.7, 3.4, and 3.5
* Convert python scripts to entry_points.
* Migrate CI from travis to GitHub actions.
* Add options to output filter to set timestamps.
* Remove dependency on unittest2.
BUGFIXES
----------
* Fix tests with testtools >= 2.5.0.
* Mark rawstrings as such, fixing warnings.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 03:02:06 +0000 (11:02 +0800)]
python3-pip: update 22.3 -> 22.3.1
Bug Fixes
-----------
Fix entry point generation of pip.X, pipX.Y, and easy_install-X.Y to correctly
account for multi-digit Python version segments (e.g. the "11" part of 3.11). (#11547)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Wang Mingyu [Sun, 13 Nov 2022 02:56:04 +0000 (10:56 +0800)]
gi-docgen: upgrade 2022.1 -> 2022.2
Changes since 2022.1
--------------------
* Use const.*.html instead of constant.*.html for search index links [!146]
* Remove "terms" from index.json, rewrite commandline search to work without it [!148]
* Add interface type description [!149]
* Fix failure to generate link to error domain [!151]
* Make log.log() thread safe [#129]
* Quote string constant values [#128]
* Set the license of the generated documentation [#133]
* Support (scope forever) [!155]
* Add a way to frame images [!156]
* Use the appropriate namespace for indices [#137]
* Fix type annotations for Repository packages and c_includes [!160]
* Add py.typed to comply with PEP561 [!159]
* Add links to external classes in the hierarchy [#132]
* Use definition lists for callable arguments [#123]
* Improve styles [!165]
* Use definition lists for callable arguments
* Clarify generated description for GError arguments
* Clarify generated description for nullable in/out arguments
* Add emblems for versions and stability
* Require a sufficient minimum dependency of markdown [!166]
* Add a "serve" command
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Jordan Crouse [Fri, 11 Nov 2022 21:47:12 +0000 (21:47 +0000)]
spirv-tools: Correctly set the prefix in exported cmake packages
spirv-tools exports Cmake packages. When they are installed the
INTERFACE_LINK_LIBRARIES variable is not correctly updated to use
_IMPORT_PREFIX like the other variables. This may have something to do with
the path to the sysroot being different than the source path.
The existing recipe recognizes that the sysroot path made it through to the
install and tries to get rid of it, but this just ends up with dependent
tools looking in vain for /usr/lib/librt.so.
Replace the INTERFACE_LINK_LIBRARIES value in SPIRV-ToolsTarget.cmake with
"${IMPORT_PREFIX}/lib".
Signed-off-by: Jordan Crouse <jorcrous@amazon.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Jose Quaresma [Fri, 11 Nov 2022 18:05:46 +0000 (18:05 +0000)]
rm_work: exclude the SSTATETASKS from the rm_work tasks sinature
We can exclude the SSTATETASKS from the rm_work task signature
to avoid running the task when we remove some setscene tasks
from the dependencie chain.
The inject_rm_work handler on the rm_work bbclass triggers the
rm_work task running for any signature change in the dependencie
chain of the task do_build of each recipe.
i.e INHERIT:remove = "create-spdx" will trigger the do_rm_work
when we collect the sstate cache with INHERIT = "create-spdx"
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Jose Quaresma [Fri, 11 Nov 2022 18:05:45 +0000 (18:05 +0000)]
sstatesig: skip the rm_work task signature
We can skip the rm_work task signature to avoid running the task
when we remove some tasks from the dependencie chain.
The inject_rm_work handler on the rm_work bbclass triggers the
rm_work task running for any signature change in the dependencie
chain of the task do_build of each recipe.
i.e INHERIT:remove = "create-spdx" will trigger the do_rm_work
when we collect the sstate cache with INHERIT = "create-spdx"
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Adds argument parsing to the conversion script so that the fields that
the script uses to do conversions can be customized on the command line.
The intention is to allows easier customization without having to fork
the script, and allow automated checking on 3rd party layers via CI
without false positives
vala: install vapigen-wrapper into /usr/bin/crosscripts and stage only that
Staging the whole /usr/bin is not correct, as it pulls in also
all the vala's cross binaries, which may be discovered by other recipes
and things will go wrong then.
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:35 +0000 (19:31 +0000)]
classes/testexport: move to classes-recipe
This class should be in classes-recipe as, like testimage, it is specific
to image recipes.
This also solves a regression where simply IMAGE_CLASSES += "testexport"
doesn't work if testimage isn't already in IMAGE_CLASSES. The testexport
class adds testimage to IMAGE_CLASSES, but by this point it's too late.
Now that the class can only be inherited via IMAGE_CLASSES, we can
simply inherit testimage directly.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:31 +0000 (19:31 +0000)]
oeqa/selftest/runqemu: don't hardcode qemux86-64
Don't hardcode qemux86-64. This has some complications: the
IMAGE_FSTYPES needs to be constructed to reflect what the machine can
do (only x86 machines can build ISO images), and several tests which need
a wic file are currently limited to qemux86-64.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
When the trivial test binary, which just calls printf(), is compiled for
aarch64 with -O2 -D_FORTIFY=2 (as is the default configuration), gdb
resolves main() to the inlined printf() wrapper in stdio2.h instead of
main.c, so the test fails.
Presumably, this is due to debugging being unreliable with -O2. Solve
this problem by not caring where the main() breakpoint resolves to, just
check that it was resolved at all.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:27 +0000 (19:31 +0000)]
oeqa/selftest/imagefeatures: set a .wks in test_fs_types
Set WKS_FILE to wictestdisk.wks, which is a very simple Wic file that
simply contains the root filesystem. It may not actually boot but this
test doesn't care, and it does exercise the wic image construction on
all machines.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:24 +0000 (19:31 +0000)]
oeqa/selftest/efibootpartition: improve test
This test was overly complex with a setUp() method for a single test case,
which was marked as a class function for no good reason.
Generalise the test so that it has the possibility of working on more
machines in the future, add a decorator so that it only runs on
qemux86-64, and respect QEMU_USE_KVM to speed up test execution.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:23 +0000 (19:31 +0000)]
oeqa/selftest/buildoptions: skip test_read_only_image on qemuarm64
qemuarm64 currently uses SERIAL_CONSOLES_CHECK but this is incompatible
with read-only rootfs under sysvinit. Until qemuarm64 doesn't use this,
skip the test on qemuarm64.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Ross Burton [Wed, 9 Nov 2022 19:31:22 +0000 (19:31 +0000)]
oeqa/core/decorator: add decorators to skip based on HOST_ARCH
There are already decorators to skip on the value of MACHINE, but for
flexibility it's better to skip based on the target architecture. This
means, for example, the ISO image tests could skip if the architecture
isn't x86.
Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
