]> 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>
Fri, 9 Sep 2016 12:21:18 +0000 (13:21 +0100)
commitac8f1e58ca3a0945795087cad9443be3e3e6ead8
tree97fd49969dab1eed4a1c647a23728826e0784258
parent4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac
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.

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