linux/poky.git/bitbake/lib/bb/tests, branch 5.2_M3

bitbake: tests/fetch: Verify regular expression "URLs" that contain a ?

2025-03-07T15:38:15+00:00

A regular expression "URL" in PREMIRRORS and MIRRORS may contain a ? as part of the regular expression. Make sure this does not cause problems. (Bitbake rev: 5af7fe4473cd7e75d4eb7f8b93c499bd157ff156) Signed-off-by: Peter Kjellerstedt Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

bitbake: tests/fetch: Add an additional test case to check whether the fast fetch is shallow

2025-03-06T11:16:46+00:00

(Bitbake rev: 16f1961e077c525ccfc12496a3deca944df89fc6) Signed-off-by: Stefan Koch Signed-off-by: Richard Purdie

bitbake: tests/fetch: Adapt test cases for fast shallow fetches

2025-03-06T11:16:46+00:00

- Address the absence of an initial full bare clone - Utilize the initial shallow clone - Modify existing test cases for this behavior - Remove incompatible test cases (Bitbake rev: 599fedacd7782dcb52825c22200f35344c102548) Signed-off-by: Stefan Koch Signed-off-by: Richard Purdie

bitbake: bitbake: runqueue: Verify mcdepends are valid

2025-03-03T21:38:57+00:00

In order to avoid a potentially confusing backtrace, check that the mcdepend is valid when we add it. Add a test case to ensure invalid configurations are caught and trigger an error. [RP: Reworked test case to simplify and improve code] (Bitbake rev: ff523497270f37b484b44a4445c2194791bcb6ff) Signed-off-by: Mark Hatle Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

bitbake: bitbake: tests/data: add tests for variable flags

2025-02-13T22:24:27+00:00

Check default flags are correctly returned by getVarFlags and check all flags are returned when internalflags is True. Check delVarFlags also removes default value. Check all flags are removed after delVar. Run the test with: $ bitbake-selftest -v bb.tests.data.TestFlags test_delflag (bb.tests.data.TestFlags.test_delflag) ... ok test_delvar (bb.tests.data.TestFlags.test_delvar) ... ok test_setflag (bb.tests.data.TestFlags.test_setflag) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.000s OK This is a test case for [YOCTO #15685] (Bitbake rev: ff8cae735cf489373af1aac7ee233d7b82d483d3) Signed-off-by: Louis Rannou Signed-off-by: Richard Purdie

bitbake: tests: fetch: quote URI password as per RFC3986

2025-02-11T21:18:39+00:00

The password must be quoted as per RFC3986 because it can contain reserved characters. (Bitbake rev: 5c53dbf0ad4385e1de7f2eef66565a1f05dae67a) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

bitbake: tests: fetch: use lower case hostnames

2025-02-11T21:18:39+00:00

Do not use upper case hostnames because the hostname is case insensitive and maybe decoded into lower case to follow the common style. (Bitbake rev: 554b7048412c4c67bf895a8b98822b54ac3a66db) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

bitbake: tests: fetch: add test for file URI with @

2025-02-11T21:18:39+00:00

(Bitbake rev: f169704ef48f04da33aaca8b1ad5d8d7eabf8fd6) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

bitbake: parse: Forbid ambiguous assignments to ${.}, ${+}, and ${:} variables

2025-02-05T12:11:01+00:00

Old code that parse variable names in assignment commands behave differently for variables that ends with special symbol for single-character variable names and multi-character variable names. For example: A+="1" # Change variable ${A}, '+' glued to '=' A+ = "1" # Change variable ${A+} +="1" # Change variable ${+}, the '+' symbol not part of assignment operator + = "1" # Change variable ${+} New code would always assume that '.=', '+=', and ':=' is assignment operator. As result code like the following would raise parsing error +="value" While code with extra spaces would work as before + = "value" # Change variable ${+} This change allow to catch issues in code that generate bitbake configuration files in a manner like "echo ${VARNAME}+=${VALUE} >> conf/local.conf" (Bitbake rev: 93059aad13a12cd69d86368795c88e5349197d5d) Signed-off-by: Nikolai Merinov Signed-off-by: Richard Purdie

bitbake: tests/parse: Add test for unclosed functions

2025-01-28T14:34:36+00:00

This test covers the handling of unclosed functions. It tests that both whitespace and tabs generate the correct exception if added before a closing bracket. Additionally that a residue blocks generates a error is tested as well. [YOCTO #15470] (Bitbake rev: 29e67acb87ae76879efe9688a69c961a96df10f1) Signed-off-by: Savvas Etairidis Signed-off-by: Richard Purdie