[wp-gsoc] [WordPRess GSoC Trac] #383: Testing environment - Vagrantfile error
WordPRess GSoC Trac
noreply at wordpress.org
Sun Mar 9 01:39:03 UTC 2014
#383: Testing environment - Vagrantfile error
---------------------------+-------------------------
Reporter: tony.wips | Owner: rmccue
Type: defect | Status: new
Priority: normal | Milestone:
Component: JSON REST API | Keywords: needs-patch
---------------------------+-------------------------
After issuing the 'vagrant up' command I get the errors:
...
Hit http://us.archive.ubuntu.com precise-backports/restricted Translation-
en
Get:53 http://us.archive.ubuntu.com precise-backports/universe
Translation-en [28.0 kB]
Fetched 3,269 kB in 9s (347 kB/s)
Reading package lists...
[default] Running provisioner: puppet...
Running Puppet with development.pp...
stdin: is not a tty
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type apt::ppa at /tmp/vagrant-puppet-1/manifests/development.pp:2
on node vagrant.tin.it
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
puppet apply --verbose --debug --modulepath '/tmp/vagrant-
puppet-1/modules-0' --color=false --manifestdir /tmp/vagrant-
puppet-1/manifests --detailed-exitcodes /tmp/vagrant-
puppet-1/manifests/development.pp || [ $? -eq 2 ]
Stdout from the command:
Stderr from the command:
stdin: is not a tty
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type apt::ppa at /tmp/vagrant-puppet-1/manifests/development.pp:2
on node vagrant.tin.it
Additionally, Quick Setup instructions in https://github.com/WP-API/WP-API
not correct:
between step 2. and step 3. I guess a 'cd api-tester' command has to be
inserted
--
Ticket URL: <https://gsoc.trac.wordpress.org/ticket/383>
WordPRess GSoC Trac <https://gsoc.trac.wordpress.org/>
WordPress Google Summer of Code Trac
More information about the wp-gsoc
mailing list