linux/poky.git/bitbake/lib/bb, branch 3.1_M2

bitbake: tests/fetch: Allow wget upgrade tests to run against a local server

2020-01-22T15:56:39+00:00

Currently these tests rely upon multiple uptream webservers which may change or be unavailable. Add local copies of the test data, copy the httpserver from OE-Core (used for testing there) and run these tests against a local server instead. (Bitbake rev: d5a4a352723258b4d499d3a51f340109c4f36f60) Signed-off-by: Richard Purdie

bitbake: persist_data.py: Immediately get exclusive lock in setitem

2020-01-19T13:31:05+00:00

To avoid races, SQLTable::__setitem__ needs an exclusive lock for the entire transaction, not just the INSERT/UPDATE part. (Bitbake rev: feb43e7c30f5bfab75d718896c45df621810d06f) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: fetch2/git: _revision_key: collapse adjacent slashes

2020-01-19T13:31:05+00:00

>From a SRCREV caching point of view, there is no reason to treat the following upstreams as different: SRC_URI = "git://github.com/file/file.git" SRC_URI = "git://github.com//file/file.git" (Bitbake rev: 425e21c14955dd38868c6e97637df3bbe0f89fac) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: fetch2: do not suffix srcrev cache key with PN

2020-01-19T13:31:05+00:00

Prior to this change, two different recipes pulling from the same exact repo could get a different SRCREV during a single parse session. This was originally observed using git. For git at least, it still allows recipes to pull from the same repo, but with different branches or tags, since the form of the srcrev cache key for git is: "git:" + ud.host + ud.path.replace('/', '.') + ud.unresolvedrev[name] Where the 'unresolvedrev' part is the branch or tag name. (Bitbake rev: 6c938e6fd29beebe09b32be839dae008fe6491d2) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: tests/utils: add tests for bb.utils.get_referenced_vars

2020-01-19T13:31:05+00:00

(Bitbake rev: 346e74e5d751aadf7881de70b5ab6670dfc463ce) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: bb.utils: add get_referenced_vars

2020-01-19T13:31:05+00:00

Given a start expression, bb.utils.get_referenced_vars returns the referenced variable names in a quasi-BFS order (variables within the same level are ordered aribitrarily). For example, given an empty data store: bb.utils.get_referenced_vars("${A} ${B} ${d.getVar('C')}", d) returns either ["A", "B", "C"], ["A", "C", "B"], or another permutation. If we then set A = "${F} ${G}", then the same call will return a permutation of [A, B, C] concatenated with a permutation of [F, G]. This method is like a version of d.expandWithRefs().references that gives some insight into the depth of variable references. (Bitbake rev: 076eb5453ca35b8b75b8270efb989d5208095b27) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: lib: amend code to use proper singleton comparisons where possible

2020-01-19T13:31:05+00:00

amend the code to handle singleton comparisons properly so it only checks if they only refer to the same object or not, and not bother comparing the values. (Bitbake rev: b809a6812aa15a8a9af97bc382cc4b19571e6bfc) Signed-off-by: Frazer Clews Signed-off-by: Richard Purdie

bitbake: lib: remove unused imports

2020-01-19T13:31:05+00:00

removed unused imports which made the code harder to read, and slightly but less efficient (Bitbake rev: 4367692a932ac135c5aa4f9f2a4e4f0150f76697) Signed-off-by: Frazer Clews Signed-off-by: Richard Purdie

bitbake: runqueue: Use a set for the setscene tasks list

2020-01-13T13:12:23+00:00

This should give performance improvements to functions using this list of tasks (sets are used for most of the other code for this reason, not sure why this wasn't a set in the first place). (Bitbake rev: f5daef68703481a3c243dfecc7de404e6ebfdbb6) Signed-off-by: Richard Purdie

bitbake: knotty: Be consistent when creating/updating progress bars

2020-01-13T13:12:23+00:00

When creating a new progress bar (using BBProgress), a colon was appended to the supplied message. However, when updating the message, no colon was appended. Change this so that the colon is instead part of the widgets that make up the progress bar so that it does not matter when and how the message is updated, it always displays the same. (Bitbake rev: 08f35c04f6e1ce4c4ca5c2bef4cd8a192e12e682) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb, branch 3.1_M2

bitbake: tests/fetch: Allow wget upgrade tests to run against a local server

bitbake: persist_data.py: Immediately get exclusive lock in __setitem__

bitbake: fetch2/git: _revision_key: collapse adjacent slashes

bitbake: fetch2: do not suffix srcrev cache key with PN

bitbake: tests/utils: add tests for bb.utils.get_referenced_vars

bitbake: bb.utils: add get_referenced_vars

bitbake: lib: amend code to use proper singleton comparisons where possible

bitbake: lib: remove unused imports

bitbake: runqueue: Use a set for the setscene tasks list

bitbake: knotty: Be consistent when creating/updating progress bars

bitbake: persist_data.py: Immediately get exclusive lock in setitem