linux/poky.git/meta/lib, branch 3.5_M1

selftest/recipetool: Add tests for branch parameter and srcbranch option

2021-12-09T10:33:25+00:00

The recipetool support two ways to pass a branch and fallback to master if no branch is defined. Add tests for default branch, branch parameter and srcbranch option. (From OE-Core rev: f232cffc09e917458d6e850b4aca4f87b53b43e4) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

selftest: devtool: Separate common functions and devtool sstate setup into two classes

2021-12-09T10:33:25+00:00

The selftest recipetool base class reuse the selftest devtool base class. Thereby the selftest devtool base class setup its own devtool sstate and the selftest recipetool classes trigger the build of recipes. This leads to the problem that the build artifacts doesn't reach the persistent sstate cache and rebuild on every selftest run. Move the common selftest devtool functions into its own class and use the sstate cache in the recipetool tests. (From OE-Core rev: c0bd0686092181b6a5316c373b5b125d78a24e9f) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

selftest/recipetool: Split tests into separate test classes

2021-12-09T10:33:25+00:00

Split tests into separate test classes to speed up individual test runs by reducing the test setup to a minimum. The pkgdata generation is only needed for the append tests and slow down the other tests. (From OE-Core rev: 2aef869bcca3e0de4afb9ef00492de3ee72b035c) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

selftest/devtool: Check branch in git fetch

2021-12-09T10:33:25+00:00

The commit 'meta/scripts: Manual git url branch additions (dc53fe75cc)' forget the url branch= parameter in the devtool git fetch test. (From OE-Core rev: 1419168a58a5caf99e24ada08c9ab639344a78b4) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Richard Purdie

patch.py: Initialize git repo before patching

2021-12-03T23:37:16+00:00

If PATCHTOOL="git" has been specified but workdir is not git repo bitbake fails to apply the patches with error message: Command Error: 'git rev-parse --show-toplevel' exited with 0 Output: fatal: not a git repository (or any of the parent directories): .git Fix this by initializing the repo before patching. This allows binary git patches to be applied. (From OE-Core rev: 6184b56a7a0fc6f5d19fdfb81e7453667f7da940) Signed-off-by: Pavel Zhukov Signed-off-by: Richard Purdie

go-helloworld: test at runtime

2021-11-29T23:07:13+00:00

This adds a smoke check for whether the Go toolchain actually produces working executables across a range of architectures. (From OE-Core rev: 2819bb2cf22c6cfcaeaee79f0280097ec9cb9327) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

sanity/lib: Replace usage of LooseVersion() with bb.utils.vercmp_string_op()

2021-11-29T23:07:13+00:00

distutils is going away and we have functionality in bitbake which can handle these comparisions so switch to the bb.utils function. (From OE-Core rev: fe624b520e6c75e16a8f394785ab0216341402f9) Signed-off-by: Richard Purdie

oeqa/parselogs: Fix quoting

2021-11-29T23:07:13+00:00

Fix deprecation warnings about invalid escape sequences. (From OE-Core rev: 43542614395150e8fa34133ba0fc7ee90f215bcb) Signed-off-by: Richard Purdie

oeqa/utils/dump: Fix typo

2021-11-26T17:01:08+00:00

(From OE-Core rev: 3770d539d83b589b3f8bde21fcf896bb046611d4) Signed-off-by: Richard Purdie

oe/utils: by default cap cpu_count() to 64 cores

2021-11-25T21:55:10+00:00

Larger systems may have large numbers of cores, but beyond a certain point they can't all be used for compiling: whilst purely compute-intensive jobs can be parallelised to hundreds of cores, operations such as compressing (needs lots of RAM) or compiling (lots of I/O) don't scale linearly. For example, the Marvel ThunderX2 has 32 cores, each capable of executing four threads, and can be configured with two sockets, making 256 CPUs according to Linux. Zstd using 256 threads has been seen to fail to allocate memory during even small recipes such as iso-codes. Add a default cap of 64 CPUs to the cpu_count() method so that extreme parallisation is limited. 64 is high enough that meaningful gains beyond it are unlikely, but high enough that most systems won't be effected. (From OE-Core rev: 765d0f25ce48636b1838a5968e2dc15de2127428) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie