openembedded-core.git/meta, branch thud

core-image-sato-sdk-ptest: Tweak size to stay within 4GB limit

2019-05-18T05:05:59+00:00

Adding the valgrind debug symbol information caused the genericx86-64 image to
overflow the 4GB boundary. Tweak the sizes to avoid autobuilder failures yet
leave enough space all the tests still run successfully.

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

core-image-sato-sdk-ptest: Try and keep image below 4GB limit

2019-05-18T05:05:52+00:00

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/targetcontrol.py: fix qemuparams not work in runqemu with launch_cmd

2019-05-18T04:31:14+00:00

As runqemu with launch_cmd means directly run the command, don't need set
rootfs or env vars.

Since commit [a847dd7202 runqemu: Let qemuparams override default settings]
applied in oe-core, if launch_cmd contains "qemuparams='***'", it does not
work, which is overridden by latter qemuparams="-serial tcp:127.0.0.1" in
QemuRunner.launch();

So we set qemuparams as a parameter in runqemu, the fix makes it work

Signed-off-by: Hongxu Jia 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/target/ssh: Replace suggogatepass with ignoring errors

2019-05-18T04:31:01+00:00

We continued to see encoding problems with ssh commands run in oeqa. After much
research the conclusion was we should use ignore the errors since some occasional bad
locale encoding is better than the unicode decoding issues we were seeing which crashed
large parts of tests.

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/sdk: use bash to execute SDK test commands

2019-05-18T04:30:51+00:00

The commands only work with with bash. If /bin/sh is
dash like in Debian, the command execution fails with
errors like:

Standard Output: /bin/sh: 5: export: --sysroot: bad variable name

and all SDK tests fail.

Signed-off-by: Mikko Rapeli 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/concurrenttest: Patch subunit module to handle classSetup failures

2019-05-18T04:30:39+00:00

Currently setupClass errors were not being mapped back to the failing tests
and they were hence being marked as UNKNOWN and the test statistics were
inaccurate.

This is because whilst the errors were being encoded into the test results
stream, the decoder doesn't cope with an error outside a testStart event.

We patch in an addError handler to the outsideTest parser so that this
does get handled in a way similar to the non-concurrent case.

It would be nice if we didn't have to do this but there doesn't seem
to be any other way to fix this other than forking subunit.

We also make a minor change so another of our changes can cope with
tests without a start time.

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/runner: Fix subunit setupClass/setupModule failure handling

2019-05-18T04:30:26+00:00

The string format for subunit setupClass/setupModule failures is slightly
different, tweak the regex to correctly handle both cases.

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/core/runner: Handle unexpectedSucesses

2019-05-18T04:30:06+00:00

Instead of showing:
RESULTS - ptest.PtestRunnerTest.test_ptestrunner - Testcase 1600: UNKNOWN (32.30s)

map unexpectedSuccesses to PASSED and improve the way they're displayed. We
expect/allow ptest runner to fail but if it passes we should handle it correctly.

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/ssh: Avoid unicode decode exceptions

2019-05-18T04:19:25+00:00

This code really needs to be rewritten to not split potential
multibyte characters, for now work around it to avoid exceptions like:

  File "/home/pokybuild/yocto-worker/qa-extras2/build/meta/lib/oeqa/core/target/ssh.py", line 211, in run
    data = reader.read(1024, 4096)
  File "/usr/lib64/python3.6/codecs.py", line 503, in read
    newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 0: invalid start byte

Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oeqa/core/runner: dump stdout and stderr of each test case

2019-05-18T04:19:10+00:00

Some CI pipelines might perform further processing of the test output
(for instance, to plot some metrics into a chart). However, Since `thud`
we switched away from the XML-based jUnit reporting, and at the same
time we lost the ability of collecting the stdout and stderr of the
various tests.

We now restore this functionality by adding `stdout` and `stderr` keys
to the JSON reports. This behavior is off by default; in order to enable
it, one must set the `TESTREPORT_FULLLOGS` variable in the bitbake
configuration.

Signed-off-by: Alberto Mardegan 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster