]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/parselogs: Don't use cwd for file transfers
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 9 Sep 2016 12:19:02 +0000 (13:19 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 8 Nov 2016 23:03:21 +0000 (23:03 +0000)
commit64ff5be5909705395b2db8d64e8d2c2c76092e1c
treef1c03be4c2dcb0cad69e607b3fb745c3e5b77ca1
parentcc1b341b0a8e834a15c4efe107886ad366f7678c
oeqa/parselogs: Don't use cwd for file transfers

If you run:

MACHINE=A bitbake <image> -c testimage
MACHINE=B bitbake <image> -c testimage

and A has errors in parselogs, machine B can pick these up and cause
immense confusion. This is because the test transfers the log files
to cwd which is usually TOPDIR. This is clearly bad and this patch
uses a subdir of WORKDIR to ensure machines don't contaminate each
other.

Also ensure any previous logs are cleaned up from any existing
transfer directory.

(From OE-Core rev: ac8f1e58ca3a0945795087cad9443be3e3e6ead8)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/lib/oeqa/runtime/parselogs.py