linux/poky.git/meta/lib/oeqa, branch rocko

make-mod-scripts/kernel-devsrc: Fix objtool issues

2018-08-15T09:22:44+00:00

Kernels which use tools/objtool can now fail when building external modules due to objtool being missing, the generated files can also cause problems for kernel-devsrc. Ensure objtool is generated in make-mod-scripts by also calling "make prepare". For devsrc, delete the generated binaries since they'd be native binaries and unsuitable for the target. The oeqa kernel module tests also need to have the additional "make prepare" step added. (From OE-Core rev: 52fd2993784b4218f5df4f343e7da45d964df305) Fixes [YOCTO #12860] (From OE-Core rev: 49b208fc7b3d52826ba57a86ed52bc30e181ff78) Signed-off-by: Richard Purdie [Tweaked to add "make prepare" to module-base.bbclass instead of make-mod-scripts.bb] Signed-off-by: Anuj Mittal Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/runtime/buildcpio: Use our own mirror for source

2018-01-06T10:13:57+00:00

We see occasional network glitches which break this test. Use our own mirror (which has a .gz instead of .bz2) to avoid the errors, we're not trying to test network connectivity. (From OE-Core rev: 01df65be2ae4bc337e10babeb9c2394d71ddff84) Signed-off-by: Richard Purdie

qemurunner: Simplify binary data handling

2017-12-04T17:24:00+00:00

I have concerns that bad timing of the flow of data from the logger might corrupt the output due to the way binary strings are handled in qemurunner. This simplifies the code to do the same thing it did before but much more safely. (From OE-Core rev: 20bc247316ab915465a4b1add6d09b48e07202ac) Signed-off-by: Richard Purdie (cherry picked from commit 1e87283e92a2765bb5d54d17138b208bc395953b) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/runner: Pass the value of buffer, don't force to True

2017-12-04T17:23:58+00:00

The value could be False in which case we should pass that through. (From OE-Core rev: 5b4b7bfe33630d73b5b53fc754cd45563fcbfd4d) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa: Markup further tests for stdout/stderr buffering

2017-12-04T17:23:58+00:00

This further cleans up the output of oe-selftest so that runqemu output is hidden unless tests fail. (From OE-Core rev: 22f224965ac93da0b37affc4998fc0644f14462d) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/target/ssh: Drop command/output logging to debug level

2017-12-04T17:23:58+00:00

This ensures the console is kept clear of confusing output but that the main logs contain good debugging information. (From OE-Core rev: 3727fae1e420a60ef8c62da546e1065045b163ff) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa: Clean up logger handling

2017-12-04T17:23:58+00:00

The logger handling in oeqa was confused at best. This patch: a) Passes in a logger through various qemu runner pieces b) Uses that logger consistently in the code c) Creates a logger for QemuRunner outside the bitbake namespace meaning we don't conflict with the tinfoil logging changes The result of this is more consistency. For runtime tests in testimage, the logs always contain the debug info, nothing is shwon on the console. For the oe-selftests, logs are intercepted and only shown if the test fails. (From OE-Core rev: ba8babc45141891d0624f9a181a580fa416e87ec) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/qemurunner: Use logger.debug, not logger.info

2017-12-04T17:23:58+00:00

Bitbake logs info messages to the console. These messages are really there as debugging information. At the debug level, they will be shown in failure logs and in the task logs but not on the console which is what we want in this case. (From OE-Core rev: 5c1cdd4f3ea59a202fff853e0390b9aa5859dc74) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/targetcontrol: Drop unused get_target_controller function

2017-12-04T17:23:58+00:00

This funciton appears completely unused, drop it. (From OE-Core rev: 31ccc70c4ea58e3781ea14eb534e00e9e06e131a) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/runqemu: Only show stdout/stderr upon test failure

2017-12-04T17:23:57+00:00

In general we don't need to see the output of runqemu however if it fails we do. Use the buffer option that already exists in TestResult but allow us to trigger it on a per test basis. (From OE-Core rev: 1826a8cb8cf4c51307003617864d2ffab273eb0b) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie