Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=hardknott-3.3.3 2021-02-10T23:48:16+00:00 2021-02-10T23:48:16+00:00 Joshua Watt JPEWhacker@gmail.com 2021-02-09T15:50:21+00:00 urn:sha1:75f87db413f3659fee18eff389b7b339b01cce15 The bitbake logger overrode the definition of the debug() logging call to include a debug level, but this causes problems with code that may be using standard python logging, since the extra argument is interpreted differently. Instead, change the bitbake loggers debug() call to match the python logger call and add a debug2() and debug3() API to replace calls that were logging to a different debug level. [RP: Small fix to ensure bb.debug calls bbdebug()] (Bitbake rev: f68682a79d83e6399eb403f30a1f113516575f51) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-08-26T08:05:38+00:00 Chris Laplante chris.laplante@agilent.com 2020-08-25T16:51:41+00:00 urn:sha1:77441a08d4ba27996a651651e65f63af76e2503e Now that compat.py just imports Python standard library stuff, get rid of the layer of indirection. (Bitbake rev: e2be6defbb9fcf25f9df04c3b452d0dba48dfd03) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020-01-19T13:31:05+00:00 Chris Laplante chris.laplante@agilent.com 2020-01-16T16:28:05+00:00 urn:sha1:1b1a533133e68b1850cd4194d51b53e819fa9183 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 <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-05-04T09:44:10+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2019-05-01T10:47:13+00:00 urn:sha1:cf9c0be3f69135633c0800d95e77677569a79839 With the introduction of SPDX-License-Identifier headers, we don't need a ton of header boilerplate in every file. Simplify the files and rely on the top level for the full licence text. (Bitbake rev: 695d84397b68cc003186e22f395caa378b06bc75) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-05-04T09:44:04+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2019-04-30T10:05:26+00:00 urn:sha1:79834a71447f89c52c6c9ad62c9bcbf9b8e0e05b This adds the SPDX-License-Identifier license headers to the majority of our source files to make it clearer exactly which license files are under. The bulk of the files are under GPL v2.0 with one found to be under V2.0 or later, some under MIT and some have dual license. There are some files which are potentially harder to classify where we've imported upstream code and those can be handled specifically in later commits. The COPYING file is replaced with LICENSE.X files which contain the full license texts. (Bitbake rev: ff237c33337f4da2ca06c3a2c49699bc26608a6b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-01-08T11:16:03+00:00 Joshua Watt jpewhacker@gmail.com 2019-01-03T16:36:11+00:00 urn:sha1:cea00c128311539a870d0cd233366480ddaff605 Under heavy load with process delays, sqlite can issues a "locking protocol" error (SQLITE_PROTOCOL). Unfortunately, it is impossible to distinguish between actual locking protocol errors and this race condition, so they best that can be done is to retry the operation when the error is detected. [YOCTO #13108] (Bitbake rev: 93cd15644f9d12b38abea276fee7b5bade0276df) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-12-08T17:17:37+00:00 Joshua Watt jpewhacker@gmail.com 2018-12-07T21:59:28+00:00 urn:sha1:66318c5831e91f571c167b9d33150523bd30ee95 The configuration of the sqlite database can timeout due to locking under heavy load and should be subject to the same retry logic as the other statements. [YOCTO #13069] (Bitbake rev: 5a2a95b0396e39662968690b3065d2f88167a71c) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-12-07T12:38:58+00:00 Joshua Watt jpewhacker@gmail.com 2018-12-04T03:42:33+00:00 urn:sha1:7509b5ee0555d1cc8729210e62e122da70b9d080 Turns off the shared cache. It isn't a significant factor in performance (now that WAL is enabled), and is a really bad idea to have enabled in processes that fork() (as bitbake it prone to do). [YOCTO #13030] (Bitbake rev: 71b427bf01374973a971c10cb64024c8ef2a11eb) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-12-07T12:38:58+00:00 Joshua Watt jpewhacker@gmail.com 2018-12-04T03:42:32+00:00 urn:sha1:09b4de78f2ae6fce4d3ef1992d185ec2aa12f475 Enabling the write ahead log improves database reliability, speeds up writes (since they mostly happen sequentially), and speeds up readers (since they are no longer blocked by most write operations). The persistent database is very read heavy, so the auto-checkpoint size is reduced from the default (usually 1000) to 100 so that reads remain fast. [YOCTO #13030] (Bitbake rev: 79100fa67539f9654af9bf6d3e6842eb5c12e989) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-12-07T12:38:58+00:00 Joshua Watt jpewhacker@gmail.com 2018-12-04T03:42:31+00:00 urn:sha1:549eccc0db48507dfda25aec1d8b0b5b8e1b3d16 Constructs the "key" column in the persistent database as a non-NULL primary key. This significantly speeds up lookup operations in large databases. [YOCTO #13030] (Bitbake rev: f5ba7775cfcb90401522d977cc66fe0f5aeb7a66) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>