For the first error you mentioned, your VM is too old or was not installed correctly.  The error says that the python module scipy is missing, that module was added to the bootstrap repo on 2013-01-13.

For the second error, I fixed the bug and pushed the changes.

- Travis

On Thu, Feb 6, 2014 at 12:44 PM, Michael Sneddon <mwsneddon@lbl.gov> wrote:

Hi Andreas, Tobi, and Travis,

On testing for script standards, two scripts appear to be failing.  It looks like communities_api is still set for production release, but you should probably be aware:

root@t1:~/msneddon-work/2013doctests/testing/script-tests# grep fail tests/communities_api.report.txt

----------TEST communities_api mg-inbox-decompress with -h option fail

----------TEST communities_api mg-inbox-decompress with --help option fail

----------TEST communities_api mg-correlate-metadata with -h option fail

----------TEST communities_api mg-correlate-metadata with --help option fail

root@t1:~/msneddon-work/2013doctests/testing/script-tests# mg-correlate-metadata -h

Traceback (most recent call last):

  File "/kbase/deployments/20140109-prod//pybin/mg-correlate-metadata.py", line 9, in <module>

    from scipy import stats

ImportError: No module named scipy

root@t1:~/msneddon-work/2013doctests/testing/script-tests# mg-inbox-decompress -h

Global symbol "$input" requires explicit package name at /kbase/deployments/20140109-prod//plbin/mg-inbox-decompress.pl line 61.

Execution of /kbase/deployments/20140109-prod//plbin/mg-inbox-decompress.pl aborted due to compilation errors.