sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Aníbal Limón 2016-02-04 16:14:26 -06:00 committed by Richard Purdie
parent f3c2ce2739
commit 7181da7192
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
meta/lib/oeqa/oetest.py
View File

@ -124,7 +124,7 @@ class oeSDKTest(oeTest):
return False
def _run(self, cmd):
return subprocess.check_output(". %s; " % self.tc.sdkenv + cmd, shell=True)
return subprocess.check_output(". %s > /dev/null; %s;" % (self.tc.sdkenv, cmd), shell=True)
def getmodule(pos=2):
# stack returns a list of tuples containg frame information