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 /meta/classes/testsdk.bbclass | |
| parent | 51782e5f77cb3f32a31a221c6e0f9b33cf3a33c9 (diff) | |
| download | openembedded-core-contrib-7defb10d10861501947b4a686510e957c72313e6.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
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes/testsdk.bbclass')
0 files changed, 0 insertions, 0 deletions