buildroot/utils/test-pkg, branch 2019.02-op-build

utils/test-pkg: generate package config if it is not specified

2019-03-27T09:42:52+00:00

It is possible to generate one-line config for the package just by normalize it to the form: BR2_PACKAGE_${pkg_replaced-to_and_uppercase} it simplifes a bit of testing package where no additional config options are needed. Signed-off-by: Vadim Kochan Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni (cherry picked from commit a946813dd581ac2e1aea6745edad2bc7ce44e6aa) Signed-off-by: Peter Korsgaard

utils/test-pkg: force checking dependencies

2019-01-03T10:41:26+00:00

Currently, if a user runs "make" while specifying a specific package (IE: make -p foo), the Makefile logic skips checking to see if all the dependencies are selected in the specified packages config file. This behavior is useful to test simple packages which do not have "complex" dependencies. However; if a developer uses test-pkg -p ${package_name} to check their package, the package may pass all the checks, but would have otherwise failed with a simple "make" because the developer may have failed to add a select line in packages config file, even if there is a new dependency in the packages Makefile. Pass the environment variable "BR_FORCE_CHECK_DEPENDENCIES" to the Makefile in the test-pkg script, and check it's value in the Makefile. If the value is "YES" force checking for dependency issues. Signed-off-by: Adam Duskett Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

utils/test-pkg: use the correct config prefix when merging

2018-11-24T09:11:13+00:00

We should use an empty prefix as we do not have any prefix. Note that BR2_ is mere a convention. Signed-off-by: Nasser Afshin Reviewed-by: Petr Vorel Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

utils/test-pkg: log the output of merge-config

2018-07-10T21:01:47+00:00

Currently, the stdout is consigned to oblivion, while the stderr is not redirected at all. So, when the configuration under test redefines a symbol, like is the case when testing busybox for example, there is an ugly warning. So, just redirect both stdout and stderr to the logfile. Signed-off-by: "Yann E. MORIN" Tested-by: Matt Weber Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

support/config-fragments/autobuild: remove Blackfin configuration

2018-04-15T20:03:18+00:00

In preparation for the removal of the Blackfin architecture, drop the autobuilder toolchain configuration that was testing Blackfin. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

test-pkg: test a subset of toolchains by default, add -a and -n options

2018-04-01T14:30:34+00:00

During the latest Buildroot Developers meeting, we discussed that test-pkg would perhaps be more widely used if it tested a smaller subset of toolchains. Indeed, it currently tests 47 toolchains, which takes very long to build. Several of the toolchain configurations are quite similar, and it is perhaps not necessary for contributors to test them all before submitting a package. Therefore, this commit changes the test-pkg script to only test a subset of the toolchain configurations by default. The N first configurations of the CSV files are tested, where N is hard-coded in the script. The CSV file has therefore been re-organized to have the first N toolchains be the most important ones. A -a/--all option is added to test with all toolchains, while a -n/--number option is added to test with the first N toolchains, N being passed on the command line. Note that the list of toolchains (built in the "toolchains" shell variable) is no longer sorted. Indeed, when the first N toolchains are tested, we want them to be tested in the same order as they are listed in the CSV file, as we are careful to order them in an interesting order. We only sort when all toolchains are tested. Signed-off-by: Thomas Petazzoni Tested-by: Matt Weber Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

utils/test-pkg: always run a global legal-info

2018-01-08T08:16:50+00:00

Instead of limiting it to the package under test, we run it globally. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Matthew Weber Signed-off-by: Thomas Petazzoni

test-pkg: filter empty lines and comments in CSV file

2017-11-27T22:24:49+00:00

In preparation for the addition of comments in the CSV file listing toolchain configurations, we filter out such lines when reading the CSV file in utils/test-pkg. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

utils/test-pkg: add option to use an alternate toolchains CSV file

2017-07-29T13:40:55+00:00

When testing a package with test-pkg, it may be useful to override the set of toolchains used. For example: - to test with toolchains used in your company; - to test against a subset that is known to be problematic; - to use only toolchains you already have available locally when you have no network access. Add an option to use an alternate CSV file containing the config fragments of toolchains to try. Cc: "Yann E. MORIN" Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

test-pkg: use merge_config.sh to merge the fragments

2017-07-25T21:07:03+00:00

It is supposedly more robust than just concatenating. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Yann E. MORIN Signed-off-by: Thomas Petazzoni