linux/poky.git/bitbake, branch master-next2

bitbake: hashserv fixup

2019-09-18T10:52:03+00:00

(Bitbake rev: b31de77665851fd1745ced8aa0abc26df7b4ea9a) Signed-off-by: Richard Purdie

bitbake: svn fetcher: allow "svn propget svn:externals" to fail

2019-09-18T10:52:03+00:00

Not all servers and repositories have this property set which results in failures like this when actual svn checkout command succeeded: svn: warning: W200017: Property 'svn:externals' not found on '' svn: E200000: A problem occurred; see other errors for details (Bitbake rev: a080b440935b0f4385d8344b176e68aec98fb580) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie

bitbake: fixup

2019-09-18T10:52:03+00:00

(Bitbake rev: 6f66f785a36e8e3128330936e6f41011615afae5) Signed-off-by: Richard Purdie

bitbake: bitbake: Rework hash equivalence

2019-09-18T10:52:03+00:00

Reworks the hash equivalence server to address performance issues that were encountered with the REST mechanism used previously, particularly during the heavy request load encountered during signature generation. Notable changes are: 1) The server protocol is no longer HTTP based. Instead, it uses a simpler JSON over a streaming protocol link. This protocol has much lower overhead than HTTP since it eliminates the HTTP headers. 2) The hash equivalence server can either bind to a TCP port, or a Unix domain socket. Unix domain sockets are more efficient for local communication, and so are preferred if the user enables hash equivalence only for the local build. The arguments to the 'bitbake-hashserve' command have been updated accordingly. 3) The value to which BB_HASHSERVE should be set to enable a local hash equivalence server is changed to "auto" instead of "localhost:0". The latter didn't make sense when the local server was using a Unix domain socket. 4) Clients are expected to keep a persistent connection to the server instead of creating a new connection each time a request is made for optimal performance. 5) Most of the client logic has been moved to the hashserve module in bitbake. This makes it easier to share the client code. 6) A new bitbake command has been added called 'bitbake-hashclient'. This command can be used to query a hash equivalence server, including fetching the statistics and running a performance stress test. 7) The table indexes in the SQLite database have been updated to optimize hash lookups. This change is backward compatible, as the database will delete the old indexes first if they exist. 8) The server has been reworked to use python async to maximize performance with persistently connected clients. This requires Python 3.5 or later. (Bitbake rev: 1f404bd23335f6c5f6ca944c5be0b838ffb76c4d) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: runqueue/siggen: Optimise hash equiv queries

2019-09-16T22:02:45+00:00

We only have hash equivalence for setscene tasks so only query the server for those, reducing the number of connections needed. (Bitbake rev: 22082c7b3ca0cffcedb7d1d8c6681d35286376db) Signed-off-by: Richard Purdie

bitbake: Revert "bitbake: cooker: Ensure bbappends are found in stable order"

2019-09-16T22:02:45+00:00

This reverts commit 94c0c7f15c7a6244a8576ed948ffc21afb96ba82. This ignores the layer priority, making the issue much worse. E.g. I'm seeing a lot of failures caused by missing users, because base-passwd bbappends applied in unexpected order caused different passwd.master to be found in re-ordered FILESPATH. (Bitbake rev: 2dc862237dba82da37c8ac9289e0a21409b1305c) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: key-expansion: Don't refer to overrides

2019-09-10T14:18:06+00:00

Nowadays bitbake applies overrides dynamically, not at a single specific point in time during parsing. (Bitbake rev: 218431b0f7c97764cb2c0b79a3aadfe2007f490b) Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Correct description for _append/_prepend/_remove

2019-09-10T14:18:06+00:00

The effects of _append/_prepend/_remove are applied when a variable is expanded, not after parsing has completed. (Bitbake rev: f9b67433cb4fe5132ab2cf4a9c6bc078b42e1960) Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Improve the example for Removal (Override Style Syntax)

2019-09-07T12:08:54+00:00

* to better show how it works with spaces and multiple values (Bitbake rev: 89dd570ebd7046f5bce4a8b7f3b2b50b1cf65589) Signed-off-by: Herb Kuta Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: bitbake: cooker: Ensure bbappends are found in stable order

2019-09-07T12:08:54+00:00

Thanks to wildcards in bbappend filenames, it's possible to have multiple bbappends that apply to the same recipe in the same directory. In order to get sstate hits between different workspaces, we want to apply those bbappend files in a consistent order. Since readdir() returns files in a non-deterministic order between workspaces (based on inode number and/or time of creation), we'll need to sort its result in order to have any consistency. (Bitbake rev: 94c0c7f15c7a6244a8576ed948ffc21afb96ba82) Signed-off-by: Wes Lindauer Signed-off-by: Richard Purdie