Ok, so I've got the source - but before I begin my first problem already 
arises.. 

I ran the tests and one of them failed:

Failures:

  1) Vagrant::Environment#home_path throws an exception if inaccessible

     Failure/Error: expect {
       expected Vagrant::Errors::HomeDirectoryNotAccessible but nothing was 
raised
     # ./test/unit/vagrant/environment_test.rb:47:in `block (3 levels) in 
<top (required)>'

As far as I can tell, the test tries to set the active folder to "/", 
assuming it is inaccessible and expecting failure - but in my case it is 
writeable.
(I work on OSX 10.9.1, I have not - as far as I know - changed any of the 
privileges on /). 

After running the tests I can confirm the following files are created in 
the root of my system:

-rw-r--r--   1 fzz   admin        3 Feb 24 23:12 setup_version
drwxr-xr-x   2 fzz   admin      102 Feb 24 23:12 rgloader
-rw-------   1 fzz   admin     1675 Feb 24 23:12 insecure_private_key
drwxr-xr-x   2 fzz   admin       68 Feb 24 23:12 gems
drwxr-xr-x   2 fzz   admin       68 Feb 24 23:12 data
drwxr-xr-x   2 fzz   admin       68 Feb 24 23:12 boxes
It it reasonable to expect running a test on my system *not* to create 
stuff it does not delete?
Anyone else see this happening?

Kind regards,


Ramon de la Fuente
@F_U_E_N_T_E


On Monday, February 17, 2014 9:37:15 AM UTC+1, [email protected] wrote:
>
> [ I apologise for this issue I posted to the github repo (
> https://github.com/mitchellh/vagrant/issues/2983), when it's just a 
> question and not a bug ]
>
> Hi all,
>
> I'd like to add two boxes called *primary* and *secondary* to a 
> Vagrantfile, but only startup *primary* when I run
>
> vagrant up
>
> Starting the *secondary* box would require an explicit
>
> vagrant up secondary
>
> Is this possible?
>
> I've added primary: true to the *primary* box, but there doesn't seem to 
> be a way to avoid the *secondary *box from starting up.
>
> (a little background: I have a project containing a development box that 
> everyone should use to work with the project, but I also add a 
> "production-test" box to test provisioning and deployment Ansible scripts 
> agains a box set up like a production server. This "production-test" box is 
> overhead for regular developers)
>
> Regards,
>
> Ramon de la Fuente
> @f_u_e_n_t_e
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to