linux/poky.git/bitbake/lib, branch yocto-3.0

bitbake: bitbake: Update to version 1.44.0

2019-10-09T13:10:48+00:00

(Bitbake rev: 5d83d828cacb58ccb7c464e799c85fd2d2a50ccc) Signed-off-by: Richard Purdie

bitbake: toaster: Enable Zeus branch in place of Thud

2019-10-08T19:49:36+00:00

Toaster directly supports the last two stable branches of Yocto Project. With "Zeus" being released, it is time to replace "Thud". [YOCTO #13579] (Bitbake rev: 29374386fd7fcfac9d4070584dff76327845595e) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: bitbake: Bump verison 1.43.1 -> 1.43.2

2019-10-02T19:22:25+00:00

This allows metadata to depend on SignatureGeneratorUniHashMixIn which was recently added. (Bitbake rev: f0f814407fdd2fffa7071c36c011b489bfcd53da) Signed-off-by: Richard Purdie

bitbake: toaster: improve warnings when adding dependency to packages

2019-10-02T13:42:13+00:00

Some of the objects that bitbake reports to Toaster as dependencies to packages are known objects that are not packages, for example library files and kernel modules. In the Toaster logs, mark these as "Info" instead of "Warning". [YOCTO #13386] (Bitbake rev: 0d66f644d647900e8f5afa526a6d9cee687c41cc) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: toaster: issues in import layer when clicking 'add layer'

2019-10-02T13:42:13+00:00

There were three issues in this one bug. 1) The Add Layer button allows empty layers 2) The internal XHR URL was wrong, which caused a hidden AJAX error and did not correctly complete the action nor disable the button after an add. 3) There was a race condition between typing in the dependent layer select text box (which would normally disable the add button), and the typeahead pull-down selection (which would normally enable the add button). This forced the user to select the typedahead layer twice. [YOCTO #13385] (Bitbake rev: c4ccf3a792ae7e8549b879ba77ff7f7edb0e665a) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: tests/runqueue: Fix hashserve shutdown race

2019-10-02T13:18:59+00:00

The hashserve can delete its socket whilst the cleanup us happening leading to backtraces and test failures. Add code to avoid this race condition. [YOCTO #13542] (Bitbake rev: efd7b025cee25d0ee668c09476395d08fcf5ae1a) Signed-off-by: Richard Purdie

bitbake: siggen: Remove full path from unitaskhashes keys

2019-09-30T16:23:35+00:00

The full paths make the cache useless in the sdk. They also bloat the cache size. They're for human debugging benefit only so compromise and reduce this to the filename. (Bitbake rev: 3b275c4083eae1d3781f0862919af9de83932b0f) Signed-off-by: Richard Purdie

bitbake: runqueue: Small performance optimisation

2019-09-30T16:23:35+00:00

A minor performance optmisation to keep lists smaller when running large builds. We can do this since once a task has been built, we don't need to worry about it. This improves a major bottleneck that shows up on performance profile charts in dryruns. (Bitbake rev: cd6b89230823707c3c9bb9e6883bf5a971916581) Signed-off-by: Richard Purdie

bitbake: runqueue: Save unihashes more frequently

2019-09-30T16:23:35+00:00

There are some runqueue code paths where the unihash cache would not be saved where for example only parsing or an occurred. Save the cache at the end of runqueue generation to ensure entries are cached. (Bitbake rev: 9eee0d36870c11dd303894a6151c33a83bd3a1bc) Signed-off-by: Richard Purdie

bitbake: siggen: Avoid writing misleading sigdata files

2019-09-30T16:23:35+00:00

Use the unihash in the output filename of sigdata files else the contents of stamp directories is misleading. Write the unihash into the singature to make it clear what happened. (Bitbake rev: feb01ee54d3706fe93768f332054c7532f7209e4) Signed-off-by: Richard Purdie