linux/poky.git/meta/classes/ptest.bbclass, branch 2.7_M2

ptest: Optionally strip build host tool info from installed files

2018-12-03T12:20:01+00:00

Several packages (eg. acl, attr, openssl) install Makefiles or other build host configuration files for ptest so that they can run `make check`, for instance. These build host files commonly include paths and versions of build host tools, (eg. rpm or perl) whose presence and version depends on the build host distro. Optionally strip lines from installed PTEST_BUILD_HOST_FILES using an extended regex pattern defined in PTEST_BUILD_HOST_PATTERN. This has no effect on the on-target ptest. (From OE-Core rev: a3b657470eeea9f1954bc3a3e593a5c4907b6f17) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

ptest: Reproducibility: Strip build host paths from any installed Makefile

2018-12-03T12:20:01+00:00

A common pattern for ptest is to install a Makefile that provides a make check target. These generated Makefiles are normally full of build host paths, to hosttools, and to files and scripts within the source or build tree. They also commonly include the CFLAGS and CPPFLAGS. None of these build host paths can possibly work on-target, so stripping them has no effect on the success of the resulting ptests. Stripping the HOSTTOOLS_DIR has this effect, for instance: -MKDIR_P = /home/douglas/workspace/upstream/build/tmp/hosttools/mkdir -p +MKDIR_P = mkdir -p The curious WORKDIR/*= pattern avoids non-parseable -fdebug-prefix-map patterns in the CFLAGS by adding an arbitrary ".", eg: -fdebug-prefix-map=.=/usr/src/debug/rsyslog/8.37.0-r0 In all other cases, we simply remove the WORKDIR, eg: CPP = arm-tait-linux-gnueabi-gcc -E --sysroot=recipe-sysroot ... (From OE-Core rev: 137e38dbae42e9d4d413cd2f9460fb707ca77f9c) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

ptest: Reproducibility: Take control of umask

2018-11-23T23:35:19+00:00

The build host umask was leaking into the thing-ptest packages at do_install_ptest() time. (From OE-Core rev: 891343e8ba6490ca3e1876c892269b611ddc7877) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

ptest.bbclass: use BPN in PTEST_PATH for multilib

2017-03-04T23:18:19+00:00

Use BPN instead of PN in PTEST_PATH for multilib builds, or we get two directories for a package in libdir which doesn't make sense, e.g. $ ls /usr/lib/*coreutils /usr/lib/coreutils: libstdbuf.so /usr/lib/lib32-coreutils: ptest (From OE-Core rev: 0e949b7bfc4207aba0e3c4d12b76cc1f1815470d) Signed-off-by: Jackie Huang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes: Ensure pass setVar/setVarFlag strings, not integers

2015-11-24T15:50:26+00:00

This doesn't cause any issues right now but it make sense to standardise on consistently using strings in the data store. (From OE-Core rev: 99203fbe5ad470ef65cff93cec9d7f332883b5ee) Signed-off-by: Richard Purdie Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ptest: run-ptest not required to run do_install_ptest

2015-10-01T14:07:48+00:00

Modify do_install_ptest_base to run do_install_ptest and install the Makefile irrespective of the presence of ${WORKDIR}/run-ptest. This change allows "ptest-aware" packages to install run-ptest as part of the make machinery. (From OE-Core rev: 2055517d91e0c55ed108d3a6f52abd1d2c6824b2) Signed-off-by: Ian Ray Signed-off-by: Richard Purdie

Revert "ptest: use fakeroot for do_install_ptest_base"

2015-09-12T21:48:46+00:00

This reverts commit 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d. (This fix was incorrect and there is a better fix due to be merged) (From OE-Core rev: 21e044d92e927639a574c43cf7778e31f2e66377) Signed-off-by: Richard Purdie

ptest: fix file ownerships in ${PTEST_PATH}

2015-09-12T21:48:34+00:00

As most upstreams don't have installable test suites it's fairly common to copy files directly out of a source tree for ptests, but this results in files in the recipe being owned by the user running bitbake: WARNING: QA Issue: .../sed/4.2.2-r0/packages-split/sed-ptest/usr/lib64/ sed/ptest/testsuite/bug-regex21 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated] Instead of needing to fix this in every recipe that has this problem simply chown the files to root:root in do_install_ptest_base. (From OE-Core rev: 552daf60c58784c8f1acc12c5a443a44a922f743) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

ptest: use fakeroot for do_install_ptest_base

2015-09-09T13:27:55+00:00

The do_install_ptest_base task wasn't running in the fakeroot environment so files installed by do_install_ptest were often not owned by root:root but the user running the builds. (From OE-Core rev: 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie