From: Aníbal Limón Date: Thu, 4 Feb 2016 22:14:26 +0000 (-0600) Subject: oeqa/oetest: oeSDKTest when run a command redirect env output to null X-Git-Tag: 2016-4~1035 X-Git-Url: https://code.ossystems.io/gitweb?a=commitdiff_plain;h=7defb10d10861501947b4a686510e957c72313e6;p=openembedded-core.git 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 Signed-off-by: Ross Burton --- diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py index 16705cc3fe..47ea3b259f 100644 --- a/meta/lib/oeqa/oetest.py +++ b/meta/lib/oeqa/oetest.py @@ -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