pcp
[Top] [All Lists]

Re: [pcp] QA Status - python tests

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] QA Status - python tests
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 05 Dec 2012 06:06:54 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <1354614677.4291.20.camel@xxxxxxxxxxxxxxxx>
References: <1162586249.39888846.1354609821476.JavaMail.root@xxxxxxxxxx> <1354614677.4291.20.camel@xxxxxxxxxxxxxxxx>
On Tue, 2012-12-04 at 20:51 +1100, Ken McDonell wrote:

> > pcpqa$ ./check -q -l 708 709 710
> > 708 0s ...
> > 709 28s ...
> > 710 1s ...
> > Passed all 3 tests
> > 
> > 
> > Same results both with and without NSS goo-dness.  Noticed the last
> > four there are all the python tests, FWIW - those failures probably
> > share a root-cause I guess.
> 
> Yep, e.g. 707.full looks like ...
> 
> Traceback (most recent call last):
>   File "/home/kenj/src/pcp/qa/src/test_pcp.python", line 16, in <module>
>     import pmapi
> ImportError: No module named pmapi

I can get 707 to pass if
        PYTHONPATH=/usr/lib/python2.7/site-packages
is set in the environment, so it looks like we're installing the modules
in place where my version of python (2.7) is not looking for the
modules.

I know nothing about python, ... is this expected / normal.

If QA needs to know where the package installed the modules we'll need
some additional /etc/pcp.conf help to make this all work.

<Prev in Thread] Current Thread [Next in Thread>