Can't get tests to run -- any help available?

[jimgraham]

Hi

I've followed the README instructions, using OSX 10.10, VB 5.08 and vagrant 1.7.4 .

At provisioning, I get

==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
==> default: Mounting NFS shared folders...
==> default: Mounting shared folders...
    default: /home/vagrant/.hosthome => /Users/jim
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
mecano% vagrant ssh

(I'm not sure if that's an error -- a cursory search indicates that it isn't)

Then in the VM I get errors like

Welcome to your Vagrant-built virtual machine.
Last login: Sun Nov  8 18:26:26 2015 from 10.0.2.2
vagrant@djangocore:~$ runtests2.6-sqlite
Traceback (most recent call last):
  File "/django/tests/runtests.py", line 11, in <module>
    from argparse import ArgumentParser
ImportError: No module named argparse

or

vagrant@djangocore:~$ runtests2.7-sqlite
Please install test dependencies first:
$ pip install -r requirements/py2.txt

Also, in the home directory is the file postinstall.sh which according to #11 should have been removed when https://github.com/jphalip/djangocore-box/blob/master/provisioning/shell/init-system.sh was run.

It appears that the provisioning didn't run to completion?

Any help would be greatly appreciated.

[jimgraham]

Also, when trying to build from the VagrantFile-build file, I get

ox/provisioning/chef
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: Current version: Chef: 10.14.2
==> default: Uninstalling and then installing version: 10.16.2
==> default: Removing chef-client
==> default: Removing chef-solo
==> default: Removing knife
==> default: Removing shef
==> default: Successfully uninstalled chef-10.14.2
==> default: ERROR:  Error installing chef:
==> default:    mixlib-shellout requires Ruby version >= 1.9.3.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.