linux/poky.git/meta/lib/oeqa/runtime, branch uninative-1.7

oeqa/runtime: Replace buildiptables for buildlzip on runtime tests

2017-07-08T12:34:46+00:00

Buildiptables test cases are conflicting with images built with “musl” as standard C library, in order to avoid those issues lzip package was selected to be used on the tests as this does not have any "musl" dependency. This patch is applicable for testimage tests [YOCTO # 11713] (From OE-Core rev: 41683e0ab316049e28b1f4ceaf39f0fe17722d92) Signed-off-by: Jose Perez Carranza Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/runtime/context.py: Add support to specify port in target_ip

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

(From OE-Core rev: 7fe4c074611eb21abdf811d8f216d4df7ab6a3ea) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

oeqa/runtime/case: Don't use OEQA framework internal methods

2017-06-02T12:36:14+00:00

The OEQA framework has internal methods for provide functionality in decorators so Test components aren't expected to override it. Use the base unittest methods for setUp and tearDown. (From OE-Core rev: 21df9f0f6d6272adc6131cdc113000a5e6ac9d46) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

parselogs: whitelist failed to enable keyboard error on intel-corei7-64

2017-05-11T15:59:19+00:00

This error is seen on the Braswell RVP platform we have been using for testing. The error is caused by atkbd.c keyboard driver, which is only for AT and PS/2 keyboards. I tested a PS/2 keyboard with the board, which worked fine, and the board does not have a separate AT connector, so this error won't cause any functional issues. [YOCTO #10110]. (From OE-Core rev: c9f83639242313ca04ec36b49602a8464e10dae8) Signed-off-by: California Sullivan Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

parselogs: whitelist bluetooth firmware load error for intel-corei7-64

2017-05-11T15:59:19+00:00

The NUC6 has issues bringing up Bluetooth early in the boot sequence. We see: [ 4.091790] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 4.097326] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 4.145317] Bluetooth: hci0: Failed to send firmware data (-38) Followed by this later on: [ 11.509870] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 11.509988] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 13.090308] Bluetooth: hci0: Waiting for firmware download to complete [ 13.090829] Bluetooth: hci0: Firmware loaded in 1549114 usecs [ 13.090987] Bluetooth: hci0: Waiting for device to boot [ 13.101958] Bluetooth: hci0: Device booted in 10818 usecs Bluetooth does successfully come up and the firmware is loaded. This behavior is consistent across all kernels I've tested. [YOCTO #10628]. (From OE-Core rev: 045ee89342ea8ce16e78fea9f1c73d978d66a337) Signed-off-by: California Sullivan Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir

2017-04-06T09:13:39+00:00

Rather than hard-coding the tmpdir for TargetBuildProject to /tmp allow the parent's default handling to define an appropriate tmpdir. (From OE-Core rev: 901659a51cd53625a93f57a9c5865e90a07ec09d) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

runtime/dnf : Add ID to the dnf test cases

2017-04-05T22:22:12+00:00

Add the corresponding Testopia ID to the test cases for dnf (From OE-Core rev: 434b48566f2febcc5bd5d6cd9c04788f008ffce1) Signed-off-by: Jose Perez Carranza Signed-off-by: Richard Purdie

oeqa/runtime/cases: Migrate underscore cases

2017-04-01T07:14:57+00:00

There were two missing cases to be migrated to the new framework: _qemutiny and _ptest. qemutiny was straightforward. ptest on the other hand wasn't working even in previous releases; it has been migrated from smart to dnf, and how ptest packages are gathered to be installed, adapted to use unicode, and removed a lot of code that wasn't needed anymore. (From OE-Core rev: ee7c19546b686e852d01df25143504d9798d10d6) Signed-off-by: Mariano Lopez Signed-off-by: Richard Purdie

oeqa: use WORKDIR/oe-testimage-repo to look for RPM packages

2017-03-23T13:19:49+00:00

Using RPM deploy dir was causing errors when pre-built images were used with these steps: https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project [YOCTO #11173] (From OE-Core rev: f633abed51ed19522340b1d923ffc12ed7e291d6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/lib/oeqa: change sdk test from cvs to cpio

2017-03-22T11:35:21+00:00

We currently fetch,configure,build, and install cvs as our test for the sdk. cvs unfortunately, requires a default editor in order to run. The change in 94790a8254d6 that checks to see if you have something like vi installed is fragile since you may have a different default editor. This patch switches from using cvs as a test to using cpio. cpio also uses autotools so the functionality tested is equivalent. (From OE-Core rev: 233d36b0382a8b2e430c3377e50885d1a0c3ba21) Signed-off-by: brian avery Signed-off-by: Ross Burton Signed-off-by: Richard Purdie