summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* license.bbclass: Make incompatible_pkg_license return incompatible licsPeter Kjellerstedt2019-12-161-3/+9
| | | | | | | | | This makes it possible to report the incompatible licenses. (From OE-Core rev: 02a3189b4902e616f5b4277ee3d0fca10b73b4dc) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licenses.conf: Remove the SRC_DISTRIBUTE_LICENSES variablePeter Kjellerstedt2019-12-161-43/+0
| | | | | | | | | | | The SRC_DISTRIBUTE_LICENSES variable and its static list of licenses has been replaced by AVAILABLE_LICENSES, which automatically contains all available licenses. (From OE-Core rev: 64daaf29e2c12c8b587bafdebf9409433187ddf7) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* license.bbclass: Introduce AVAILABLE_LICENSES that lists all licensesPeter Kjellerstedt2019-12-163-7/+27
| | | | | | | | | | | | | | | | | | | | | | Previously, there was SRC_DISTRIBUTE_LICENSES, an undocumented variable that contained a static list of licenses. It was used by expand_wildcard_licenses() to expand any wildcards used in, e.g., INCOMPATIBLE_LICENSE. However, since this static list of licenses has not been kept up-to-date, many licenses were missing, with the result that if one tried to use any of those licenses with a wildcard, no licenses would be found, effectively ignoring that they should be marked as incompatible. This introduces a new (documented) variable, AVAILABLE_LICENSES, that is automatically updated to contain all licenses found in any directories specified by ${COMMON_LICENSE_DIR} and ${LICENSE_PATH}, and uses it instead of SRC_DISTRIBUTE_LICENSES when expanding wildcards. (From OE-Core rev: 8c9ef587fe499c612a878a1ab42092eb79b334ef) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa.inc: allow the user to choose the build typeTrevor Woerner2019-12-161-0/+13
| | | | | | | | | | | | | Upstream mesa can either be built as a debug release (the default) or a production release. This patch allows the user to choose which one they want by setting MESA_BUILD_TYPE to either 'production' or 'debug' as they see fit. Under OpenEmbedded a production build will be performed by default. (From OE-Core rev: 6a6b775d69aa59102e1f6a68c88276be6d54a8e6) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson.bbclass: allow buildtype to be changedTrevor Woerner2019-12-161-1/+2
| | | | | | | | | | | Some upstream projects are employing the buildtype parameter so users can create, say, "production" versus "debug" builds. Therefore create a configurable parameter so recipes/users can tweak it. (From OE-Core rev: 5b12211ef7856bedafd356f6b7a03add46eca6c7) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: 3.15.5 -> 3.16.1Pascal Bach2019-12-167-13/+13
| | | | | | | | | Patches have been refreshed and all of meta-oe and oe-core was sucessfully built. (From OE-Core rev: 469bcfbfe25afd9c480c26f117b81d65cc305fbe) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: upgrade 8.6.9 -> 8.6.10Yi Zhao2019-12-164-11/+58
| | | | | | | | | | | | | | | | Refresh patches: alter-includedir.patch tcl-remove-hardcoded-install-path.patch Backport a patch to fix tk build failure with cross compile: 0001-Fix-abd4abedd2-Failed-to-build-tk-8.6.10-with-cross-.patch See: https://core.tcl-lang.org/tk/tktview/abd4abedd2f01c12839f0ad94564ae31137f7af5 (From OE-Core rev: f7226d8b28d7ee9292c53c8830c86c0619910f23) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: fix CVE-2019-1551Anuj Mittal2019-12-162-0/+759
| | | | | | | (From OE-Core rev: 7a8165e0d833bc64c824fa2aee2ddad21d866675) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysstat: fix CVE-2019-19725Anuj Mittal2019-12-162-0/+29
| | | | | | | (From OE-Core rev: 2bf6fdc460526feb0955b3b789e7be78f6e8ec4a) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/apt dnf opkg: support running from within docker containerAndré Draszik2019-12-163-3/+8
| | | | | | | | | | | | | | | | | If the user specified an http port to use for serving files, use that instead of a random one. At the same time, have the http server bind to all interfaces. Binding to the server_ip might not always be possible, e.g. in the case of running bitbake / oeqa from within a docker container. In this case, the ip address is valid outside the container, but not inside, and hence can't be bound to. So switch to simply binding to all interfaces. (From OE-Core rev: da529e6522959c2024023e90de52b5e42f160596) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/target/ssh oeqa/target/qemu: expose server listening port to testsAndré Draszik2019-12-162-1/+3
| | | | | | | | | | | | | Allow tests to access the listening port as just introduced. Note that when using qemu this infrastructure shouldn't be needed, but we still need to set the port to 0 so that a listening port is determined automatically (e.g. by the python http server). (From OE-Core rev: ca58559fc30842c123907fb5cc68b3356c530862) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/context.py: support listening port in TEST_SERVER_IPAndré Draszik2019-12-161-0/+6
| | | | | | | | | | | | | | | | | Similar to the existing possibility to specify a port in TEST_TARGET_IP, allow TEST_SERVER_IP to also contain a port. The intention is for this port to be passed into e.g. the http server from the apt / dnf / opkg tests, or any other (custom) tests that might need the target to connect to a service spawned by bitbake / oeqa, where bitbake is actually running inside a docker container. (From OE-Core rev: 9f401cd8b010ca613a151d0323b251f2243f399f) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/httpserver: allow to pass in listening portAndré Draszik2019-12-161-2/+2
| | | | | | | | | | | | | | | | Being able to specify the listening port is useful when running OEQA from within a docker container, e.g. crops or any other solution. In that case, a port on the outside must be mapped to a specific port inside the container. If no port is specified for the http server module in this case, the http server would choose a random port, which is unlikely to be mapped and thus won't be reachable from the outside. (From OE-Core rev: e54391ca9068661693275fbfcfded9bc0b2606f3) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: update kernel module RRECOMMENDS for kernel >= v4.19André Draszik2019-12-161-1/+1
| | | | | | | | | | | | | | | | nf_tables_inet.ko and nf_tables_ipv4.ko and nf_tables_ipv6.o (and nf_tables_arp.ko and nf_tables_netdev.ko) were merged into the core nf_tables.ko before v4.17 in kernel commit 02c7b25e5f54 netfilter: nf_tables: build-in filter chain type nf_meta.ko was merged to be a builtin of nf_tables.ko before v4.18 in kernel commit 8a22543c8e70 netfilter: nf_tables: make meta expression builtin (From OE-Core rev: 98715c9dc8dd925cffce9bd5d57172206d1e2a7b) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: split dumpe2fs into its own packageAndré Draszik2019-12-162-4/+5
| | | | | | | | | | | | | | | | | | | This is a mere 24KB (on 32bit arm), avoiding to pull in all of the remainder +300KB in small initramfs images when not needed. Add this new package to RDEPENDS of e2fsprogs so as to not break existing users. Also, remove a stale reference to the non-existent e2fsprogs-fsck package which was removed in 2012 from here in commit 98b1b9f047ef ("e2fsprogs: Drop fsck binary"), commit 93d647172786 in poky, and sort some of the lists alphabetically. (From OE-Core rev: 19dd3453da39066564d899d561e4814822dcbd18) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-systemctl: Fix handling of aliased targetsSlavic Brutalik2019-12-161-1/+1
| | | | | | | | | | | | | The script scans for services, parses them and makes sure those targets are still there. The exists file check fails if the target is an alias, such as default.target so add an additional test. [YOCTO #13685] (From OE-Core rev: 10bdbf033e51c97f6408c9114d480372135a2c2e) Signed-off-by: Werner Grift <sky.captin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: fix NULL pointer deference error when testing rpc_task_runningQuanyang Wang2019-12-165-0/+377
| | | | | | | | | | This is a backport from upstream https://github.com/lttng/lttng-modules.git stable-2.10 to fix NULL pointer deference error when running kts testcase lttng_syscall_events. (From OE-Core rev: a522ccff838ba1577255c90e64d98dd75470fb0a) Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: upgrade 2.24.0 -> 2.24.1Anuj Mittal2019-12-162-11/+11
| | | | | | | | | | Fixes a bunch of CVEs: https://github.com/git/git/commit/53a06cf39b756eddfe4a2a34da93e3d04eb7b728 (From OE-Core rev: 8be3c48a418776c8480dbae2dcb5f46c8fb138ed) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: update to 1.8.29Alexander Kanavin2019-12-164-305/+13
| | | | | | | | License-Update: added SPDX info. (From OE-Core rev: d3660148a64fc6ef18c7f9d2080c26d89c0b3826) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpio: update to 2.13Alexander Kanavin2019-12-165-401/+2
| | | | | | | | | Drop a couple of backports. (From OE-Core rev: 66f3b09364c499d9b0610f7c01763ae5dc1521cf) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man-db: update to 2.9.0Alexander Kanavin2019-12-161-2/+2
| | | | | | | (From OE-Core rev: dd0c62ba4c1ade7aaa4760f351cf9f76c0aca91e) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man-pages: update to 5.04Alexander Kanavin2019-12-161-2/+2
| | | | | | | (From OE-Core rev: 6451a900ce184e7d78785dbdfced9c7812e33374) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parted: update 3.2->3.3Alexander Kanavin2019-12-1612-737/+117
| | | | | | | | | | | | | | | | | 0001-Unset-need_charset_alias-when-building-for-musl.patch is no longer necessary as upstream has removed the code. dm_check.patch is replaced with 0002-tests-use-skip_-rather-than-skip_test_-which-is-unde.patch Rework ptests, in particular remove the generated Makefile from the layer, and use the upstream Makefile. Ptest pass rate is 100%. (From OE-Core rev: 5dc6529d0b5b8b1bef12b90008f0a25612bd453e) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: update to 2.9.10Alexander Kanavin2019-12-162-32/+34
| | | | | | | (From OE-Core rev: de72e0440bc36fab09a7e3c13d3967c97dcda66b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glide: update to 0.13.3Alexander Kanavin2019-12-161-1/+1
| | | | | | | (From OE-Core rev: 0270b64a69f30d36f03ce8de819fa703da84ecbb) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* puzzles: update to latest revisionAlexander Kanavin2019-12-165-84/+35
| | | | | | | | | Remove 0001-Use-labs-instead-of-abs.patch as problem is fixed upstream. (From OE-Core rev: 6ecc17f83d57d08bbeb6366cb586993a8844c8a6) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dos2unix: update to 7.4.1Alexander Kanavin2019-12-161-3/+2
| | | | | | | | License-Update: copyright years (From OE-Core rev: 248e777ac61e90da061e336acbcd23e8e71cd0e4) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Further optimiseRichard Purdie2019-12-161-3/+2
| | | | | | | | Optimise the call into the parent function to be only when needed. (From OE-Core rev: 198bacaa1068fd68075d9182318fe64e9809dd36) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-build-perf-test: Use python3 from the environmentRichard Purdie2019-12-151-1/+1
| | | | | | | | | On test machines we have python3 available at alternative locations. Use these rather from the evnrionment rather than a hardcoded path. (From OE-Core rev: 81ee68f39a155c79443d45321ce4b81d9bf6675e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Optimise get_taskhash for hashequivRichard Purdie2019-12-151-2/+11
| | | | | | | | | | | With hashequiv the get_taskhash function is called much more regularly and contains expensive operations. This these don't change based upon hash in a given build, improve the caching within the function to reduce overhead. (From OE-Core rev: de98cfe3cde4b8d5f4b163b5fba3f129651ef06a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/x86-base: use wic instead of liveRoss Burton2019-12-151-1/+1
| | | | | | | | | | Use wic instead of the live/hddimg filesystem type for x86 machines, as it produces better filesystems and doesn't have a hard limit of 4GB. (From OE-Core rev: 04e4e93efa4d8e2bdde950fe95c2fd95f89c13e7) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats: Replace 'is' with '==' in python condition check expressionKhem Raj2019-12-151-1/+1
| | | | | | | | | | | | | | | python 3.8 has started to throw this as a warning but usage is wrong see [1], it seems to be working by accident and not design. Fixes SyntaxWarning: "is" with a literal. Did you mean "=="? [1]: https://bugs.python.org/issue34850 (From OE-Core rev: c3cb6bc21f3f84e2ed103b6438516ab85222faa9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjpeg-turbo: Build reproduciblyJoshua Watt2019-12-151-0/+2
| | | | | | | | | | Configures the options passed to nasm to remove build paths in the generated object files. (From OE-Core rev: 9119a882adbf19df9f47f66cebaa7f730d3e9462) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: Add debug-prefix-map optionJoshua Watt2019-12-153-0/+444
| | | | | | | | | | | Adds an option to nasm to change the prefix for file paths encoded in the object files. This allows builds to be reproducible regardless of the build directory. (From OE-Core rev: ad5c914933c7b38296dcb8bba3c36aed45aacc32) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "go: Reset unneeded GOARCH variables for native recipe"Khem Raj2019-12-151-10/+0
| | | | | | | | | This reverts commit 4825eede606b075d0d529b38d6162999f1dec506. (From OE-Core rev: 18b90967bd367263280ec871be84e67e3eed11fa) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* goarch: Remove target specific dependenciesKhem Raj2019-12-151-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | goarch is used in all classes of recipes ranging from native to target, therefore its best to contain the variables and not spill over into recipe classes where they can adversely affect shared state reuse e.g. go-native currently gets TUNE_FEATURES into dependency chain of referenced variables which means go-native gets rebuilt when we change from qemuarm to qemux86 machine types since TUNE_FEATURES is defined with DEFAULTTUNE which would change as machines are switched These variables are specific to arm/mips/x86 so marking them with appropriate overrides for native recipes will be right thing here Chose 'hardfloat' for mips which is default too, 7 for arm and sse2 for x86 somehow go-native bootstrap compiler (1.4) still needs them so feed commonly used values or defaults. Fixes ERROR: go-native different signature for task do_configure.sigdata between qemux86copy and qemuarm ... List of dependencies for variable TUNE_FEATURES changed from '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-core2-32'}' to '{'DEFAULTTUNE', 'TUNE_FEATURES_tune-armv7vethf-neon'}' changed items: {'TUNE_FEATURES_tune-core2-32', 'TUNE_FEATURES_tune-armv7vethf-neon'} (From OE-Core rev: 83eebf5577dd0a23be937375c1a8a15e3da4fa64) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cronie:fix SRC_URI pathStefano Babic2019-12-151-1/+1
| | | | | | | (From OE-Core rev: 06ce57157a43f5988e1a0c6bc147fec7b55e63ec) Signed-off-by: Stefano Babic <sbabic@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: disable debug output in ptestsAlexander Kanavin2019-12-151-1/+1
| | | | | | | | | | This makes the log very large and breaks the ptest result parser. (From OE-Core rev: 78221af4c0297e0278c042eed390ad0e53f2548a) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez: update 5.50 -> 5.52Alexander Kanavin2019-12-159-982/+16
| | | | | | | | | | | | | Drop a big pile of backports. Disable zsh completions, as they're unlikely to be useful. (From OE-Core rev: dad8cd50bcc4203a65d153dc2445502c1e728975) (From OE-Core rev: 1a31a31a3bd68f027ba0a13f8e66ce92104a4d4c) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: avoid vlock conflict with busyboxHongxu Jia2019-12-151-1/+2
| | | | | | | | | | | | | | | | | | | | | | busybox as well as vlock utility from meta-oe provides vlock utility which can conflict when with kbd if pam is a enabled distro_feature Fixes image build errors update-alternatives: Error: not linking <rootfs>/usr/bin/vlock to /bin/busybox.suid since <rootfs>/usr/bin/vlock exists and is not a link ERROR: yoe-qt5-wayland-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. (From OE-Core rev: 08636708f6ca677a6ee6c88fa2999c7b70b7d474) Signed-off-by: Khem Raj <raj.khem@gmail.com> The vlock doesn't exist if PAM isn't enabled. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* reproducible_build_simple: inherit podfixRoss Burton2019-12-151-0/+1
| | | | | | | | | | When doing reproducible builds inherit podfix to remove the possibility of differing Perl versions causing manpages to change. (From OE-Core rev: 5dc43edab4787906f2c9f51e51bf78d1dc966286) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* podfix: class to remove Pod::Man versions from manpagesRoss Burton2019-12-151-0/+32
| | | | | | | | | | | | | | Manpages generated by Pod::Man contain the version number, which isn't reproducible if we're using the host Perl to generate manpage. One option is to always depend on perl-native when generating manpages but this is a heavy dependency, so instead strip out the versions in do_install(). (From OE-Core rev: 18d8e5ac689d6eb6098f68ac785f43e9d5f5938a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: handle tap device creation failure properlyPaul Eggleton2019-12-151-2/+6
| | | | | | | | | | | | If we fail to run the command to generate the tap devices then we should show a reasonable message and then exit, without showing a traceback. "return 1" at this point in the code does nothing because the caller doesn't check the return, so just use sys.exit(). (From OE-Core rev: 47e40fdd7dd58bde4e017e2375c16450fcb14eca) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: log parameters correctly within testimagePaul Eggleton2019-12-151-12/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is not a good idea to mix logging and calls to print() - if the output is being captured the result can be that the two types of output are not recorded contiguously; this could be observed if an error occurred running runqemu from inside testimage: ---------- snip ---------- ERROR: core-image-minimal-1.0-r0 do_testimage: Output from runqemu: runqemu - INFO - Continuing with the following parameters: runqemu - INFO - Setting up tap interface under sudo sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper runqemu - ERROR - Setting up tap device failed: Command '('sudo', '/home/paul/poky/poky/scripts/runqemu-ifup', '1000', '1000', '/home/paul/poky/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin')' returned non-zero exit status 1. Run runqemu-gen-tapdevs to manually create one. runqemu - INFO - Cleaning up KERNEL: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/bzImage--5.2.20+git0+bd0762cd13_dd25a04fc5-r0-qemux86-64-20191205213021.bin] MACHINE: [qemux86-64] FSTYPE: [ext4] ROOTFS: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4] CONFFILE: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf] ---------- snip ---------- What we should see here is the KERNEL, MACHINE, etc. lines appearing immediately after the "Continuing with the following parameters:" line as they do when you run runqemu directly. If we put all of the lines through the logger instead then it works properly. (From OE-Core rev: ca64a3d490fbe1bf87c9f1dd6d87a1ecdeba8325) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure we print runqemu output in the event of failurePaul Eggleton2019-12-151-2/+2
| | | | | | | | | | | | If we get here in the code it's because runqemu has failed, this is not a debug situation - we need to see the output, so print it as an error. Fixes [YOCTO #13681]. (From OE-Core rev: c1def38c680d64c992839166bbf9bec51eb0788a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: fix width of top output in host dumpPaul Eggleton2019-12-151-0/+1
| | | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). One of those commands is "top -bn1", however top restricts the output to the width of the calling terminal, and for whatever reason this is a little restrictive when called from inside testimage, so set COLUMNS in the environment to a high value to fix it. (Another way is to use the -w option, but that is not supported by our default busybox configuration so it will then fail when this same list of commands is used on the target). (From OE-Core rev: 07da998f5aa6c3f5ffeee5150fc579e8a1051ba4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: qemu: ensure that host dump commands can be run properlyPaul Eggleton2019-12-151-1/+3
| | | | | | | | | | | | | | | | | If runqemu fails, there is some logic to run a set of commands to dump various bits of information that might help debug the issue (particularly in a busy situation such as on the autobuilder). However, when we try to run these we are inside the normal build environment which restricts commands to be run on the host to those specified in HOSTTOOLS. Since this isn't a place where host contamination is going to be a problem, override PATH to a reasonable default so that we run the actual host tools directly to avoid the issue. (Logically we would want to use the original PATH value here, but it is not easily accessible.) (From OE-Core rev: 3f6dcf67bccb4f0fc1a9a64e02bd0e2da620ad0e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/systemd_boot: Ensure wic-tools are availableRichard Purdie2019-12-151-3/+5
| | | | | | | | | | If mtools isn't present on the underlying system this test would fail. Ensure wic-tools is available in a similar way to other wic selftests in OE-Core. (From meta-yocto rev: 5d48d41a3f93ca0e7085ce3c0f646b1d0c8d52d1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/systemd-boot: test against wic imageChee Yang Lee2019-12-151-5/+4
| | | | | | | | | | | | effort to remove live for x86 from default image see https://bugzilla.yoctoproject.org/show_bug.cgi?id=11291 reduce dependency on hddimg, change the test to based on wic image. (From meta-yocto rev: 8cce1493f625664c21c156a36d9c9fb6d4dd4b1f) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* genericx86: wic wks do not hardcode loaderChee Yang Lee2019-12-152-2/+3
| | | | | | | | | | | replace .wks with .wks.in and refer loader to EFI_PROVIDER to enable different bootloader. soft assign default EFI_PROVIDER "grub-efi" for genericx86. (From meta-yocto rev: 11ecd2febed95e923c8cc68e2c438cd846a88d02) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-09 19:12:15 +0000