linux/poky.git/scripts/oe-selftest, branch 2.7_M2

scripts/oe-{self,}test: Logger change default stream to stdout

2017-06-06T18:02:44+00:00

By default python logging module uses stderr as default stream for output but is unix-like to use stdout instead, so change it. (From OE-Core rev: 986452c410a958e339f31f8c05461c18a1a15eb5) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

scripts/oe-selftest: Migrate to new framework into oeqa.selftest.context

2017-06-06T18:02:43+00:00

The new OEQA framework aims to re-use code into the different Test components. The previous oe-selftest implements it-self loading, run, and list test cases in a non-standard way (unittest base) and other functionalities like logging that is now on oeqa core. This ends on a compact oe-selftest script. All needed command line options was migrated but there are some of them pending of implementation and others deprecated. Deprecated options: list-tags: The tag functionality into the old oeqa framework isn't work, the selftest doesn't has tag decorators. {run, list}-tests-by: Ambiguos options it accepts all the posibilites module, class, name, id or tag. Remaining to implement: coverage: It enables covrage reports over a test run, currently isn't on on use and some bugs [1], i filed a bug to add support to OEQA core module in this way other Test components could enable it. repository: It push XML results into a git repository and isn't in use, i filed a bug to implement this into OEQA core module. [2] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11582#c0 [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11583#c0 (From OE-Core rev: 3b2a20eee4a39f40287bf67545839eaa09fc892d) Signed-off-by: Leonardo Sandoval Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

scripts/oe-selftest: Move {add,remove}_include files to case

2017-06-06T18:02:43+00:00

The oe-selftest creates include files to store custom configuration to make specific tests, every class executes a different test and may be uses custom configuration. So move to case class in order to simplify oe-selftest script and later implement later a build folder per class. (From OE-Core rev: 1130b40c3dfa65e7ece08a95b3941e4d1d20bcf0) Signed-off-by: Leonardo Sandoval Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

oe-selftest: Error if known problem variables are set

2017-04-13T09:54:10+00:00

Setting SANITY_TESTED_DISTROS or PRSERV_HOST are known to break oe-selftest. Rather than have the user experience this, refuse to execute unless the environment is correct. Ideally we'd try and unset these but that is a more invasive change and this at least makes people aware of the problem. [YOCTO #11292] (From OE-Core rev: 0c9b981e88c76da316e76f17e6da3a03b87c5008) Signed-off-by: Richard Purdie

selftest: automatically add the meta-selftest layer

2017-01-23T12:05:22+00:00

adding the meta-selftest layer is a small bump you always encounter when you want to run selftest. Adding an automatic procedure to include the layer if it is not yet present. (From OE-Core rev: b5000dd7b1d74d5dfede869ffa75ed87f5a8553c) Signed-off-by: Benjamin Esquivel Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-selftest: Error if the user has buildhistory enabled

2017-01-20T11:53:49+00:00

buildhistory interfers with various tests so error if the user has it enabled, hence avoiding time spent running the tests only for them to fail. For example, if there is an sstate cache and something comes from that cache, you can get a "version went backwards" warning from buildhistory which would then change the outcome of a test. Its safer/easier to disable it. (From OE-Core rev: 941ec7c50c30052e346e72fef2920135dba89a21) Signed-off-by: Richard Purdie

oeqa.utils.metadata: allow storing any bitbake config variables

2017-01-19T22:47:22+00:00

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: qemux86 The value of MACHINE is moved there instead of having a dedicated element. [YOCTO #10590] (From OE-Core rev: 6e7e6e37664b0a86111272f5f6f4a4e1d0f23302) Signed-off-by: Markus Lehtonen Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa.utils.metadata: rename 'revision' to 'commit'

2017-01-19T22:47:22+00:00

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] (From OE-Core rev: a6521b89e86ddba6bd646dd3974d7b0390323b56) Signed-off-by: Markus Lehtonen Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa.utils.metadata: drop 'unknown' git data elements

2017-01-19T22:47:22+00:00

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] (From OE-Core rev: fce531c21f5e56d0f416b3405a0b0fc5ba567679) Signed-off-by: Markus Lehtonen Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa.utils.metadata: re-organise distro information

2017-01-19T22:47:22+00:00

Use the same format, based on /etc/os-release, as for host distro information. [YOCTO #10590] (From OE-Core rev: 0156ef46ccf5334ee72f0202f1089249c62af37b) Signed-off-by: Markus Lehtonen Signed-off-by: Ross Burton Signed-off-by: Richard Purdie