linux/poky.git, branch yocto-2.5.3

build-appliance-image: Update to sumo head revision

2019-03-27T23:22:02+00:00

(From OE-Core rev: 0a2db923fd17019d07d88204b355aa46590f0b97) Signed-off-by: Richard Purdie

oeqa/utils/gitarchive: Handle case where parent is only on origin

2019-03-27T23:21:47+00:00

The parent code currently assumed that any parent branch is locally checked out which may not be the case. Use the local branch by default but fall back to the origin. This also means removing the later saftey check as the branch may not exist locally. This fixes the autobuilder resulttool test pushing code. (From OE-Core rev: 633e024f5d492ba38debf745b59813f6a2f4a3f0) Signed-off-by: Richard Purdie

build-appliance-image: Update to sumo head revision

2019-03-26T15:54:21+00:00

(From OE-Core rev: ece8242187558011940d7c6762b64c7116e38689) Signed-off-by: Richard Purdie

poky.conf: Bump version for 2.5.3 sumo release

2019-03-26T15:54:12+00:00

(From meta-yocto rev: c19ec95877614314ab236fd89d9b5055f33de0c4) Signed-off-by: Richard Purdie

yocto-uninative: Update to 2.4

2019-03-26T15:38:28+00:00

This supports glibc 2.29 which is appearing in distros like Ubuntu 19.04 (From OE-Core rev: 661ac7ed164965690a4334d372bf22f04c3bfd3a) Signed-off-by: Richard Purdie [Fixed up for Sumo context; no aarch64] Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oe-build-perf-report/gitarchive: Move common useful functions to library

2019-03-26T15:38:28+00:00

These functions can be reused by the resulttool code so move to the common function library for this purpose. (From OE-Core rev: c66f848938c04e133259c5b6903dc592866ab385) (From OE-Core rev: 94a3ca85d30fc957f8f01a216a75342be49f9143) Signed-off-by: Richard Purdie

scripts/oe-git-archive: Separate out functionality to library function

2019-03-26T15:38:28+00:00

This turns the core of the script into a library function. Ultimately this will let us call that code with custom 'keywords' rather than relying on the data parsed from bitbake metadata which can't be used when archiving historical results. (From OE-Core rev: 4820ca2b0850e29b04a4fd5659a6e9837d6714d0) (From OE-Core rev: ab5d49ba8bb02410fb9f3024f98ff19a04acb3ca) Signed-off-by: Richard Purdie

oe-build-perf-report: Fix missing buildstats comparisions

2019-03-26T15:38:28+00:00

Integers were being compared to strings leading to missing buildstats comparision data. Fix this. (From OE-Core rev: 2dbbf598192ae2b3aa488df042f56aa6c6634a00) (From OE-Core rev: e8651b2e01db0777b23a0359f9413c3b27bae77f) Signed-off-by: Richard Purdie

oe-build-perf-report: Improve branch comparision handling

2019-03-26T15:38:28+00:00

When comparing branches, correctly filter the revisions corresponding to the specific branch specified. Also use the commit numbers as a way to gauge spatially related commits for comparision meaning comparisions for out of order build revisions becomes meaninful. This should improve the reporting for autobuilder generated builds. Also improve the branch option help text. (From OE-Core rev: 9f6f4ab6eec9dca07af7f53da5f737a6167bfb38) (From OE-Core rev: d6645c4c931565d62df85db0fa71f15d51265828) Signed-off-by: Richard Purdie

oe-build-perf-report: Allow commits from different branches

2019-03-26T15:38:28+00:00

The code won't currently allow comparisions of two commits on different branches even if the commits are specified by their hashes. This updates the code to search two branches for any relavent commits, hence allowing comparisions to be made. A particularly useful case is master vs. master-next for example. (From OE-Core rev: 2d835bb1570c515ae501442f3ce19fae8e249b27) (From OE-Core rev: c6351550a9bff3e0b0e3d3c0baefed4041c47b33) Signed-off-by: Richard Purdie