linux/poky.git/meta-selftest, branch walnascar

pulseaudio: Add audio group explicitly

2025-09-09T16:30:07+00:00

Since pulseaudio-server requires the audio group, we explicitly add it. When use useradd-staticids or do not use the default group in base-passwd, an error will occur because the audio group is not defined. NOTE: pulseaudio: Performing useradd with [--root TOPDIR/tmp/work/cortexa72-poky-linux/pulseaudio/17.0/recipe-sysroot --home-dir /var/run/pulse --gid 998 --groups audio,pulse --no-create-home --system --shell /bin/false --uid 998 pulse] useradd: group 'audio' does not exist ERROR: pulseaudio: useradd command did not succeed. (From OE-Core rev: 4fc918da4667eebbbdae3def8c38209a3d650f97) Signed-off-by: Kyungjik Min Signed-off-by: Steve Sakoman

devtool: reset: Escape command line input used in regular expression

2025-03-20T11:29:04+00:00

Running, e.g., `devtool reset sdbus-c++` would result in the following error: re.error: multiple repeat at position 35 This was due to the ++ in the recipe name, which would be treated as an incorrect regular expression in _reset(). Use re.escape() to make sure all characters in the recipe name are treated literally. (From OE-Core rev: 6e73bd9b3e6d529752db93879f2c0ed53873dd1a) Signed-off-by: Peter Kjellerstedt Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta/meta-selftest: Fix variable assignment whitespace

2025-02-01T13:42:34+00:00

Recipes are much more readable with whitespace around the assignment operators. Fix various assignments in OE-Core to show this is definitely the preferred formatting. (From OE-Core rev: 30ea609d3357fb3de911f2f6a5e6856c151b976a) Signed-off-by: Richard Purdie

oeqa/poisoning: fix gcc include poisoning test

2025-01-22T13:20:29+00:00

The test code in poison was flawed: as long as one CPP/CC/CXX has fatal poisoning enabled then the test passes. However, at the moment due to a bad rebase only CPP has fatal poisoning and CC/CXX do not. Rewrite the do_compile() task to more carefully check the output so the test harness itself just has to bitbake the recipe. Note that this results in the test failing: ERROR: poison-1.0-r0 do_compile: C Compiler is not poisoned. Exit status 0, output: cc1: warning: include location "/usr/include" is unsafe for cross-compilation [-Wpoison-system-directories] ERROR: poison-1.0-r0 do_compile: C++ Compiler is not poisoned. Exit status 0, output: cc1plus: warning: include location "/usr/include" is unsafe for cross-compilation [-Wpoison-system-directories] (From OE-Core rev: 5b413d1fdb4bdbaec86d630bb52c3ccf68aae789) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bbconfigbuild/configfragments.py: set BBPATH in standalone datastore

2025-01-09T16:59:23+00:00

Otherwise fragments with 'require' statements will not parse, as the parser will not be able to find files referred to by those statements. Add such a statement to the test fragment so that the scenario is tested. [YOCTO #15707] (From OE-Core rev: d88e63d1a7867b3a4ebfc57d472900136b5361d8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake-config-build: add a plugin for config fragments

2024-12-13T11:11:18+00:00

This allows fine-tuning local configurations with pre-frabricated configuration snippets in a structured, controlled way. It's also an important building block for bitbake-setup. The tool requires that each fragment contains a one-line summary, and one or more lines of description, as BB_CONF_FRAGMENT_SUMMARY style metadata. There are three (and a half) operations (list/enable/disable/disable all), and here's the 'list' output: alex@Zen2:/srv/storage/alex/yocto/build-64$ bitbake-config-build list-fragments NOTE: Starting bitbake server... Available fragments in selftest layer located in /srv/work/alex/poky/meta-selftest: Enabled fragments: selftest/test-fragment This is a configuration fragment intended for testing in oe-selftest context Unused fragments: selftest/more-fragments-here/test-another-fragment This is a second configuration fragment intended for testing in oe-selftest context (From OE-Core rev: fdb611e13bd7aa00360d3a68e4818ef5f05c8944) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

selftest/static-group: Add seat

2024-11-28T12:37:12+00:00

With a group added to the seatd recipe, we need an entry in our static group file for selftest. (From OE-Core rev: 655d334584769a9b9d86cf8fab2c06bc0878d0b3) Signed-off-by: Richard Purdie

oeqa/selftest: add a test for bitbake "-e" and "-getvar" difference

2024-11-18T22:09:03+00:00

This is a non-regression test for [YOCTO #15638] (From OE-Core rev: 22b508da24e0f7e5ad8ce4e090832bd0829963f0) Signed-off-by: Yoann Congal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

oe-selftest-image: use explicit IMAGE_FEATURES instead of debug-tweaks

2024-11-06T12:18:05+00:00

debug-tweaks is vague and doesn't give any indication that the root user can login over SSH without a password. This behaviour is incredibly dangerous if used unwittingly, so discourage it by using the underlying features explicitly to spell out exactly what is being done. (From OE-Core rev: 83cd8b5ca4544e9b19c110035276e5de2ebe7404) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest/container: fix IMAGE_FEATURES assignment

2024-11-06T12:18:05+00:00

Assigning IMAGE_FEATURES="" in local.conf doesn't actually do anything useful, as bitbake.conf has IMAGE_FEATURES += EXTRA_IMAGE_FEATURES after the include of local.conf. In this test case, this results in IMAGE_FEATURES still using EXTRA_IMAGE_FEATURES, so the image contains the files installed by the post-install-logging feature. As the intention here is that container-test-image is as minimal as possible, move the IMAGE_FEATURES assignment into the image itself so it actually works, and update the expected file list to remove the post-install-logging files. (From OE-Core rev: c65349e1238ddc6634dfa4759c57e6168a355200) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie