summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* xf86-input-libinput: upgrade 0.28.1 -> 0.28.2Richard Purdie2019-02-251-2/+2
| | | | | | (From OE-Core rev: c90e9b95325d2d2645752776fcc7d7f78d6afc88) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* readline: upgrade 7.0 -> 8.0Richard Purdie2019-02-254-7/+7
| | | | | | (From OE-Core rev: 59062ff94f9b3fe0ce22a497e90a2224554506ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pkgconf: upgrade 1.5.3 -> 1.6.0Richard Purdie2019-02-251-2/+2
| | | | | | (From OE-Core rev: ab4b0aed95abc4facc63a817b05fbd423ab67a5b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* netbase: upgrade 5.5 -> 5.6Richard Purdie2019-02-252-10/+8
| | | | | | (From OE-Core rev: 2d52ca3beacfd7a91581afa3fb02481f292869e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxau: upgrade 1.0.8 -> 1.0.9Richard Purdie2019-02-251-2/+2
| | | | | | (From OE-Core rev: 5624657ac127f1adfd867d04c5a361e74e2d31d9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libassuan: upgrade 2.5.2 -> 2.5.3Richard Purdie2019-02-251-2/+2
| | | | | | (From OE-Core rev: 0da1ae8322763c0b75e977ff40275fa4220140d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* less: upgrade 530 -> 549Richard Purdie2019-02-251-3/+4
| | | | | | | | The license checksum changed due to a change in copyright years. (From OE-Core rev: ee3057bf109b2d11ecb0089c2c424e9b6033932e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-examples: upgrade to latest revisionRichard Purdie2019-02-251-1/+1
| | | | | | (From OE-Core rev: 8c428ead6baeafbd583c864d610ec7ef048d0fa2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnupg: upgrade 2.2.12 -> 2.2.13Richard Purdie2019-02-253-4/+4
| | | | | | (From OE-Core rev: c675a07fd820e47d2a13211cdc6496a09ddb5b3b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: upgrade 7.63.0 -> 7.64.0Richard Purdie2019-02-251-3/+3
| | | | | | | | | | | | | The license checksum changed as the copyright years changed. Fixes: - CVE-2018-16890: NTLM type-2 out-of-bounds buffer read - CVE-2019-3822: NTLMv2 type-3 header stack buffer overflow - CVE-2019-3823: SMTP end-of-response out-of-bounds read (From OE-Core rev: 41c3ee4fe87a181786c47da044da700e8f605540) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Add opengl to native and nativesdk PACKAGECONFIGFabio Berton2019-02-251-2/+2
| | | | | | | | | | | Allow the use of opengl for native and nativesdk packages. Based on https://patchwork.openembedded.org/patch/158748/ (From OE-Core rev: 4a94dc8daab8890aaff36ffafdfe2feaa52902d4) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Replace dri-native with dri for native and nativesdk classesFabio Berton2019-02-251-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using a native specific packageconfig option, we now set the swrast as the supported driver. Currently the native version does not build any dri drivers at all. This is intentional: mesa-native is used only by virgl, so was made the most minimal possible configuration for mesa-native so that a) virgl works; and b) build time is as short as possible. There are two swrast drivers, one dri-based, another gallium-based. Autotools lets you build both, meson forces you to choose. Thus DRIDRIVERS = "swrast" is only set for _native, as for _target we get the gallium driver instead. See discussion here [1] Based on https://patchwork.openembedded.org/patch/158748/ [1] https://patchwork.openembedded.org/patch/158806/ (From OE-Core rev: 223ee432b908180932bf70e77d4058964d7f0786) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Update 18.1.9 -> 18.3.4Fabio Berton2019-02-2510-115/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Refresh all patches. - Remove "Use Python 3 to execute the scripts" patch Commit 986033a2750c1160a4cef3c8418fc7f9e2b4fb5a add support for both python 2 and 3. - Remove "dri: i965: Add missing time.h include" patch Commit 3c288da5eec81ee58b85927df18d9194ead8f5c2 add time.h header file. - Remove --enable-texture-float. Commit 66673bef941af344314fe9c91cad8cd330b245eb remove option to unconditionally enable floating-point textures. - Commit 30b10dbb7c6f6bdf3e489620f8333c727bd3a6dd moved ${sysconfdir}/drirc to ${datadir}/drirc.d/00-mesa-defaults.conf Add 00-mesa-defaults.conf to mesa-megadriver package - Stop removing ${sysconfdir}/drirc on do_install_append - Fix upgrade path from mesa to mesa-megadriver - Add patch to fix mesa-native build - Add xrandr to X11_DEPS (From OE-Core rev: 9ddd6add68f07fb7b3f264cee7c853ffe4a1b43e) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: fix incorrect symbolic link for libperl.soYi Zhao2019-02-251-1/+3
| | | | | | | | | | | | | The perl-cross uses PERL_API_VERSION but not PERL_VERSION to define libperl soname: libperl.so.$PERL_API_REVISION.$PERL_API_VERSION.$PERL_API_SUBVERSION. For perl stable releases, the PERL_API_SUBVERSION is always 0. Specify the so version for libperl to make sure the libperl.so can be linked to the correct library. (From OE-Core rev: 6257fcd86e63fe533aeaadbc65a54213b4885c16) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Fix staging_populate_sysroot_dir native corruptionRichard Purdie2019-02-251-0/+4
| | | | | | | | | | | | | | | | bitbake gdk-pixbuf gdk-pixbuf-native bitbake build-sysroots -c build_target_sysroot can lead to tracebacks as gdk-pixbuf-native is being installed into the target sysroot. The issue is that the x86_64 (common BUILD_ARCH) sysroot components directory can contain a mix of native and target artefacts. Differentiate by the "-native" in the recipe names. Should also trim down the size of the sysroot used in eSDK. (From OE-Core rev: 57f32836060bba0eaa6b36f53146dd6fd07b77ed) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext.bbclass: Fix the derivate sdk build error from an published ↵Manjukumar Matha2019-02-251-5/+4
| | | | | | | | | | | | | | | | | | | | | | | | eSDK When you install the eSDK in publish mode and then try to build a derivative sdk using devtool build-sdk, the following error happens | NOTE: Generating sstate task list... | NOTE: Generating sstate-cache... | NOTE: Generating sstate-cache... | DEBUG: Python function copy_buildsystem finished | NOTE: Executing install_tools ... | DEBUG: Executing shell function install_tools | install: cannot stat /core/meta/files/ext-sdk-prepare.py': No such file or directory This patch will fix the error by installing ext-sdk-prepare.py in publish mode, so that derivative sdk can be generated. (From OE-Core rev: aab4089a57a655ca5a7792f05eb5d8dcdb934ae1) Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: Upgrade to 2019.01 releaseMarek Vasut2019-02-254-1/+1
| | | | | | | | | | | | This upgrades the U-Boot to latest 2019.01 release. (From OE-Core rev: fc5895a41f1e903d86f726821dadfeeba4145585) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Otavio Salvador <otavio@ossystems.com.br> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devicetree.bbclass: Add virtual provider for dtbManjukumar Matha2019-02-251-0/+2
| | | | | | | | | | | | | | | Add virtual provider for dtb. This class can be used to generate dtb from static devicetree, for reference see meta-xilinx layer meta-xilinx/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb By providing a virtual provider we can use it to differentiate between in-kernel dtb or an external one. This can be set in local.conf as PREFERRED_PROVIDER_virtual/dtb = "devicetree" (From OE-Core rev: a7d52dbffd0da95de82d910c595a6c27d9b2ad0d) Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mdadm: add init and service scriptsZheng Ruoqin2019-02-253-1/+106
| | | | | | | | | | Add init script and service file for sysvinit and systemd. (From OE-Core rev: a6222a41c54fb9feebb980e57bcc8a572f93acd1) Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lighttpd: Use the upstream lighttpd.serviceAdrian Bunk2019-02-253-18/+5
| | | | | | | | | | | | We shipped an old version that was missing several fixes. A minor incompatibility is that this moves /etc/lighttpd.conf -> /etc/lighttpd/lighttpd.conf (From OE-Core rev: bd46eeee09e99ae4646a92f5bf5bc3c619e63cde) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: enable CONFIG_FLOAT_DURATIONAdrian Bunk2019-02-251-1/+1
| | | | | | | | | | | The 1.29.3 -> 1.30.1 upgrade lost support for sleep with float values (e.g. "sleep 0.1") since this replacement for CONFIG_FEATURE_FLOAT_SLEEP (enabled in thud) was missing. (From OE-Core rev: 3f6021e8b444e9b8f7aae0c564bef1d3c9634198) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-tools: use a better SRC_URITanu Kaskinen2019-02-251-1/+1
| | | | | | | | | The ftp server has been flaky recently. (From OE-Core rev: 9257ba3cdadc0721fad7d57a5fd75e7cd45fd53c) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-utils: 1.1.6 -> 1.1.8Tanu Kaskinen2019-02-252-8/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelogs: http://alsa-project.org/main/index.php/Changes_v1.1.6_v1.1.7 http://alsa-project.org/main/index.php/Changes_v1.1.7_v1.1.8 There's a new program, axfer, which is a reimplementation of aplay (and arecord). The purpose of the rewrite is to have code that is easier to maintain. For now both implementations exist, and I decided to put both in the aplay package. The new 89-alsa-ucm.rules udev file initializes the mixer settings for certain hardware. It's needed for making the hardware usable at boot, in case there's no higher level software (such as PulseAudio) managing the mixer settings. Shipping hardware specific configuration in alsa-utils seems wrong, but I don't know what else to do. I added it to the alsaucm package, because it's kind of tied to the alsaucm utility (the udev rules execute the alsaucm program, and the build system installs the rules file only when alsaucm is enabled). Ideally the UCM configuration in alsa-lib would define the default UCM verb for each hardware, then the udev rules file could just enable the default verb, and there would be no hardware specific configuration in alsa-utils. But that requires upstream development effort. SRC_URI was changed to a more reliable source (at least currently the ftp server is flaky). (From OE-Core rev: f78e2fc921093cdd279f4245760b5e0a7adbe85c) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-plugins: 1.1.6 -> 1.1.8Tanu Kaskinen2019-02-252-16/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelogs: http://alsa-project.org/main/index.php/Changes_v1.1.6_v1.1.7 http://alsa-project.org/main/index.php/Changes_v1.1.7_v1.1.8 The --enable-avcodec configure option was renamed to --enable-libav, and I renamed the respective packageconfig item too. There's a new pcm plugin: aaf (AVTP Audio Format). I added a packageconfig item for it, but I didn't test it, because libavtp doesn't seem to be currently packaged for OpenEmbedded. There are now configuration files for most of the plugins. I removed the symlink creation for 50-pulseaudio.conf, because upstream now creates the symlinks for us. 99-pulseaudio-default.conf is an exception, because upstream ships it only as an example, and upstream doesn't install a symlink for it (upstream actually installs it directly under /etc, but I moved it back to /usr/share), so for that file we still have to create the symlink ourselves. The lavcrate plugin was converted to use libavresample (and renamed to lavrate). Libavresample is provided by ffmpeg, but ffmpeg was by default built with libavresample disabled. This patch now enables libavresample by default in the ffmpeg recipe in order to not cause a regression in alsa-plugins. SRC_URI was changed to a more reliable source (at least currently the ftp server is flaky). (From OE-Core rev: ddf5421331180bc45697511b44cdd4a4e6dda6ff) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-lib: 1.1.6 -> 1.1.8Tanu Kaskinen2019-02-252-4/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelogs: http://alsa-project.org/main/index.php/Changes_v1.1.6_v1.1.7 http://alsa-project.org/main/index.php/Changes_v1.1.7_v1.1.8 One significant change was that the search path of add-on configuration files was changed from /usr/share/alsa/alsa.conf.d to /etc/alsa/conf.d. Packages that install such files should still use the /usr/share location, though. Symlinks need to be created from /etc to /usr/share. The rationale for using /etc is that the system administrator can better control the configuration that way, and the rationale for installing files under /usr/share is that configuration snippets that are installed by packages are not meant to be directly edited by the administrator. alsa-plugins had to be modified to add symlinks for the configuration snippets that it installs. I also added FILES_${PN} = "", because the alsa-plugins package is supposed to be empty, but also because for some reason that I don't understand the symlinks would otherwise go to the alsa-plugins package rather than alsa-plugins-pulseaudio-conf. SRC_URI was changed to a more reliable source (at least currently the ftp server is flaky). (From OE-Core rev: 91f506958e4b7e9b8e8f1dcfe4a8aa4bdac7c5d1) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sbc: upgrade 1.3 -> 1.4Richard Purdie2019-02-251-2/+2
| | | | | | (From OE-Core rev: a96b52a825cc0de2ffbdef0e1fb2f52d4d384994) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* resulttool/resultutils: Avoids tracebacks for missing logsRichard Purdie2019-02-251-1/+2
| | | | | | (From OE-Core rev: ec020699086cc56bfa37bab38065472da52b3d0f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fix CVE-2019-6454George McCollister2019-02-253-0/+273
| | | | | | | | | | | | | | | Apply patches from systemd_239-7ubuntu10.8 to fix CVE-2019-6454. CVE-2019-6454 is an issue in which systemd (PID1) can be crashed with a specially formed D-Bus message. For information see: https://usn.ubuntu.com/3891-1/ https://git.launchpad.net/ubuntu/+source/systemd/commit/?id=f8e75d5634904c8e672658856508c3a02f349adb (From OE-Core rev: 9d2ec5970adfc906fcc4581528321a879953fd55) Signed-off-by: George McCollister <george.mccollister@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: Ensure an initramfs is added if configuredRichard Purdie2019-02-251-1/+3
| | | | | | | | | | | | | | | | | | | | | | If ${DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE_NAME}.cpio does not exist, nor any of the compressed variants, nothing is copied to kernel build's ./usr directory. The code does not fail, but silently proceeds without a bundled initramfs. Change to fail and tell the user something is wrong. Also, if an initramfs is found, contrary to the comments, it does not stop at the first uncompressed/compressed cpio image found. Instead it keeps processing all so the last is used. Fix this to behave as per the comments. [YOCTO #12909] (Patch by Leon Woestenberg) (From OE-Core rev: 5b5604e288af755eb5553a97d26533445b2cf94b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/gitarchive: Handle case where parent is only on originRichard Purdie2019-02-251-2/+2
| | | | | | | | | | | | | | | The parent code currently assumed that any parent branch is locally checked out which may not be the case. Use the local branch by default but fall back to the origin. This also means removing the later saftey check as the branch may not exist locally. This fixes the autobuilder resulttool test pushing code. (From OE-Core rev: 0ee636bc89d93282cb3d3cd747b3dd046f6e5a9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* resulttool: Improvements to allow integration to the autobuilderRichard Purdie2019-02-2110-508/+530
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a combined patch of the various tweaks and improvements I made to resulttool: * Avoid subprocess.run() as its a python 3.6 feature and we have autobuilder workers with 3.5. * Avoid python keywords as variable names * Simplify dict accesses using .get() * Rename resultsutils -> resultutils to match the resultstool -> resulttool rename * Formalised the handling of "file_name" to "TESTSERIES" which the code will now add into the json configuration data if its not present, based on the directory name. * When we don't have failed test cases, print something saying so instead of an empty table * Tweak the table headers in the report to be more readable (reference "Test Series" instead if file_id and ID instead of results_id) * Improve/simplify the max string length handling * Merge the counts and percentage data into one table in the report since printing two reports of the same data confuses the user * Removed the confusing header in the regression report * Show matches, then regressions, then unmatched runs in the regression report, also remove chatting unneeded output * Try harder to "pair" up matching configurations to reduce noise in the regressions report * Abstracted the "mapping" table concept used to pairing in the regression code to general code in resultutils * Created multiple mappings for results analysis, results storage and 'flattening' results data in a merge * Simplify the merge command to take a source and a destination, letting the destination be a directory or a file, removing the need for an output directory parameter * Add the 'IMAGE_PKGTYPE' and 'DISTRO' config options to the regression mappings * Have the store command place the testresults files in a layout from the mapping, making commits into the git repo for results storage more useful for simple comparison purposes * Set the oe-git-archive tag format appropriately for oeqa results storage (and simplify the commit messages closer to their defaults) * Fix oe-git-archive to use the commit/branch data from the results file * Cleaned up the command option help to match other changes * Follow the model of git branch/tag processing used by oe-build-perf-report and use that to read the data using git show to avoid branch change * Add ptest summary to the report command * Update the tests to match the above changes (From OE-Core rev: ff2c029b568f70aa9960dde04ddd207829812ea0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/resulttool: enable manual execution and result creationMazliana2019-02-212-0/+145
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Integrated “manualexecution” operation to resulttool scripts. Manual execution script is a helper script to execute all manual test cases in baseline command, which consists of user guideline steps and the expected results. The last step will ask user to provide their input to execute result. The input options are passed/failed/blocked/skipped status. The result given will be written in testresults.json including log error from the user input and configuration if there is any.The output test result for json file is created by using OEQA library. The configuration part is manually key-in by the user. The system allow user to specify how many configuration they want to add and they need to define the required configuration name and value pair. In QA perspective, "configuration" means the test environments and parameters used during QA setup before testing can be carry out. Example of configurations: image used for boot up, host machine distro used, poky configurations, etc. The purpose of adding the configuration is to standardize the output test result format between automation and manual execution. To use these scripts, first source oe environment, then run the entry point script to look for help. $ resulttool To execute manual test cases, execute the below $ resulttool manualexecution <manualjsonfile> By default testresults.json store in <build_dir>/tmp/log/manual/ [YOCTO #12651] (From OE-Core rev: f24dc9e87085a8fe5410feee10c7a3591fe9d816) Signed-off-by: Mazliana <mazliana.mohamad@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* resulttool: enable merge, store, report and regression analysisYeoh Ee Peng2019-02-2110-0/+832
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OEQA outputs test results into json files and these files were archived by Autobuilder during QA releases. Example: each oe-selftest run by Autobuilder for different host distro generate a testresults.json file. These scripts were developed as a test result tools to manage these testresults.json file. Using the "store" operation, user can store multiple testresults.json files as well as the pre-configured directories used to hold those files. Using the "merge" operation, user can merge multiple testresults.json files to a target file. Using the "report" operation, user can view the test result summary for all available testresults.json files inside a ordinary directory or a git repository. Using the "regression-file" operation, user can perform regression analysis on testresults.json files specified. Using the "regression-dir" and "regression-git" operations, user can perform regression analysis on directory and git accordingly. These resulttool operations expect the testresults.json file to use the json format below. { "<testresult_1>": { "configuration": { "<config_name_1>": "<config_value_1>", "<config_name_2>": "<config_value_2>", ... "<config_name_n>": "<config_value_n>", }, "result": { "<testcase_namespace_1>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, "<testcase_namespace_2>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, ... "<testcase_namespace_n>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, } }, ... "<testresult_n>": { "configuration": { "<config_name_1>": "<config_value_1>", "<config_name_2>": "<config_value_2>", ... "<config_name_n>": "<config_value_n>", }, "result": { "<testcase_namespace_1>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, "<testcase_namespace_2>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, ... "<testcase_namespace_n>": { "status": "<PASSED or FAILED or ERROR or SKIPPED>", "log": "<failure or error logging>" }, } }, } To use these scripts, first source oe environment, then run the entry point script to look for help. $ resulttool To store test result from oeqa automated tests, execute the below $ resulttool store <source_dir> <git_branch> To merge multiple testresults.json files, execute the below $ resulttool merge <base_result_file> <target_result_file> To report test report, execute the below $ resulttool report <source_dir> To perform regression file analysis, execute the below $ resulttool regression-file <base_result_file> <target_result_file> To perform regression dir analysis, execute the below $ resulttool regression-dir <base_result_dir> <target_result_dir> To perform regression git analysis, execute the below $ resulttool regression-git <source_dir> <base_branch> <target_branch> [YOCTO# 13012] [YOCTO# 12654] (From OE-Core rev: 78a322d7be402a5b9b5abf26ad35670a8535408a) Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-build-perf-report/gitarchive: Move common useful functions to libraryRichard Purdie2019-02-212-80/+81
| | | | | | | | | These functions can be reused by the resulttool code so move to the common function library for this purpose. (From OE-Core rev: c66f848938c04e133259c5b6903dc592866ab385) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdrm: Upgrade 2.4.96 -> 2.4.97Fabio Berton2019-02-201-2/+2
| | | | | | | (From OE-Core rev: f15ceac287c094abdeda64b03628455d92e0ce74) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-six: upgrade 1.11.0 -> 1.12.0Richard Purdie2019-02-202-3/+3
| | | | | | | | The license checksum changed due to a change in copyright years only. (From OE-Core rev: f45e890838544bcb77cf2e8503994ef894d3071e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-setuptools: upgrade 40.0.0 -> 40.8.0Richard Purdie2019-02-204-8/+6
| | | | | | (From OE-Core rev: dceac54e05bb786e19de8db33982a8d54e41a915) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip: upgrade 18.0 -> 19.0.2Richard Purdie2019-02-201-3/+3
| | | | | | | | The license checksum changed due to copyright year changes. (From OE-Core rev: a50aa22a229e8c13d36528a9e5a776688a5133a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pbr: upgrade 5.1.1 -> 5.1.2Richard Purdie2019-02-202-5/+5
| | | | | | (From OE-Core rev: 5aa11b42509ae74364f07c5aa30ff6758caffe2f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-gitdb: upgrade 2.0.4 -> 2.0.5Richard Purdie2019-02-202-2/+2
| | | | | | (From OE-Core rev: 50b87d78a3c1193315ccf7cd08f31a99a6950f56) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* diffutils: upgrade to 3.7Chen Qi2019-02-204-67/+2
| | | | | | | | | | | | The following two patches are removed as they are not needed anymore. 0001-Unset-need_charset_alias-when-building-for-musl.patch 0001-explicitly-disable-replacing-getopt.patch (From OE-Core rev: cc8c9b36258d0bb1635b2d4644d7fc64357c5110) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysstat: upgrade to 12.1.3Chen Qi2019-02-201-2/+2
| | | | | | | (From OE-Core rev: ca407f2409328740dac7af34e0e6a0ede578cb2f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: Fix PVRichard Purdie2019-02-201-1/+1
| | | | | | | | | Meant to fix this pre merge, the git revision is the PV so no need to add SRCPV. (From OE-Core rev: 3233096f0dbada97d9d71c98044150a641bfb0a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-networking: upgrade 2.54.1 -> 2.58.0Anuj Mittal2019-02-202-29/+31
| | | | | | | | | | | | | | | | | * Autotools support has been removed upstream, so migrate recipe to meson. For changes, see: https://gitlab.gnome.org/GNOME/glib-networking/blob/glib-2-58/NEWS * Remove unsupported configure options: pkcs11, ca-certificates. See: https://bugzilla.gnome.org/show_bug.cgi?id=793281 https://bugzilla.gnome.org/show_bug.cgi?id=753260 License-Update: Change to LGPLv2.1 (From OE-Core rev: 2cdc3c42283da2782461357a5936c88b402bea5e) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libjpeg-turbo: upgrade 2.0.1 -> 2.0.2Anuj Mittal2019-02-202-10/+10
| | | | | | | | | | | For changes, see: https://github.com/libjpeg-turbo/libjpeg-turbo/releases (From OE-Core rev: 5b89f003c3fc399b08b636f841e0f9f4c3043427) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tar: upgrade to 1.31Chen Qi2019-02-201-7/+2
| | | | | | | | | | Remove the musl specific do_install, as it's not suitable for this version. (From OE-Core rev: 348a96a5b4016a7615f8d22c03ec1ced60367c3b) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: upgrade to 26Chen Qi2019-02-204-21/+28
| | | | | | | | | Refresh patches to avoid warning. (From OE-Core rev: 5dc170d74e932e1dbfc58d23b204bf1d9ebc6e42) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: do not set mtime on data.tar.XAlejandro del Castillo2019-02-202-0/+34
| | | | | | | | Suggested-by: Tristan Ramseyer <t@ramseyer.email> (From OE-Core rev: 212f9ecc18aed653c852d21989093841d063fa44) Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logrotate.py: restore /etc/logrotate.d/wtmpMingli Yu2019-02-201-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During the test logrotate.LogrotateTest.test_1_logrotate_setup, there is below logic: # mkdir $HOME/logrotate_dir # sed -i "s#wtmp {#wtmp {\n olddir $HOME/logrotate_dir#" /etc/logrotate.d/wtmp After all logrotate.LogrotateTest finished, only cleanup $HOME/logrotate_dir as below, but don't restore the config file /etc/logrotate.d/wtmp. [snip] def tearDownClass(cls): cls.tc.target.run('rm -rf $HOME/logrotate_dir') [snip] That's to say, there is one additional line added to /etc/logrotate.d/wtmp and will make the logrotate service start failed when run systemd.SystemdBasicTests.test_systemd_failed Take an example as below when run test as root: # cat /etc/logrotate.d/wtmp # no packages own wtmp -- we'll rotate it here /var/log/wtmp { olddir /root/logrotate_dir missingok monthly create 0664 root utmp minsize 1M rotate 1 } # ls /root/logrotate_dir ls: cannot access '/root/logrotate_dir': No such file or directory # systemctl start logrotate Job for logrotate.service failed because the control process exited with error code. See "systemctl status logrotate.service" and "journalctl -xe" for details. # systemctl status logrotate logrotate.service - Rotate log files Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor preset> Active: failed (Result: exit-code) since Wed 2019-02-13 03:35:19 UTC; 7s ago Docs: man:logrotate(8) man:logrotate.conf(5) Process: 540 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE) Main PID: 540 (code=exited, status=1/FAILURE) Feb 13 03:35:18 qemumips systemd[1]: Starting Rotate log files... Feb 13 03:35:19 qemumips logrotate[540]: error: wtmp:9 error verifying olddir path /root/logrotate_dir: No such file or directory Feb 13 03:35:19 qemumips logrotate[540]: error: found error in file wtmp, skipping Feb 13 03:35:19 qemumips systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Feb 13 03:35:19 qemumips systemd[1]: logrotate.service: Failed with result 'exit-code'. Feb 13 03:35:19 qemumips systemd[1]: Failed to start Rotate log files. Add the logic to restore /etc/logrotate.d/wtmp to make the cleanup complete to fix the above issue. (From OE-Core rev: a2db9320d97d12d87524ff16a329f9c38a8da33f) Signed-off-by: Mingli Yu <Mingli.Yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* menu-cache: fix upstream version checkAlexander Kanavin2019-02-201-1/+1
| | | | | | | (From OE-Core rev: 41eaa75cdac684e152d3f6c881cac1ac83cdbb9d) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-29 19:53:17 +0000