linux/poky.git/bitbake, branch yocto-4.0.31

bitbake: test/fetch: Switch u-boot based test to use our own mirror

2025-07-30T14:47:48+00:00

The upstream servers are having issues so switch to our own shadow copy of the repo. (Bitbake rev: 8e2d1f8de055549b2101614d85454fcd1d0f94b2) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: cache: bump cache version

2025-03-27T15:16:30+00:00

Version bump is needed after "siggen.py: Improve taskhash reproducibility" otherwise there will be taskhash mismatch errors (Bitbake rev: 046871d9fd76efdca7b72718b328d8f545523f7e) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: siggen.py: Improve taskhash reproducibility

2025-03-19T14:13:17+00:00

file checksums are part of the data checksummed to generate the task hash. The list of file checksums was not ordered. In this commit we make sure the task hash checksum takes a list of checksum data that is ordered by unique file name thus guaranteeing reproducibility. (Bitbake rev: da5f41996687e18b78d9c9845e621d832115aa1e) Signed-off-by: Paulo Neves Signed-off-by: Richard Purdie Signed-off-by: Martin Jansa Signed-off-by: Steve Sakoman

bitbake: tests/fetch: Fix git shallow test failure with git >= 2.48

2025-02-05T14:54:35+00:00

>From git 2.48 release notes: """ When "git fetch $remote" notices that refs/remotes/$remote/HEAD is missing and discovers what branch the other side points with its HEAD, refs/remotes/$remote/HEAD is updated to point to it. """ This means with git 2.48 onwards, there is a mystery "HEAD" revision appearing in some of our shallow clone tests. We can avoid this by using the same canonicalization as used for the reference revisions. This resolves autobuilder failures on the Fedora 40 workers. (Bitbake rev: e71f1ce53cf3b8320caa481ae62d1ce2900c4670) Signed-off-by: Richard Purdie (cherry picked from commit c83444d1210740e27b1744d3aa7c5cad4e28db2f) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: fetch/wget: Increase timeout to 100s from 30s

2024-12-02T14:23:20+00:00

Testing shows the worst case CDN response time can be up to 100s. The wget fetcher is used for accessing sstate from the CDN so increase our timeouts there to match our worst case repsonse times. (Bitbake rev: 3f88b005244a0afb5d5c7260e54a94a453ec9b3e) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: fetch2: use persist_data context managers

2024-12-02T14:23:19+00:00

Python 3.13 emits a ResourceWarning for unclosed sqlite3 `Connection`s. See https://docs.python.org/3/whatsnew/3.13.html#sqlite3 The previous commit fixed persist_data's context manager to close the connection, but we were never actually using `with` in the first place. This change is not necessary on 'master' because persist_data was removed. (Bitbake rev: 9789c55ecc90ba074596061fa16e90d3e8accb02) Signed-off-by: Chris Laplante (cherry picked from commit 61f803c7d92a012b62837b0cdae4789a394b260e) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: persist_data: close connection in SQLTable exit

2024-12-02T14:23:19+00:00

A Connection's __exit__ does not close the connection, but rather deals with transactions. See https://docs.python.org/3/library/sqlite3.html#how-to-use-the-connection-context-manager This change is not necessary on 'master' because persist_data was removed. (Bitbake rev: 97856a56cbf09401b34d6c9bb5444c07a88772ce) Signed-off-by: Chris Laplante (cherry picked from commit b0fba0f5af555ff970406b5cf3bf8fb113d953d1) Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

bitbake: codeparser: Fix handling of string AST nodes with older Python versions

2024-11-15T14:05:32+00:00

Commits 4591011449212c8e494ea42348acb2d27a82a51b and 6c19b6cf105ac321ec89da1a876a317020c45ab7 unconditionally changed codeparser to rely on CPython 3.8 semantics. However, kirkstone continues to support CPython versions >= 3.6.0 and as such string AST nodes were no longer correctly identified. Fix this by continuing to use `ast.Str` for Python versions < 3.8.0 and only using the new code path for more recent versions. Detecting which version of the AST API to use seems to be non-trivial so the Python feature version is used instead. Instances of this issue can be identified when executing bitbake with debug logging: while parsing MACHINE_ARCH, in call of d.getVar, argument ''TUNE_PKGARCH'' is not a string literal As a consequence of these parsing issues, bitbake may assume that task inputs haven't changed and as such erroneously reuse sstate objects when it shouldn't. (Bitbake rev: fb73c495c45d1d4107cfd60b67a5b4f11a99647b) Signed-off-by: Philip Lorenz Signed-off-by: Steve Sakoman

bitbake: tests/fetch: Use our own mirror of mobile-broadband-provider to decouple from gnome gitlab

2024-11-02T13:06:09+00:00

GNOME gitlab has occasional downtime which impacts bitbake-selftest and causes autobuilder failures. Switch to our own mirror for test purposes to avoid those issues. (Bitbake rev: 0c30e9aadd30fc6f0dcf811eb8340687b52eb00b) Signed-off-by: Richard Purdie (cherry picked from commit 91e268b11ed683bd197026f9b36001f6d54ee05c) Signed-off-by: Steve Sakoman

bitbake: tests/fetch: Use our own mirror of sysprof to decouple from gnome gitlab