Compiling code is memory-intensive, especially kernel modules like the
SystemTap probes, so give the VM 768MB of RAM. Using 1GB appears to
cause PCI error, interestingly.
Hopefully this solves the intermittent failures caused by OOMs during
the SystemTap test.
[ YOCTO #14673 ]
(From OE-Core rev: 50ff1f018a670c963e1979dee76ebd696153b4c1)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When attempting to execute runqemu on qemuarmv5, the following error is
encountered:
runqemu - ERROR - Failed to run qemu: qemu-system-arm: versatilepb: memory size must not exceed 256MB
To work around this, limit the QB_MEM size for qemuarmv5, similar to
what is being done for qemumips.
(From OE-Core rev: 6450138afebffcc55ab32afadd5fb979274fff2b)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the result of automated script conversion:
scripts/contrib/convert-overrides.py <oe-core directory>
converting the metadata to use ":" as the override character instead of "_".
(From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
They have been replaced by core-image-minimal-ptest-fast/all
(From OE-Core rev: 0d5bd979a9f67474c4da1d69377a1a1c2161ca6b)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As this image isn't buildable without ptest (the packages won't exist),
depend on the ptest DISTRO_FEATURE to ensure we don't try and build it.
(From OE-Core rev: 0fe856d726c6d9c35533e32e70fbe05ef2b88b17)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit 45da2fc4f7.
qemumips is unstable with more than 256MB memory, the original issue
this limit was added for remains.
We'll have to find other solutions to the systemd out of memory issues.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes:
WARNING: core-image-sato-sdk-1.0-r0 do_testimage: Couldn't login into serial console as root using blank password
WARNING: core-image-sato-sdk-1.0-r0 do_testimage: The output:
root
<<< run_serial(): command timed out after 60 seconds without output >>>
In another run, this error was seen:
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 14.3M are free, but a safety buffer of 16.0M is enforced.
With updates to systemd and Qemu we should revert: 499a31cf06 core-image-sato: don't use 512MB in qemumips
(From OE-Core rev: cf92c8bbd017338e7e91ac092c6f222b6e37e44a)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Unfortunately, a couple of tests sporadically fail still;
bugs have been filed, but they will take time to resolve.
(From OE-Core rev: 6b408f40b6c214d05433c41f0cd6200c715cc615)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This can be useful with a more specific, targeted and robust set of ptest
packages; the benefit is that ptest regressions are caught as they happen
and can be more easily traced to changes that caused them.
The existing AB ptest image continues to be expected to fail, my observation
of the AB runs is that the full set of ptests is not robust enough
(particularly around socket/network related tests) and sporadically fails
in random places. This can probably be addressed by making ptests exclusive
to a worker (e.g. there is no other workload happening at the same time as
ptests).
(From OE-Core rev: 102afcc7ea7d7673183f272a29ab233084ad168b)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The lists of ptests are defined via PTESTS_FAST and PTESTS_SLOW;
specifying 'ptests-pkgs' also pulls in additional ptests that
are specifically excluded from those lists due to causing issues with
ptesting. (particularly bash-ptest is one such item)
(From OE-Core rev: 1d8e5d1bc1aa8fdaf967395e27b13cc989717fb7)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Particularly, 1G wasn't enough for lttng-tools ptests as
half of that went to /tmp, and lttng-tools needs more.
(From OE-Core rev: abc308a38c6e37afcaf507858a6578c10438c5d8)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemumips doesn't appear to work well with 512MB of RAM and randomly hangs. As
the bump to 512MB was primarily motivated by the memory needs of virtualised GL
which doesn't work in qemumips currently, drop the memory back to 256MB for
qemumips.
(From OE-Core rev: 499a31cf06c934b40b5866d5eb77c9ad20c9a15f)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
256M was found to be no longer sufficient, as the X server fails to
start with the modesetting driver and 3D enabled.
Only images that actually include X11 are adjusted.
(From OE-Core rev: 9dd0812acc73287287b48d28e0935baf7f545b58)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This image continues to run out of space on the autobuilder, tweak it a bit
further now the image space requirements were reduced after various ptest
fixes to avoid the error.
(From OE-Core rev: 9f974dd51c18a1387134a9350097dea97ef5f7d0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding the valgrind debug symbol information caused the genericx86-64 image to
overflow the 4GB boundary. Tweak the sizes to avoid autobuilder failures yet
leave enough space all the tests still run successfully.
(From OE-Core rev: fa24a5056acea6610e2ad1a1eb1e7425a3828979)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since we want to ultimately move this recipe to that name, add a PROVIDES
to allow things to work whilst we fix the bugs preventing the move. This
avoids having to keep changing the autobuilder.
(From OE-Core rev: 2b70ea6ca2c96fb233f42cfe5058cc89c9de5f82)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are recipes not included in core-image-sato-sdk which have ptests, include
these in our ptest test image using the new include file.
(From OE-Core rev: f685ec5740e1a8c3922f8f0631ddaed4b2a5d1f0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Create a common include file which lists recipes that have ptests divided
into 'fast' and 'slow' groups. This allows us to include ptests which otherwise
may not get included in images and allows us to test the faster running things
more regularly.
The new image allows access to these faster executing tests. 'fast' is defined
as tests which execute in under 30s roughly speaking.
(From OE-Core rev: 2d8f8ab85d98929b0f1f699f256b40b1d9cddaec)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some tests such as strace-ptest require more than the current 500MB of free
space. Increase the amount available, staying under the 4GB limit. We have more
flexibility now since we shrank kernel-devsrc and the comments are out of date
due to that.
This should improve the strace-ptest results and the util-linux ones since
those sort after strace and also hit the space issues as strace-ptest didn't
clean up after itself when failing.
(From OE-Core rev: 5c1b2459e2d5651b02bdfdf6cb93b7f9ce32df0a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This image is very large and is skirting the maximum size of hddimg images (4GB,
as they're embedded inside FAT partitions). Making the image 10MB bigger can be
enough to cause the build to fail. This image is also used by QA so currently
we need to keep it working.
The default values for expanding an image to give it usable space are quite
generous, (3GB rootfs * 1.3 gives 1GB of empty space), so change the overhead
multiplier to 1.0x and explicitly request just 0.5GB of empty space in the
images.
This should give us a bit more breathing room until we can either remove hddimg
from the default build, or make this image dramatically smaller.
(From OE-Core rev: 98d9d8958fd5a3bba849e9051bf0310c28b551c2)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
packagegroup-core-x11-sato-games package is being RDEPENDS by
packagegroup-core-x11-sato, hence will be installed if x11-sato is
choosen in IMAGE_FEATURES. So it's unnecessary appending it into
IMAGE_INSTALL.
Even worse, it's causing the following error when x11 is not
in DISTRO_FEATURES:
| ERROR: Required build target 'core-image-sato' has no buildable providers.
| Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-core-x11-sato-games']
(From OE-Core rev: 6c28b122e6214a9e57e4b116ff85145d9ac845ec)
Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SDK (and its tests) need these tools. We happened to be finding them
from the native tools in PATH but recipe specific sysroots prevents that.
This fixes the SDK to work as originally intended and contain these tools.
We have to clear this in the eSDK case since the _append can't be overridden
from the class. Ugly, but we'll have to come back to this issue.
(From OE-Core rev: edde4c52872fbd089f85b10b94db4d6ef1796be5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We added gtk+ to core-image-sato for M1 solely because the SDK self test was
building an application (sudoku) that links to GTK+ 2.
Now that sukoku has been replaced with galculator this workaround can be
removed.
This reverts commit 282d5f7f85.
(From OE-Core rev: aaccc1109fbdda72ffc5b5e66177d00b365d267b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need an image containing the ptest packages for testing purposes.
This adds such an image based on sato-sdk. We did try appending this
in the autobuilder but it creates too much confusion about what is
going on, and increases build time due to lack of parallelisation.
(From OE-Core rev: 0f3ca0b4cae7d17d7b2d53cc433e87e1d148cdfb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Qt4 is no longer supportd upstream, but it is still needed for LSB compliancy.
Qt4 recipes have been moved to a separate meta-qt4 layer to be consistent with
meta-qt3 and meta-qt5.
(From OE-Core rev: cb89d2b25b4edb1241bc5426a69a6bc44df9be2c)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #7230]
In certain system configurations TRANSLATED_TARGET_ARCH will not
expand in the right order for gcc-cross-candian-mips64n32 to be
generated properly.
This will cause SDKs to fail to generate properly.
Changing the global definition of TRANSLATED_TARGET_ARCH always
expands the ABIEXTENSION, which causes the OVERRIDES to pick it up
as well. This effectively defines a new class of overrides for the 'n32'.
The side effect is that we need to duplicate some mips64 overrides, and
redefine others that were previously 'n32' or 'mips64' exclusive to have
the correct semantics.
(From OE-Core rev: 4b3a2b703b20583bd107f00a297d972e9bfb514a)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the move of the kernel source to the kernel-devsrc, we need this package
to ensure the kernel module sanity tests made on core-image-sato-sdk continue
to pass. Therefore update the name of the package included in the image.
(From OE-Core rev: 51c19b97f7282eaba0a6f6b04703a62a3fea2b4a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qt4 doesn't build on mips64 so don't include it in sato-sdk images.
(From OE-Core rev: 900584946698b5bb2c459ad9555709665843be2c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Split out the packages added for Eclipse remote debugging to a separate
package group so that we can avoid pulling them in if not using Eclipse.
Fixes [YOCTO #3251].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently hardware codecs are being injected in rather ugly ways and end up
either in no or all images. This adds a dedicated IMAGE_FEATURE for them based
on the MACHINE_HWCODECS variable. We may need to refine this in due course
but this patch at least illustrates the concept.
(From OE-Core rev: 1cb370587fd72e3f0f69678748108cc4116767fb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This provides one package group, packagegroup-core-apps-console, which
is usually brought in by adding "apps-console-core" to IMAGE_FEATURES.
Aside from the naming inconsistencies, this is a group of mostly
unrelated packages, none of which are actually "apps". Handling each
one:
* dbus: should mostly be brought in by package runtime dependencies
* avahi-daemon: if you are using packagegroup-base (as all images that
inherit from core-image do) this is brought in by having "zeroconf" in
DISTRO_FEATURES.
* portmap: not very useful by itself; should be brought in by selecting
NFS server/client through other means.
* psplash (or whatever SPLASH is set to): this has been changed to be
an explicit item "splash" in IMAGE_FEATURES. Since this is a fairly
fundamental feature, a piece of code has been added to automatically
handle this for images still using apps-console-core (and show a
warning).
(From OE-Core rev: 592d6e602466628d10704835a7b07d3d713f58e1)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now the Sato pieces have been moved out, rebase packagegroup-core-x11 on
packagegroup-x11-mini but using the structure/contents of meta-oe's
task-x11 so that it can replace that; rename packagegroup-core-x11-mini
to packagegroup-core-x11-base and pull in the xserver/utils packages via
packagegroup-core-x11, and move both of these recipes under
recipes-graphics.
x11-mini is renamed to x11-base as it's what people should build on top
of and since x11-mini is newer, the corresponding IMAGE_FEATURES item is
less likely to be used in existing user recipes.
(From OE-Core rev: 0cc9ced7d96b960994b0671095bc74becfc55e2c)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Move Sato applications to packagegroup-core-x11-sato.
Note that this eliminates both the apps-x11-core and apps-x11-games
IMAGE_FEATURES; in practice it is unlikely these were useful to anyone
outside of the Sato images however.
(From OE-Core rev: 46cc375f29d5ecac7311613514a474f288d7c781)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This indirection does not add anything in terms of configuration and
only serves to increase confusion; and given the nature of these it is
unlikely they are being used outside of OE-Core. Change the sato-sdk and
sato-dev images to be based on the main Sato image (avoiding the need
for a common SATO_IMAGE_FEATURES variable) and eliminate all references
to them.
Fixes [YOCTO #2458].
(From OE-Core rev: 6488842b0d03cfec9f8675eca5a2e05675decf66)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable was added in the very same commit that added a mechanism
that makes it obsolete: if you have dropbear and you want openssh, you
just add ssh-server-openssh to your IMAGE_FEATURES and it will replace
dropbear via IMAGE_FEATURES_REPLACES_.
(From OE-Core rev: 6c78d99cc2e54a99af22357d7567f64e864949b9)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replace the usage of EXTRA_IMAGE_FEATURES in a small number of .bb
files with IMAGE_FEATURES, and leave the use of EXTRA_IMAGE_FEATURES
for developers in their local.conf files, to avoid the possibility of
undesirable side effects.
(From OE-Core rev: 347fc6e82a3d1c1ac7dbabd9e5cdd08abd864bfb)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These image recipes are meant to be examples that people can copy and
modify completely for their own purposes, and most of them are so
trivial they don't really need copyright notices anyway, so trim them
off.
(From OE-Core rev: 22db8917f6301595a48f6dcbcccc27627c8a3941)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
IMAGE_FEATURES such as 'ssh-server-dropbear' and 'ssh-server-openssh'
can't be both enabled. User can use the following variables to define
the relationship of image features:
IMAGE_FEATURES_REPLACES_foo = "bar" means including image feature "foo"
would replace the image feature "bar".
IMAGE_FEATURES_CONFLICTS_foo = "bar" means including both image features
"foo" and "bar" would cause an parsing error.
(From OE-Core rev: e36d12a9c1cf69540079e48a1dfadbc343758e48)
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While sdk images already have dev-pkgs included, the kernel-dev package
is special and does not get installed. Add kernel-dev explicitly to the
*sdk image recipes.
Note: We have to be careful with "IMAGE_INSTALL +=" as it must appear
after "inherit core-image" which makes an "IMAGE_INSTALL ?=" assignment.
(From OE-Core rev: 337428316de3612a8e1efa70b3a4ba7cb6e058d2)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Jessica Zhang <jessica.zhang@intel.com>
CC: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #2227]
I've updated the image descriptions per the bug description.
(From OE-Core rev: 479b020edbc609c3ae1e3846e9e0d1643ac10059)
Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add DESCRIPTION to each image bb file according to poky reference manual for Hob2 use later.
(From OE-Core rev: 05a7c022e613f35de8ce47bb667140a7ce47fcea)
Signed-off-by: Shane Wang <shane.wang@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
