openembedded-core.git/meta, branch uninative-1.6

classes: Replace "if test" file tests with POSIX file tests

2017-03-27T10:08:28+00:00

In entire meta/classes/ directory, replace shell tests of the form
"if test -? ..." with POSIX tests of the form "if [ -? ...

Signed-off-by: Robert P. J. Day 
Signed-off-by: Richard Purdie

autotools.bbclass: Replace "grep ... >/dev/null" with "grep -q"

2017-03-26T23:07:36+00:00

For aesthetic style reasons, use "grep -q" instead of ">/dev/null".

Signed-off-by: Robert P. J. Day 
Signed-off-by: Richard Purdie

mdadm: update criteria to build with corosync

2017-03-26T12:17:04+00:00

mdadm only works with corosync 2.x which provides header file corosync/cmap.h.
If build mdadm with corosync 1.x, it fails with:

| member.c:12:27: fatal error: corosync/cmap.h: No such file or directory
|  #include 
|                            ^

Build with corosync only header file corosync/cmap.h exists.

Ref:
https://github.com/neilbrown/mdadm/blob/master/mdadm.h#L63

Signed-off-by: Kai Kang 
Signed-off-by: Richard Purdie

runtime-test.py: fix typo

2017-03-26T12:17:03+00:00

roofs -> rootfs.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

image_types: perform fsck on created ext image

2017-03-26T12:17:03+00:00

When performing a file system check, the image created with mkfs will
trigger Pass 3A ('Optimizing directories') which turns the file system
into state "changed" (EXT2_FLAG_CHANGED).

This will let fsck request a reboot by setting the return code flag "2".

The result of this is that each ext-image built with oe-core will
trigger a reboot during the first time an fsck is triggered.

A common case where this might occur is when fsck detects having
a future superblock write time. This always happens when booting a
newly created ext4 rootfs with a target that does not have a recent time
set.

This patch moves the initial fsck run that performs the optimization
from the target to the host system and thus prevents the target from
performing an avoidable reboot.

Signed-off-by: Enrico Jorns 
Signed-off-by: Ulrich Ölmann 
Signed-off-by: Richard Purdie

oeqa.buildperf: limit the length of error output

2017-03-26T12:17:03+00:00

Limit the length of error logs to 40 lines. We don't need to
show/archive thousands of lines of bitbake logs if an error occurs.

Signed-off-by: Markus Lehtonen 
Signed-off-by: Richard Purdie

oeqa.utils.commands: limit runCmd exception output

2017-03-26T12:17:03+00:00

Make it possible to limit the length of output lines shown in runCmd
exceptions. E.g when running bitbake we easily get thousands of lines of
log output, where only the last few (tens) are interesting or relevant
when an error occurs.

Signed-off-by: Markus Lehtonen 
Signed-off-by: Richard Purdie

oe-build-perf-test: sum rusage in buildstats

2017-03-26T12:17:03+00:00

Instead of separate rusage and child rusage values, only store their sum
value in buildstats. This is a big reduction in data footprint without
really losing any interesting data.

Also, utilize OrderedDict to order data more logically.

[YOCTO #10582]

Signed-off-by: Markus Lehtonen 
Signed-off-by: Richard Purdie

oe-build-perf-test: pack all buildstat in one file

2017-03-26T12:17:02+00:00

Write out all buildstats into one big json file, instead of using
multiple per-measurement files. Individual buildstats will be indexed
using "." as the key. Also, changes the
per-testcase working directories into temporary directories that will be
removed after test execution as there are no more per-testcase data files
to store permanently.

[YOCTO #10582]

Signed-off-by: Markus Lehtonen 
Signed-off-by: Richard Purdie

valgrind: correct the comparison logic in vg_regtest

2017-03-26T12:17:02+00:00

do_diffs in the vg_regtest script compares the actual test output
against the expected test output and returns 0 if it matches.

Previous upgrade modified the return value of do_diffs() and that
resulted in ptest failures.

[YOCTO #8471]

Signed-off-by: Maxin B. John 
Signed-off-by: Richard Purdie