summaryrefslogtreecommitdiffstats
path: root/meta/classes/testsdk.bbclass
diff options
context:
space:
mode:
authorAníbal Limón <anibal.limon@linux.intel.com>2016-02-04 16:14:26 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-10 16:06:23 +0000
commit7181da7192d83a43294d80edd61a1dce5543bc71 (patch)
tree267d82cb1a01ab227ff673b1ddd7262c3c0616a1 /meta/classes/testsdk.bbclass
parentf3c2ce27390b008b210cc439b8130942eb380ce9 (diff)
downloadpoky-7181da7192d83a43294d80edd61a1dce5543bc71.tar.gz
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 (From OE-Core rev: 7defb10d10861501947b4a686510e957c72313e6) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/testsdk.bbclass')
0 files changed, 0 insertions, 0 deletions