linux/poky.git/bitbake/lib/bb/ui/buildinfohelper.py, branch 2.3_M2

bitbake: toaster: buildinfohelper Clarify log message for build history

2016-11-30T15:48:10+00:00

(Bitbake rev: 5accd6c4d1dcdf6609b4ed25c2b5e4faaf7f0909) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper fix _get_layer_version_for_dependency

2016-11-30T15:48:10+00:00

This function is simplified by not trying to handle replacing the regex and just compiling and using it for matching. - Fix typo in logger output with undefined variable - Fix pyflake errors (Bitbake rev: ea298ece8d678889cd5bcde46e00545e9a73edb9) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper Simplify layer event to toaster layer function

2016-11-30T15:48:10+00:00

Simplify the layer event information to layer version object in toaster function. Previously this attempted many different methods of trying to obtain the correct layer from toaster by manipulating the data from the event or the data from the known layers to try and match them together. We speed up and simplify this process by making better use of django's orm methods and by working down the most likely matching methods in order of accuracy. [YOCTO #10220] (Bitbake rev: 6935cc06974ea94c9971ede89b6e8f0eae9c195b) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper toaster-custom-images layer

2016-11-30T15:48:10+00:00

This fixes the unidentified layers issue by making the toaster-custom-images layer a local layer. By doing this we also fix the git assumptions made for the local layers which stop recipes and other meta data being associated with them. This also removed some of the special casing previously needed when we didn't have the concept of a local (non git) layer. Also rename created flag var to a have a different var for each returned value so that the same value isn't used multiple times. [YOCTO #10220] (Bitbake rev: ba5332d4960d7f4f79aef63136796e2fa67284e3) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper Handle regex paths

2016-11-04T12:50:55+00:00

We were presuming that all the layer dependency information was of the form "^/path/to/layer" to we were just stripping the leading "^" off of the layer information when we were matching the layer priorities to the toaster database. This patch splits out the priorities layer match which gets a regex from the task/recipe match which is gets a path. (Bitbake rev: e23b574fe52f416184ee43838b8ab28b5b8eb71d) Signed-off-by: brian avery Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper: Use correct way to get message from LogMessage

2016-10-06T10:41:48+00:00

Use the correct method to get a message value from the LogMessage object rather than constructing it ourselves which is not recommended. This causes an exception when the msg contains a '%' such as when there are wildcards in file names (something2.%.bbappends) (Bitbake rev: 11b3b6a7087554d14a2812a9ae463dce740b879e) Signed-off-by: Michael Wood Signed-off-by: bavery Signed-off-by: Richard Purdie

bitbake: toaster: check if file exist

2016-09-30T15:52:22+00:00

Buildinfohelper assumes that all files mentioned in manifest exist in deploy/ directory, which is not always the case. Toaster crashes with OSError trying to call os.stat on non-existing file. Checking if file exists before processing it should fix this. [YOCTO #10185] (Bitbake rev: 54565e7ca84d2722a2454e7fa52cda564b28b527) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper local layer don't construct path using git info

2016-09-21T20:58:06+00:00

When the layer is local source don't try and work out the location of the layer by using the git information (getGitCloneDirectory) [YOCTO #10199] (Bitbake rev: 3dfea5214d4bd006e26630e5024774ecb84ea527) Signed-off-by: Michael Wood Signed-off-by: bavery Signed-off-by: Richard Purdie

bitbake: toaster: unlock BuildEnvirnoment when build is done

2016-09-21T20:58:06+00:00

There is no need to lock build environment before changing build status as this operation is very fast. However, there is a need to unlock it after changing build status. Explicitly unlocked BuildEnvironment after build reaches final status SUCCEEDED, FAILED or CANCELLED. This should allow runbuilds process to pickup next build faster. (Bitbake rev: faa88272d656640c039572c5c8f3e6c56535b6f7) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: notify runbuilds when build status changes

2016-09-21T20:58:06+00:00

Called signal_runbuilds API when build is scheduled, cancelled or finished to notify runbuilds process about builds status change. [YOCTO #8918] (Bitbake rev: fe08f0fa4b328908e73695ebbceca87bc86a49f9) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie