openembedded-core.git/meta/lib/oeqa/utils/metadata.py, branch uninative-1.5 Mirror of openembedded-core oeqa.utils.metadata: include BB_NUMBER_THREADS and PARALLEL_MAKE 2017-01-19T22:45:46+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:46+00:00 97c07a55815c2fc3915705317b6f30d212fa1d45 Inlude values of BB_NUMBER_THREADS and PARALLEL_MAKE in the metadata. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Inlude values of BB_NUMBER_THREADS and PARALLEL_MAKE in the metadata.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: allow storing any bitbake config variables 2017-01-19T22:45:46+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:45+00:00 6e7e6e37664b0a86111272f5f6f4a4e1d0f23302 Make it possible to store any bitbake config variables in the metadata. Config values will be stored under a new config element in the xml report: <config> <variable name="MACHINE">qemux86</variable> </config> The value of MACHINE is moved there instead of having a dedicated <machine> element. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Make it possible to store any bitbake config variables in the metadata.
Config values will be stored under a new config element in the xml report:
    <config>
        <variable name="MACHINE">qemux86</variable>
    </config>

The value of MACHINE is moved there instead of having a dedicated
<machine> element.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: add bitbake revision information 2017-01-19T22:45:46+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:44+00:00 71ca7dab08fc500b231054249aacc90ae4aa85da [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: have layer name as an attribute in xml 2017-01-19T22:45:46+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:43+00:00 50ea44c19005b536a2791113f8b536fd10548ead Have the layer name as an attribute instead of of the name of the element itself. That is, have <layer name="layer_name"/> instead of <layer_name/>. A bit better XML design. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Have the layer name as an attribute instead of of the name of the
element itself. That is, have <layer name="layer_name"/> instead of
<layer_name/>. A bit better XML design.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: add commit count information 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:42+00:00 7757970bced4ecd6503991c0cf11f4d9158f650c Makes it easier to put the commits into a timeline. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Makes it easier to put the commits into a timeline.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: rename 'revision' to 'commit' 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:41+00:00 a6521b89e86ddba6bd646dd3974d7b0390323b56 Revision is a bit vague and could point to a tag, for example. Git commit objects are unambiguous and persistent so be explicit that the element should contain git commit hash. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Revision is a bit vague and could point to a tag, for example. Git
commit objects are unambiguous and persistent so be explicit that the
element should contain git commit hash.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: fix retrieval of git branch and revision 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:40+00:00 02d3ba17a8090bd088beb973980651d664f713bb Always return a valid branch name, or, '(nobranch)' if the current HEAD is detached. Also, always return the hash of the commit object that HEAD is pointing to. Previous code returned an incorrect branch name (or crashed) e.g. in the case of detached HEAD. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Always return a valid branch name, or, '(nobranch)' if the current HEAD
is detached. Also, always return the hash of the commit object that HEAD
is pointing to. Previous code returned an incorrect branch name (or
crashed) e.g. in the case of detached HEAD.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: drop 'unknown' git data elements 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:39+00:00 fce531c21f5e56d0f416b3405a0b0fc5ba567679 It's better just to not have the xml elements than to have elements with faux data. One could have git branch named 'unknown', for example. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
It's better just to not have the xml elements than to have elements with
faux data. One could have git branch named 'unknown', for example.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: re-organise distro information 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:38+00:00 0156ef46ccf5334ee72f0202f1089249c62af37b Use the same format, based on /etc/os-release, as for host distro information. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Use the same format, based on /etc/os-release, as for host distro
information.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.utils.metadata: re-organise host distro information 2017-01-19T22:45:45+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2017-01-13T13:12:37+00:00 98cad0b4063772dad94fea96edce1a5422256c32 Put all host distro data under one <host_distro> element. In addition take the data directly from /etc/os-release instead of the "lsb API". The /etc/os-release file is virtually ubiquitous, now, and using its field names and values provides a more standardized and extensible format. [YOCTO #10590] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Put all host distro data under one <host_distro> element. In addition
take the data directly from /etc/os-release instead of the "lsb API".
The /etc/os-release file is virtually ubiquitous, now, and using its
field names and values provides a more standardized and extensible
format.

[YOCTO #10590]

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>