diff options
| author | Aníbal Limón <anibal.limon@linux.intel.com> | 2016-02-04 16:14:26 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-02-10 15:51:03 +0000 |
| commit | 7defb10d10861501947b4a686510e957c72313e6 (patch) | |
| tree | 0a673107f729cec95de2eb60001351405310f83e | |
| parent | 51782e5f77cb3f32a31a221c6e0f9b33cf3a33c9 (diff) | |
| download | openembedded-core-7defb10d10861501947b4a686510e957c72313e6.tar.gz openembedded-core-7defb10d10861501947b4a686510e957c72313e6.tar.bz2 openembedded-core-7defb10d10861501947b4a686510e957c72313e6.zip | |
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>
| -rw-r--r-- | meta/lib/oeqa/oetest.py | 2 |
1 files changed, 1 insertions, 1 deletions
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 |