On Fri, 2015-09-18 at 12:05 +0100, Burton, Ross wrote:
>
> On 17 September 2015 at 21:38, Benjamin Esquivel <
> benjamin.esqui...@linux.intel.com> wrote:
> > put the import of pexpect around a try statement so it can tell you
> > why it failed to import when in a system that has the module
> > unr
On Friday 18 September 2015 12:05:35 Burton, Ross wrote:
> On 17 September 2015 at 21:38, Benjamin Esquivel <
>
> benjamin.esqui...@linux.intel.com> wrote:
> > put the import of pexpect around a try statement so it can tell you
> > why it failed to import when in a system that has the module unrea
On 17 September 2015 at 21:38, Benjamin Esquivel <
benjamin.esqui...@linux.intel.com> wrote:
> put the import of pexpect around a try statement so it can tell you
> why it failed to import when in a system that has the module unreachable
>
As the failing import is throwing an exception, can't the
put the import of pexpect around a try statement so it can tell you
why it failed to import when in a system that has the module unreachable
the message that outputs is:
"No module named pexpect, import failed"
Signed-off-by: Benjamin Esquivel
---
meta/lib/oeqa/selftest/buildoptions.py | 8 +++
