]> code.ossystems Code Review - openembedded-core.git/commit
oeqa/oetest: oeSDKTest when run a command redirect env output to null
authorAníbal Limón <anibal.limon@linux.intel.com>
Thu, 4 Feb 2016 22:14:26 +0000 (16:14 -0600)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 10 Feb 2016 15:51:03 +0000 (15:51 +0000)
commit7defb10d10861501947b4a686510e957c72313e6
tree0a673107f729cec95de2eb60001351405310f83e
parent51782e5f77cb3f32a31a221c6e0f9b33cf3a33c9
oeqa/oetest: oeSDKTest when run a command redirect env output to null

Some tests are failing because the eSDK env load script shows a help
message on the output so redirect this to /dev/null.

There was a discussion with Paul Eggleton [1], he don't want to have env
variables to change the behaviour of what the env script needs to print
so redirect the output in oeSDK.run() method. I didn't agree because
it can hides another messages like error ones and with the variable you
can control what prints or not.

[1] http://lists.openembedded.org/pipermail/openembedded-core/2016-February/116744.html

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/lib/oeqa/oetest.py